Repository navigation
Renormalize line endings for files with CRLF matching .gitattributes patterns - #138
Merged
Merged
Conversation
paolosalvatori
approved these changes
Oct 19, 2026
paolosalvatori
left a comment
Contributor
There was a problem hiding this comment.
Thanks @purcell, I use Visual Studio Code from WSL, and I think also @DrisDary and @bryansan-local. Nonetheless, apparently, some files contain CRLF instead of LF 🙂
This branch was successfully deployed
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.
Motivation
A fresh checkout of this repo on a non-Windows machine immediately shows several files modified, apparently because they were added with CRLF line endings before the corresponding .gitattributes rules were added: the fix is to
git add --renormalizethose files.Changes
git add --renormalize .No further changes were made.
Tests
Related