3 ms·
> You can also override import resolution to point to a fork (eg. of any module if using gomodules), if you want to test drive some local patches. So much over
by doublerabbit 6y ago
> You can also override import resolution to point to a fork (eg. of any module if using gomodules), if you want to test drive some local patches.
So much overhead where time is limited. I shouldn't need to fork packages, I don't want to fork.
- q3k 6y agoIt's one `cp -r` and a 1 line change in go.mod [1]. You can also just `go mod vendor` to have all modules land in a `vendor/` directory when you can edit things as you wish [2]. [1] - https://golang.org/ref/mod#go-mod-file-replace https://golang.org/ref/mod#go-mod-file-replace [2] - https://golang.org/ref/mod#vendoring https://golang.org/ref/mod#vendoring