Skip to content

[Docs Preview] Clarify allowed characters and spaces in target names in documentation. - #30870

Draft
copybara-service[bot] wants to merge 1 commit into
masterfrom
copybara_docs_preview_971199303
Draft

copybara-service[bot] wants to merge 1 commit into
masterfrom
copybara_docs_preview_971199303

Conversation

@copybara-service

Copy link
Copy Markdown

Clarify allowed characters and spaces in target names in documentation.

The target name lexical specification in labels.mdx omitted spaces, backticks, and non-ASCII characters from the listed character set, causing confusion over whether spaces are permitted in target names (#27628).

Update docs/concepts/labels.mdx to include spaces and non-ASCII code points in the documented set of allowed characters, explicitly noting that spaces are supported because package source files may contain spaces in their filenames.

RELNOTES: Document that target names allow spaces and non-ASCII characters.

The target name lexical specification in `labels.mdx` omitted spaces, backticks, and non-ASCII characters from the listed character set, causing confusion over whether spaces are permitted in target names (#27628).

Update `docs/concepts/labels.mdx` to include spaces and non-ASCII code points in the documented set of allowed characters, explicitly noting that spaces are supported because package source files may contain spaces in their filenames.

RELNOTES: Document that target names allow spaces and non-ASCII characters.
PiperOrigin-RevId: 971199303
@google-cla

google-cla Bot commented Aug 26, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@bazel-docs-pr-commenter

Copy link
Copy Markdown

✅ Bazel docs preview is ready!

Preview URL: https://bazel-pr-30870.mintlify.app/

Updated for 4440c475c90200748aa7f159cbaf10b59ca185bf

@github-actions

Copy link
Copy Markdown

Thank you for contributing to the Bazel repository! This pull request has been marked as stale since it has not had any activity in the last 30 days. It will be closed in the next 30 days unless any other activity occurs. If you think this PR is still relevant and should stay open, please post any comment here and the PR will no longer be marked as stale.

@github-actions github-actions Bot added the stale Issues or PRs that are stale (no activity for 30 days) label Sep 26, 2026
@phst

phst commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

Not stale

@github-actions github-actions Bot removed the stale Issues or PRs that are stale (no activity for 30 days) label Oct 1, 2026
@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown

Thank you for contributing to the Bazel repository! This pull request has been marked as stale since it has not had any activity in the last 30 days. It will be closed in the next 30 days unless any other activity occurs. If you think this PR is still relevant and should stay open, please post any comment here and the PR will no longer be marked as stale.

@github-actions github-actions Bot added the stale Issues or PRs that are stale (no activity for 30 days) label Nov 1, 2026
@phst

phst commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

@hvadehra I think this is still relevant

@github-actions github-actions Bot removed the stale Issues or PRs that are stale (no activity for 30 days) label Nov 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant