Repository navigation
[Docs Preview] Clarify allowed characters and spaces in target names in documentation. - #30870
copybara-service[bot] wants to merge 1 commit into
Conversation
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
|
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 preview is ready! Preview URL: https://bazel-pr-30870.mintlify.app/ Updated for |
|
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. |
|
Not stale |
|
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. |
|
@hvadehra I think this is still relevant |
Clarify allowed characters and spaces in target names in documentation.
The target name lexical specification in
labels.mdxomitted 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.mdxto 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.