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
If you have git setup on Windows to convert LF to CRLF, running format creates a huge diff even though nothing really changed. If we set tsfmt to not change the line endings, then that will make it simpler here but could make us end up with a bunch of bad line endings.
I'm wondering if we could configure our git repo to automatically do the conversion and not worry about it in tsmft?
The text was updated successfully, but these errors were encountered:
I think if we can get GitHub to enforce LF over CRLF, then I'm for getting rid of the tsfmt rule. However, I believe the configuration of the git tool on Windows depends on the user, but I'm not too sure.
If you have git setup on Windows to convert LF to CRLF, running format creates a huge diff even though nothing really changed. If we set tsfmt to not change the line endings, then that will make it simpler here but could make us end up with a bunch of bad line endings.
I'm wondering if we could configure our git repo to automatically do the conversion and not worry about it in tsmft?
The text was updated successfully, but these errors were encountered: