Add a case_conflict.py to check for case-only file conflicts. #574
Conversation
This file contains 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
This is confusing and can cause issues for folks running case
insensitive filesystems (happens in windows sometimes).
If there is a conflict the pages in question are output. And you get an
non-zero exit status. E.g.
Conflict!
../../README.md
../../Readme.md
andynu
force-pushed
the
case_conflicts.py
branch
from
5b54de2
to
ca65fdb
Compare
…ript. This will prevent the addition of new files where the only difference between it and an existing file is the case of the filename.
This should ensure human edits to files do not result in filenames that differ only in the case of the filename.
claremacrae
approved these changes
Dec 19, 2022
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.
This is confusing and can cause issues for folks running case insensitive filesystems (happens in windows sometimes).
If there is a conflict, the pages in question are output. And you get an non-zero exit status. E.g.
Additionally adds this check to the update_hub and check_content github workflows.
Related to #308