Handle modified files where the case of the filename changed on case-insensitive filesystems#6327
Merged
WithoutPants merged 3 commits intostashapp:developfrom Dec 2, 2025
Merged
Conversation
… found nothing This limits the overhead to new paths, and adds an extra query for new paths to windows installs
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
1 participant
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.
Adjusts the scanning process so that, if an existing file/folder isn't found for a given scanned file, it will test the path filesystem for case sensitivity. If it is not case sensitive (ie on a windows machine), then it will perform a second, case insensitive query. This means that on case insensitive paths, a file/folder that has been renamed with a differently cased (but otherwise equal) name will be treated as an existing file/folder, rather than a new one. The execution path for existing paths has been changed to also rename the file/folder basename/path to the new one if it has changed.
There is an overhead introduced with this change, but it is limited to running the case sensitivity checks for any new file/folder, and running a second file/folder query for new/renamed paths on case insensitive file systems.
Resolves #6326.
Related to #1426, as it re-solves that issue.