use_repo
should be called use_repos
#17146
Labels
area-Bzlmod
Bzlmod-specific PRs, issues, and feature requests
P4
This is either out of scope or we don't have bandwidth to review a PR. (No assignee)
stale
Issues or PRs that are stale (no activity for 30 days)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Description of the bug:
The name
use_repo
doesn't make it clear that the function accepts an arbitrary number of arguments. There are examples of BCR modules with successive, repeateduse_repo
calls with a single repo name for the same extension proxy, so this is already providing incorrect intuition to real users.The singular form is also inconsistent with other API such as
register_toolchains
andregister_execution_platforms
.Since there are only ~40 modules today, many of which don't even use
use_repo
, addinguse_repos
and keepinguse_repo
as a deprecated alias for the time being may be doable. Given that this new function will (hopefully) stay with us for a long time, it may very well be worth the effort.What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Any
What is the output of
bazel info release
?6.0.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: