4 ms·
You can use a shell script that you check into your repos that explicitly sets these environment values instead of using the go command directly. As long as you
by shkkmo 7y ago
You can use a shell script that you check into your repos that explicitly sets these environment values instead of using the go command directly. As long as you habitually never run "go get" or "go build" directly it ameliorates the issues you mentioned.
- Cthulhu_ 7y agoIndeed; if you're working with multiple developers and you need these policies enforced, you should use e.g. a makefile. I'm not sure if it's possible to force the use of that over straight `go` commands though.