Git Line Endings

Invoke whenever git prints an LF/CRLF warning, a diff churns whole files or shows ^M, files sit modified right after a fresh clone, or before creating a repository that will be cloned on both Windows and non-Windows machines. Diagnose the current state with git ls-files --eol — it prints index vs worktree endings per file.

warning: in the working copy of '<file>', LF will be replaced by CRLF the next time Git touches it means the file is LF on disk but the checkout policy (core.autocrlf=true with no eol attribute) would write CRLF the next time Git touches it. * text=auto alone does NOT silence it — it only normalizes the index, so the warning returns on every git add of an LF-edited file. Never "fix" this by re-saving files or suppressing warnings. Give the repo an explicit contract: