Ah… yes, that would probably let me work on it. Didn’t occur to me — thanks for pointing it out. It seems unpleasant to deal with, though, especially since there is a non-zero chance that you then commit your go.mod file with that change inadvertently.
I think a local replace will do that. Something like: replace " > foo.com/my/pkg" v1.5.2 => ../local-clone-with-changes > Put that in the top-level module, and it should override that import > throughout the build with your local copy, pending changes and all. Or is > that not what you were trying to do here? -- 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.
