![]() ![]() ![]() (The use of CSS selectors in this description is to communicate the precise location of the erroneous element. appears next to the -modified status icon in the div.changed-file div.header when reviewing the changed file. GitHub Desktop should present the changes as normal, with no remarks about the line endings (as the LF line endings in the working copy of the file match the LF line endings of the file as recorded within the repository data).Īn -endings warning-triangle element containing a title with the content Warning: line endings have changed from 'LF' to 'CRLF'. Edit README.md to make a content change to the file in an editor that allows you to switch between CRLF and LF line endings (such as Atom, via the line-ending tile on the footer status bar). While Git normally leaves file contents alone, it can be configured to normalize line endings to LF in the repository and, optionally, to convert them to CRLF.Clone (can be from within GitHub Desktop or another Git implementation like Git for Windows).OS version: Microsoft Windows Steps to reproduce I haven't tried changing the value of core.eol: it might impact this, but the behavior with its default value of native is a bug, so whether changing core.eol changes the behavior or not isn't really relevant. Edit README.md to make a content change to the file in an editor that allows you to switch between CRLF and LF line endings (such as Atom, via the line-ending tile on the footer status bar). You will lose windows based CRLF after commit/checkout, and LF will replace it. Similarly, the opposite happens if the warning says, CRLF will be replaced by LF. This bug is not affected by the setting of tocrlf. If you use a windows machine, make modifications to the code, and do commit, it will be replaced by CRLF since git is smart and does not expect you to use LF on Windows OS. As initially noticed in #1906 (comment) and observed further in #3828, GitHub Desktop presents an erroneous warning about line endings for text files with LF line endings in the working directory. ![]()
0 Comments
Leave a Reply. |