You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 15, 2023. It is now read-only.
When I setup a go.goroot project setting I expect that the install tools would use the go command installed in that location, and not try to find it from the $PATH environment variable.
I have a setup where I want different tooling and different versions of the go environment for different projects and they should all be self contained.
Output:
Installing 1 tools
goreturns
Installing goreturns FAILED
1 tools failed to install.
goreturns:
Error: Command failed: go get -u -v sourcegraph.com/sqs/goreturns
/bin/sh: go: command not found
/bin/sh: go: command not found
When I setup a go.goroot project setting I expect that the install tools would use the go command installed in that location, and not try to find it from the $PATH environment variable.
I have a setup where I want different tooling and different versions of the go environment for different projects and they should all be self contained.
Output: