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
New files that don't contain a script (.sh) or configuration (.conf) are converted over to using the CRLF endings due to the .gitattributes overriding local configurations. gitattributes is only taking into consideration the 2 file extensions. For example config/homebin contains no extension scripts.
Not sure if you'd prefer to just force Unix line endings for all files moving forward:
* text eol=lf
The text was updated successfully, but these errors were encountered:
Yes, you are correct. This is to avoid confusion by not having to go that extra step and to avoid forcing all GitHub projects in a Windows environment to use Unix style line endings via the global command.
New files that don't contain a script (.sh) or configuration (.conf) are converted over to using the CRLF endings due to the .gitattributes overriding local configurations. gitattributes is only taking into consideration the 2 file extensions. For example config/homebin contains no extension scripts.
Not sure if you'd prefer to just force Unix line endings for all files moving forward:
The text was updated successfully, but these errors were encountered: