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
I've had a persistent issue when setting up new clones of FTOT where many or all files appear modified even though they are newly downloaded. As best I can tell, it's related to line endings. I know we have .gitattributes setting eol=crlf for the repository, which should cover this, but does not seem to be adequate.
When I modify the line in .gitattributes to "* text=auto eol=crlf", then files properly register as unchanged. I'll submit a pull request with this change - I think it will have no impact, if you were not already having this problem. I am not changing the crlf setting, only which files it's applied to.
If your global autocrlf setting is set to false, you probably never run into this anyway.
But anyone available, please test.
The text was updated successfully, but these errors were encountered:
I've had a persistent issue when setting up new clones of FTOT where many or all files appear modified even though they are newly downloaded. As best I can tell, it's related to line endings. I know we have .gitattributes setting eol=crlf for the repository, which should cover this, but does not seem to be adequate.
When I modify the line in .gitattributes to "* text=auto eol=crlf", then files properly register as unchanged. I'll submit a pull request with this change - I think it will have no impact, if you were not already having this problem. I am not changing the crlf setting, only which files it's applied to.
If your global autocrlf setting is set to false, you probably never run into this anyway.
But anyone available, please test.
The text was updated successfully, but these errors were encountered: