Docs: recommend bracket-glob patterns for cross-platform case safety in FAQ (refs #6187) - #6192
Merged
chrisd8088 merged 3 commits intoJan 24, 2026
Merged
Conversation
Author
|
Updated the FAQ entry to keep wording filesystem/OS-neutral, use the bracket-glob examples directly in |
chrisd8088
approved these changes
Jan 17, 2026
chrisd8088
left a comment
Member
There was a problem hiding this comment.
Hey, thanks for this addition to our FAQ, it looks great!
I'll hold off running our CI tests and merging this PR until the tests are passing again; we're just waiting for a regression in upstream Git to be resolved, which should happen soon.
Thanks again for helping improve our documentation!
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
2 participants
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.
Addresses part of #6187 by documenting the portable bracket-glob workaround in git-lfs-faq(7).
Adds a new FAQ entry under Tracking and Migration explaining that .gitattributes patterns are case-sensitive, which can cause assets committed on macOS/Windows with uppercase extensions to fail matching on Linux CI, leaving LFS pointer files.
Docs-only change; no behavior or performance impact.
Test/verification:
Verified that *.[pP][nN][gG] matches both file.png and file.PNG on a case-sensitive filesystem.