Enforce line-feed/new-line character as the only EOL for certain line-ending sensitive script files.

TAMULib / LibraryServiceStatusSystemUI

MIT License

0 stars 0 forks source link

Enforce line-feed/new-line character as the only EOL for certain line-ending sensitive script files. #239

Closed kaladay closed 1 year ago

kaladay commented 1 year ago

This problem happens when starting a Docker container that attempts to run these files. The line-endings could end up with carriage-return characters and the scripts may fail to execute.

References:

https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreattributesFile
https://git-scm.com/docs/gitattributes
https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings

coveralls commented 1 year ago

coverage: 40.103%. remained the same when pulling 579ee1cb308a5074bfbd94d99ed981f43ca046a4 on build_scripts-git_line_endings into 419a759c31e93100d7223d91ea16fc385624a67a on main.