fix: drop case-sensitive file collision by removing triage.json #5465
Conversation
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
Resolves ossf#5437 - Verified TRIAGE.json and triage.json are identical (no merge needed) - Deleted triage.json to resolve case-sensitivity issues on Windows - Updated test/test_requirements.py to reference TRIAGE.json - Confirmed no GitHub Actions workflows reference triage.json Signed-off-by: Eshaan <[email protected]>
Eshaan-byte
force-pushed
the
fix-triage-json-case-issue
branch
from
c12eed5 to
58c3b43
Compare
ffontaine
changed the title
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.
Fixes #5437
Changes
triage.json(identical toTRIAGE.json)test/test_requirements.pyto referenceTRIAGE.jsontriage.jsonThis resolves the case-sensitivity issue on Windows filesystems.