chore: define repository line endings#344
Merged
Merged
Conversation
Greptile SummaryThis PR defines consistent repository line endings through
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (1): Last reviewed commit: "chore: define repository line endings" | Re-trigger Greptile |
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.
Summary
.gitattributes.git add --renormalize .; tracked blobs were already normalized, so the PR contains no noisy whole-repository rewrite.Why
Repository-level attributes make checkouts deterministic across platforms and prevent
core.autocrlfwarnings from obscuring real changes.Test plan
dotnet test TomLonghurst.EnumerableAsyncProcessor.sln -c Release(1,074 passed across net8.0 and net9.0)git diff --cached --checkgit check-attr text eol -- README.md scripts/AgentLocks.ps1 .gitattributesCloses #342