You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's annoying when I create a new project, the first thing I have to do is copy my .gitattributes from somewhere else lest something be committed incorrectly (like line ending fixes to lf in a .bat. autocrlf isn't really the recommended way to go these days. The best way is gitattributes. This is a good enough default for .gitattributes since these are the extensions/files that will get generated. I'm not certain if you generate with mvnw if you do then you will need to update for that.
* text=auto eol=lf
*.sh text eol=lf
*.bat text eol=crlf
*.jar -text
/gradlew text eol=lf
bat, cmd, ps will not work with lf line endings, any variant of an sh will not work with crlf, even on a windows bash (last time I tried) that's why this should be done.
The text was updated successfully, but these errors were encountered:
#
# https://help.github.com/articles/dealing-with-line-endings/
#
# Linux start script should use lf
/gradlew text eol=lf
# These are Windows script files and should use crlf
*.bat text eol=crlf
# Binary files should be left untouched
*.jar binary
it's annoying when I create a new project, the first thing I have to do is copy my
.gitattributes
from somewhere else lest something be committed incorrectly (like line ending fixes tolf
in a.bat
. autocrlf isn't really the recommended way to go these days. The best way is gitattributes. This is a good enough default for.gitattributes
since these are the extensions/files that will get generated. I'm not certain if you generate withmvnw
if you do then you will need to update for that.bat
,cmd
,ps
will not work withlf
line endings, any variant of ansh
will not work withcrlf
, even on a windows bash (last time I tried) that's why this should be done.The text was updated successfully, but these errors were encountered: