While this seems to be the correct way to do it, it also seems like a very obvious point of entry for human error.
We have tooling to prevent incorrect commits of files using gitignore and hgingnore and yet people still accidentally commit files that should not end up in repositories. Now the situation exists where there is a file that is intended to be committed to the repository, but during development may need to have specific lines of it altered for development builds. The absence of good documentation for the modules workflow and apparent warts like this make the change to modules an unwelcoming experience for Go developers. On Fri, 2018-08-31 at 10:54 -0700, Seth Hoenig wrote: > You'll want to add a replace directive to the go.mod file to > reference the > copy of your library Pkg on disk, e.g. > > replace github.com/author/package => ../<wherever>/package -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
