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? Sign in to your account
$ go version go version devel +ce7534ff06 Fri Mar 8 13:46:43 2019 +0000 linux/amd64
When go mod why is asked to show a module that isn't a dependency, it prints a "main module does not need" line, but it succeeds regardless.
go mod why
Perhaps it should be changed so that the exit status reflects whether the dependency was actually found or not.
The text was updated successfully, but these errors were encountered:
See also #27900.
Sorry, something went wrong.
This would have made a CI script quite a lot simpler for me. The closest I can do right now is something like go mod why <arg> | grep 'does not need'.
go mod why <arg> | grep 'does not need'
No branches or pull requests
When
go mod why
is asked to show a module that isn't a dependency, it prints a "main module does not need" line, but it succeeds regardless.Perhaps it should be changed so that the exit status reflects whether the dependency was actually found or not.
The text was updated successfully, but these errors were encountered: