Create .gitattributes - #1108
Merged
Merged
Conversation
tj-wazei
approved these changes
May 12, 2024
Zabuzard
requested changes
May 13, 2024
Zabuzard
left a comment
Zabuzard
left a comment
Member
There was a problem hiding this comment.
What about existing code? If this is ticked, will tooling suddenly report that some existing code has the wrong file endings?
If so, it has to be changed in the same PR as well.
Zabuzard
approved these changes
May 13, 2024
Zabuzard
left a comment
Zabuzard
left a comment
Member
There was a problem hiding this comment.
(wazei says on discord that all files are already LF)
Merged
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
3 participants
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.
Created a .gitattributes to enforce LF encoding. On Windows when I ran spotless, it changes the line encoding to CFRL which is incorrect.