Or there is vendoring <https://go.dev/ref/mod#go-mod-vendor>.
On Monday, 5 December 2022 at 09:16:24 UTC stephane....@gmail.com wrote: > Hi, > > If you don't want to commit *go.mod*, you can use *go.work > <http://go.work> *https://go.dev/ref/mod#go-work-file > > On Monday, December 5, 2022 at 9:52:17 AM UTC+1 kortschak wrote: > >> On Sun, 2022-12-04 at 23:47 -0800, 'Christian Stewart' via golang-nuts >> wrote: >> > I definitely fork things and use "replace" quite frequently. >> >> It *can* be used, but it is not the solution in the general case as >> Volker said. A replace in a library's go.mod file has no effect on >> consumers of that library. >> >> https://go.dev/ref/mod#go-mod-file-replace: >> >> > replace directives only apply in the main module’s go.mod file and >> are ignored in other modules. See Minimal version selection for >> details. >> >> -- 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/bb56e11c-e6c5-425a-8243-df7929021014n%40googlegroups.com.
