When developing on Windows, a git clone operation may automatically convert file line endings to CRLF, leading to a Sad

[miketheman]

Describe the bug
Our docs tell users to git clone the repo, and if performed in the outer context (Windows CLI), this can lead to git changing file endings and making the shells scripts non-executable by our docker containers.

Expected behavior
make commands on Windows complete successfully.

Proposed solution

Create a .gitattributes file in the root of the repo, setting all files to be lf (or \n - whichever is the correct config), so anyone cloning the code on Windows will not run into this as well.

Refs:

• https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#:~:text=core.-,autocrlf,-If%20you%E2%80%99re%20programming
• https://git-scm.com/docs/gitattributes

Credit to @AshtonWooster who uncovered this problem!