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

Use "apparent name" instead of "local name" in Bzlmod docs #16548

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Oct 25, 2022

"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.

"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.
@fmeum
Copy link
Collaborator Author

fmeum commented Oct 25, 2022

@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?

@Wyverald
Copy link
Member

@fweikert Are cherry-picks the way to get this into the docs versioned for 6.0.0?

yes

@fmeum
Copy link
Collaborator Author

fmeum commented Oct 25, 2022

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Oct 25, 2022
Copy link
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@Wyverald Wyverald added the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Oct 27, 2022
@Wyverald
Copy link
Member

@bazel-io fork 6.0.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Oct 27, 2022
@fmeum fmeum deleted the patch-6 branch October 28, 2022 12:43
@sgowroji sgowroji added team-Documentation Documentation improvements that cannot be directly linked to other team labels and removed awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally labels Oct 28, 2022
fmeum added a commit to fmeum/bazel that referenced this pull request Oct 28, 2022
"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
Wyverald pushed a commit that referenced this pull request Oct 28, 2022
"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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Documentation Documentation improvements that cannot be directly linked to other team labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants