Git normalised CRLF to LF when the fixtures were committed: the blob for uv/yanked/stderr.txt held 0 carriage returns where the real engine output has 6. pip and uv emit CRLF on Windows, so the adapter parsers would have been tested against line endings that never occur in production — a parser mishandling a trailing \r would pass CI and fail on every real Windows machine. TESTING section 1 makes adapter parsing the thing that must never regress, so .gitattributes marks the fixture tree -text -diff and the blobs are re-added with their true bytes. The override is listed last because later gitattributes rules win; placed before `* text=auto` it has no effect. Verified with git check-attr and by comparing carriage returns in the staged blob against the working file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
21 lines
841 B
Plaintext
21 lines
841 B
Plaintext
# NOTE: later rules win, so the general default comes first and the overrides follow.
|
|
|
|
# Repository default: normalise to LF in the blob, check out per platform.
|
|
* text=auto
|
|
|
|
# Windows-only scripts keep CRLF on checkout.
|
|
*.ps1 text eol=crlf
|
|
*.bat text eol=crlf
|
|
*.cmd text eol=crlf
|
|
|
|
# Shell scripts must keep LF even on Windows or they will not run.
|
|
*.sh text eol=lf
|
|
|
|
# Engine-output fixtures must be preserved byte-for-byte.
|
|
#
|
|
# pip and uv emit CRLF on Windows. Normalising those to LF in the blob would test the adapter
|
|
# parsers against line endings that never occur in production — a parser mishandling a trailing
|
|
# \r would pass CI and fail on every real Windows machine. docs/TESTING.md §1 makes adapter
|
|
# parsing the thing that must never regress, so: no normalisation, no diffing.
|
|
crates/pipdock-core/tests/fixtures/** -text -diff
|