Add .gitattributes to fix prettier behavior on Windows
#1042
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
Since prettier enforces LF line endings, it would forcefully convert Windows' CLRF linebreaks on every run, causing undesired changes for contributors using Windows. This is taken from prettier's own `.gitattributes` file: https://github.com/prettier/prettier/blob/main/.gitattributes Signed-off-by: nscuro <nscuro@protonmail.com>
1 task
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.
Description
Adds
.gitattributesto fix prettier behavior on Windows.Since prettier enforces LF line endings, it would forcefully convert Windows' CLRF linebreaks on every run, causing undesired changes for contributors using Windows.
This is taken from prettier's own
.gitattributesfile: https://github.com/prettier/prettier/blob/main/.gitattributesAddressed Issue
N/A
Additional Details
N/A
Checklist
This PR introduces new or alters existing behavior, and I have updated the documentation accordingly