fix(.editorconfig): remove setting end_of_line and make Git track EOL changes on Windows #7725
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
…line changes on Windows
unknwon
changed the title
unknwon
changed the title
unknwon
changed the title
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.
…line changes on Windows
Describe the pull request
By default, Git automatically changes end_of_line between LF and CRLF.
In this case, when a file is opened in an editor with editorconfig on Windows, and then saved without any textual changes,
editorconfig will change end_of_line from CRLF to LF.
At the same time, Git will notice this change. You have to commit it or restore it.
Just let Git handle it, I suggest removing the setting of end_of_line in editorconfig.
Link to the issue: n/a"
Checklist