We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
$ go version
go version devel go1.18-3d7cb23e3d Wed Nov 17 01:56:19 2021 +0000 darwin/amd64
When running a go command in a directory whose parent directory defines go.work but does not include this directory in its use section, the go command output is rather confusing.
$ cat go.work
$ cd tools; go list ./...
pattern ./...: directory prefix . outside available modules
Even though users can check go env GOWORK, consider to explicitly mention the existence of go.work.
(maybe something like pattern ./...: directory prefix . outside modules listed in go.work?)
go env GOWORK
pattern ./...: directory prefix . outside modules listed in go.work
Or, let it operate in a single module mode as if there is no go.work - but not sure which one is less confusing.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
@matloob This is in the 1.18 milestone; time to move to 1.19? Thanks.
I can fix this for 1.18.
Change https://go.dev/cl/384236 mentions this issue: cmd/go: mention go.work when local path outside modules in go.work
cmd/go: mention go.work when local path outside modules in go.work
What is the reason why the main module is not automatically included in the workspace?
No branches or pull requests