-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add gitattributes file to standardize line endings #7191
Comments
Hi, can I work on this? TIA |
@maribethb can I work on this issue? |
Hi @mehboobali98 you got here first, go for it! We have information about contributing on our site. One important thing it to make sure your commit messages are formatted appropriately. Thanks! @1mazin Someone else asked first but will let you know if they decide to drop the issue. You might find other issues you want to work on by checking the Thanks! |
Hello @maribethb, |
@sam301100 Go for it! |
Thank you so much! |
🚧⚠️ 🚧 This issue is being saved for Grace Hopper Open Source Day. 🚧⚠️ 🚧 An event we're running to help girls and non-binary technologists make their first contributions to open source! Please see our list of help wanted issues if you'd like to contribute!
Check for duplicates
Description
If you change files when working on Windows, you will end up checking in files with Windows-style CRLF line endings, but the library should use Linux-style LF endings.
To rectify this, we should add a
.gitattributes
file with the following content:This will have Git automatically convert the line endings in any text-based file (so not binary files like images) to LF when checking them out, but allow you to use CRLF endings on your local copy if you're using Windows.
h/t this article for the info
The text was updated successfully, but these errors were encountered: