-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Use "apparent name" instead of "local name" in Bzlmod docs #16548
Conversation
"Apparent" is used all over the codebase now, so it makes sense to also use it in user-facing docs. Also slightly rewords the definition of an "apparent repository name" to make it easier to understand.
@meteorcloudy Could you review? This was the result of a discussion with @Wyverald on #16321 (comment). @fweikert Are cherry-picks the way to get this into the docs versioned for 6.0.0? |
yes |
@bazel-io flag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@bazel-io fork 6.0.0 |
"Apparent" is used all over the codebase now, so it makes sense to also use it in user-facing docs. Also slightly rewords the definition of an "apparent repository name" to make it easier to understand. Closes bazelbuild#16548. PiperOrigin-RevId: 484507525 Change-Id: I8e3af88ddbe5f7b31af47d3ea5a6821ac6e71056
"Apparent" is used all over the codebase now, so it makes sense to also use it in user-facing docs. Also slightly rewords the definition of an "apparent repository name" to make it easier to understand. Closes #16548. PiperOrigin-RevId: 484507525 Change-Id: I8e3af88ddbe5f7b31af47d3ea5a6821ac6e71056
"Apparent" is used all over the codebase now, so it makes sense to also use it in user-facing docs.
Also slightly rewords the definition of an "apparent repository name" to make it easier to understand.