![]() Often my coworkers use Windows and I use Mac, but other than the line endings, given there's no functional difference between CRLF and LF, it may make users lives more difficult if the line ending is all that changes but colleagues can't diff each line when there inevitably will be merge conflicts. ![]() I think this would be great if the entire team is on the same page (better for configuration) - but often developers (especially new developers or young/disorganized teams) don't even know what CRLF/LF are and this can make merge requests more challenging. This can result in the entire file having a blob difference, like -2015 +2200 line changes. In my experience, if you convert line endings to LF before it commits, this happens for the whole file. Hello, I'd like to revisit whether this is indeed the recommended thing to do (fix and commit). Clicking Fix and Commit will configure Git to just always automatically convert line endings to LF before it commits, and that's a highly recommended/standard thing to do. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |