Brandon Rozek

Photo of Brandon Rozek

PhD Student @ RPI studying Automated Reasoning in AI and Linux Enthusiast.

Git Line Endings

Published on

Updated on

2 minute reading time

Warning: This post has not been modified for over 2 years. For technical posts, make sure that it is still relevant.

if you have worked with a team that has a mix of Windows and Linux developers, you might have noticed pull requests where Git reports changes in a file that is not visible. One explanation is that the line endings might have changed.

Due to historical reasons Windows uses a line ending called CRLF which stands for carriage return + line feed. This dates back to type writers where once you hit the line feed button to push the paper up, you need to press the carriage return button to move back to the left side of the paper. Wikipedia has more of a history if you want to learn more.

Meanwhile, Linux only uses LF or line feed for its ending. We can configure a repository with a .gitattributes file to automatically convert CRLF to LF line endings in order not to see these frivolous changes in our repository.

The .gitattributes file looks like this

# Automatically convert CRLF->LF on files git thinks are text
* text=auto

# Explicitly declare what are text files
*.py text
*.js text

# Denote files that are binary and should not be modified.
*.png binary
*.jpg binary

Make sure that you don’t have any working changes that need to be committed as the following commands will convert all the line endings for text files in your repository to LF.

First let us commit the git attributes file

git add .gitattributes
git commit -m "Added gitattributes file"

Then let us convert all the line endings to LF

git add --renormalize .
git commit -m "Convert line endings to LF"

Then tell your coworkers to expect a large commit which only line ending changes….

Reply via Email Buy me a Coffee
Was this useful? Feel free to share: Hacker News Reddit Twitter

Published a response to this? :