Set consistent line endings

[o-sapov]

When working with the repository on different platforms, there are problems with line ending consistency, which causes Git to show irrelevant changes, which is inconvenient.

This could be improved by setting line endings for the project using the .gitattributes file.

Here is an example of a basic configuration: This sets the line endings to the Windows style for all text files and identifies binary files, such as images.

* text=auto eol=crlf
# Pictures
*.png binary
*.jpg binary
*.gif binary
*.svg binary
# Documents
*.pdf binary

I had a good experience with this setup when I was primarily developing on Windows, but also checking out the repository on a Linux server. However, the music-encoding repository has a different setup involving GitHub Actions. In this case, probably it would be better to set the line endings to the Linux style. This is also recommended by deepwiki . Some other considerations might be needed.

Here are also pros and cons from chatgpt: https://chatgpt.com/s/t_6867898361ec819193b4b7ab89c43247

[craigsapp]

* text=auto eol=crlf

* means any file

text=auto: git automatically determines if the file is text or binary. If text, then the internal repository newlines will automatically be set to LF. When checking out, git will use either LF or CRLF depending on the operating system preferences (LF for linux/Mac; CRLF for Windows). But see further below about this.

eol=crlf = Overrides the OS default and extracts text files from the repository as CRLF. This is not a useful option for Linux/unix or MacOS, since it forces the text files to be in Windows format, so it should not be used in .gitattributes.

For:

# Pictures
*.png binary
*.jpg binary
*.gif binary
*.svg binary
# Documents
*.pdf binary

These should not be necessary because Git should automatically identify them as binary and not do any LF/CRLR processing. If you did * text instead of * text=auto, then you would need these extra options, since * text means treat all files as if they were text (and would mess up binary files as a result).

---

Are you having problems with newline styles in Windows? If so, then running this command (in PowerShell?) should fix the problem:

git config --global core.autocrlf true

This should make text files in any git repository you have behave properly on Windows (not only this specific one), where text files on the disk will have CRLF newlines, and in the repositories they will be LF (at least for Windows computers). This would be preferable to adjusting in a repository .gitattributes file (particularly since the one you suggest would cause problems in linux/mac).