Clarify wildcard behavior in watch paths#28164
Merged
elithrar merged 1 commit intoproductionfrom Feb 13, 2026
Merged
Conversation
Co-authored-by: elithrar <elithrar@users.noreply.github.com>
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
elithrar
approved these changes
Feb 6, 2026
Contributor
|
Preview URL: https://6a6fa031.preview.developers.cloudflare.com Files with changes (up to 15) |
|
This is wild! (no pun intended) However I'm not sure it's a real fix. |
caley-b
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's a summary of the changes made to
src/content/docs/pages/configuration/build-watch-paths.mdx:Problem: The documentation was misleading about how the
*wildcard works in build watch paths. Users expected standard shell glob behavior where*does not match path separators (/), meaningdir/*would only match files directly insidedir/but not in nested subdirectories. The wildcard note also used a branch-matching example that was confusing in a file path context.Changes made:
Clarified wildcard behavior: Rewrote the
:::note[Wildcard syntax]callout to explicitly state that*matches including path separators (/). Added concrete examples showing thatdocs/*matches files at any nesting depth (docs/README.md,docs/guides/setup.md,docs/guides/advanced/config.md).Removed confusing branch example: The old note used a branch-matching example (
fix/*matching branch names) which was out of place on a file path documentation page. Replaced it with file path examples relevant to the actual use case.Improved examples section:
Fixed minor typo: "a empty push event" -> "an empty push event".
Closes #27710
github run