-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
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
FR: Gazelle should import direct dependencies directly without requiring buildozer #1749
Comments
I minor improvement comes with bazel 7.1's But yes, ideally the user shouldn't have to do anything manually besides running |
We'll integrate |
Quick question would this also work with |
Yes, we'll watch for any changes to your |
What version of gazelle are you using?
0.35.0
What version of rules_go are you using?
0.46.0
What version of Bazel are you using?
7.0.2
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
Macos
What did you do?
When using bzlmod support and go_deps being read from go.mod users still need to add manually direct dependencies to the use_repo rule. When running gazelle it will warn us when those are out of sync and give us a buildozer command to update it.
What did you expect to see?
Gazelle should be able to add this without users having to run the buildozer command. Alternatively rules_go should be able to add the direct dependencies as determined by go.mod without user intervention.
What did you see instead?
I have to run 3 commands to get everything to work:
With my proposal we could limit it to 2:
The text was updated successfully, but these errors were encountered: