When debugging or testing we may need to add a replace directive in the go.mod file.
This change intended to be local only may interfere with code versioning. The replace directive may be accidentally committed and published. What is the proper way to manage replace directives when it comes to code versioning ? Apparently we are supposed to remove replace directives before commits, and put it back to continue testing. That is boring and error prone. Is there a better way ? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/46a8f57b-f0cc-4635-b4b9-cc89aec98fdfn%40googlegroups.com.
