chore: check text files out with LF on every platform
A Windows clone with core.autocrlf=true checked every text file out with CRLF, and Biome's formatter (which expects LF) then failed `npm run lint` on all 114 files before a single line had been edited. The two scripts with a `#!/usr/bin/env node` line were also unusable from WSL. `eol=lf` fixes the checkout, not the repository: the index already held LF everywhere (`git add --renormalize .` stages nothing else), and tests/fixtures/** stays -text so the CRLF records the CSV fixtures exist to exercise are untouched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3fc8fd1d5d
commit
49323d91df
1 file changed
+7
-2
+7
-2
@@ -1,5 +1,10 @@
|
||||
# Default: normalize to LF in the repo, check out native.
|
||||
* text=auto
|
||||
# Default: normalize to LF in the repo AND in every checkout.
|
||||
#
|
||||
# `eol=lf` and not "check out native": Biome's formatter (and every gate built
|
||||
# on it) expects LF, so a Windows clone with core.autocrlf=true used to fail
|
||||
# `npm run lint` on all 114 files before a single line had been edited. The
|
||||
# two `#!/usr/bin/env node` scripts are also unusable from WSL with CRLF.
|
||||
* text=auto eol=lf
|
||||
|
||||
# Fixtures are byte-exact samples of what real browsers and spreadsheets emit.
|
||||
# EOL normalization would rewrite the CRLF records in the CSV exports, so a
|
||||
|
||||
Reference in new issue
Block a user