Repository navigation
chore: pin text files to LF so a Windows save is not a 259-line diff - #201
Merged
Merged
Conversation
trace-spec had no .gitattributes, so line endings were whatever each contributor's editor produced. #184 landed a one-line CHANGELOG entry as +265-264, with all 259 removed lines ending in CR and none of the added ones, rewriting the blame on a file nobody had edited. The same class cost two listing PRs in awesome-ai-governance before it. Pins *.md, *.json, *.py, *.yml and *.yaml to LF and normalises the ten text files still stored with CRLF. The normalisation is line endings only: git diff --cached --ignore-all-space reports no content change on any of them. Doing it here rather than in a contributor's PR keeps the blame churn in one commit that is obviously mechanical, instead of spread across whoever next edits docs/schema.md, schema/trace-claim.json or src/agentrust_trace/models.py. Those three are exactly the files #199 is currently touching. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Why
This repository has no
.gitattributes, so line endings are whatever each contributor's editor produces.#184 landed a one-line CHANGELOG entry as +265-264. Measured on the diff bytes: all 259 removed lines end in CR, none of the 265 added lines do, and there are exactly two genuinely new lines and zero genuinely deleted. The rest was a CRLF-to-LF conversion of a file nobody had edited, rewriting its blame.
That is the third occurrence of the class.
awesome-ai-governance#57 and #65 hit it before, and #66 fixed it there the same way.What
Pins
*.md,*.json,*.py,*.ymland*.yamltoeol=lf, and normalises the ten text files still stored with CRLF:The normalisation is line endings only.
git diff --cached --ignore-all-space --numstatreports zero changed content on every one of them.Why now rather than later
docs/schema.md,schema/trace-claim.jsonandsrc/agentrust_trace/models.pyare three of the six files #199 is currently touching. Landing this first keeps the churn in one obviously mechanical commit instead of spreading it across whoever edits those files next.The diffstat is large and every line of it is a carriage return.