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
If a file (e.g. foo_test.go) includes //+build integration, it won't touch it to rewrite it.
foo_test.go
//+build integration
The text was updated successfully, but these errors were encountered:
@djui thanks for bringing this up.
I added a new flag so you can do mod upgrade -buildflags=-tags=integration
mod upgrade -buildflags=-tags=integration
This is because the go compiler has no option to parse all go files so we have to be explicit about the build tags.
I'll think about whether it's worth replacing go/packages with manual parsing of go files so that we avoid having to explicitly pass -buildflags
go/packages
-buildflags
I might also think about replacing -buildflags with just -tags=one,two,three to make the mod API a little bit nicer. Let me know what you think :)
-tags=one,two,three
mod
Sorry, something went wrong.
No branches or pull requests
If a file (e.g.
foo_test.go
) includes//+build integration
, it won't touch it to rewrite it.The text was updated successfully, but these errors were encountered: