Skip to content
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

valid user-provided repo names are not documented #24285

Open
dws opened this issue Nov 12, 2024 · 0 comments
Open

valid user-provided repo names are not documented #24285

dws opened this issue Nov 12, 2024 · 0 comments
Assignees
Labels
help wanted Someone outside the Bazel team could own this P2 We'll consider working on this in future. (Assignee optional) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: documentation (cleanup)

Comments

@dws
Copy link
Contributor

dws commented Nov 12, 2024

Page link:

No response

Problem description (include actual vs expected text, if applicable):

I ran into an error like this when trying to enable bzlmod in our repository (with Bazel 7.2.1):

Error in use_repo: invalid user-provided repo name '2022-05-11_log': valid names may contain only A-Z, a-z, 0-9, '-', '_', '.', and must start with a letter

Interestingly enough, this repository name was just fine without bzlmod enabled.
Where are the restrictions on user-provided repo names documented on bazel.build? I saw nothing relevant on https://bazel.build/rules/lib/globals/module#use_repo

Where do you see this issue? (include link to specific section of the page, if applicable)

One place where it appears to be missing is https://bazel.build/rules/lib/globals/module#use_repo but I suspect it should be mentioned more centrally as well, as it is intended to apply to all repository names.

Any other information you'd like to share?

Comments from @Wyverald on the Bazel slack:

Screenshot 2024-11-11 at 11 12 13 PM

Links in the screenshot are:

@dws dws added team-Documentation Documentation improvements that cannot be directly linked to other team labels type: documentation (cleanup) untriaged labels Nov 12, 2024
@meteorcloudy meteorcloudy added P2 We'll consider working on this in future. (Assignee optional) help wanted Someone outside the Bazel team could own this and removed untriaged labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Someone outside the Bazel team could own this P2 We'll consider working on this in future. (Assignee optional) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

6 participants
@Wyverald @meteorcloudy @dws @iancha1992 @satyanandak and others