sbx: document OS-specific filesystem rule paths#25302
Open
dvdksn wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker-agent
reviewed
Jun 8, 2026
37ffceb to
8bf8e76
Compare
chrispatrick
approved these changes
Jun 8, 2026
docker-agent
reviewed
Jun 8, 2026
usha-mandya
approved these changes
Jun 8, 2026
Filesystem rule examples only showed POSIX paths and never explained that rules match the path format of the developer's OS. Add Windows drive-letter and backslash syntax (including the *: any-drive wildcard), note WSL support, and call out that a multi-platform policy needs a rule per path format. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
8bf8e76 to
798187a
Compare
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.
Filesystem rule examples only showed POSIX paths and never explained that rules match the path format of the developer's OS. Add Windows drive-letter and backslash syntax (including the *: any-drive wildcard), note WSL support, and call out that a multi-platform policy needs a rule per path format.