-
Notifications
You must be signed in to change notification settings - Fork 426
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
Add use_repo_add and use_repo_remove commands #1152
Conversation
@Wyverald Could you review for the Bzlmod aspects? |
6c8bede
to
7db5b82
Compare
This is soft-blocked on #1150 as otherwise the |
These commands can be used to programmatically update `use_repo` calls in MODULE.bazel files. In the future, Bazel will emit buildozer fixups relying on this command when it detects that such calls are out-of-date.
@Wyverald I updated the signature and name of the label normalization function and added a reference to https://github.com/bazelbuild/bazel/blob/dd822392db96bb7bccdb673414a20c4b91e3dbc1/src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileGlobals.java#L416. |
@vladmos Are you available to review this PR? |
Sorry, I was conducting a large scale change because of some incompatible changes of formatting rules and temporarily put all other PRs on hold. LGTM |
* Preserve compactness of `use_repo` and `use_extension` calls * Add `use_repo_add` and `use_repo_remove` commands These commands can be used to programmatically update `use_repo` calls in MODULE.bazel files. In the future, Bazel will emit buildozer fixups relying on this command when it detects that such calls are out-of-date. * Adapt label normalization to be closer to upstream * Fix CI
These commands can be used to programmatically update
use_repo
calls in MODULE.bazel files. In the future, Bazel will emit buildozer fixups relying on this command when it detects that such calls are out-of-date.Fixes #1149
Work towards bazelbuild/bazel#17908