core-lead/molecule-core
1
0
Fork 0
forked from molecule-ai/molecule-core
Code Pull Requests Activity

chore(gitattributes): pin LF on snapshot golden files

Browse Source 
Self-review follow-up on #2258 (registry snapshot tests, just merged).

The byte-exact snapshot comparisons in test_platform_tools.py would
fail mysteriously on a Windows contributor's machine with
core.autocrlf=true: checkout would convert LF → CRLF, the test would
fail locally with no useful diagnostic, and the regen instructions
in the test-file header would produce LF files that disagree with
the working copy.

Pin workspace/tests/snapshots/*.txt to text eol=lf so this can't
happen. All three current snapshots are already LF; the attribute
ensures it stays that way.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Hongming Wang 2026-04-28 21:01:44 -07:00
parent 0f50c5889b
commit 9d7bb58374
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.gitattributes vendored
View File

@ -13,3 +13,11 @@ workspace/entrypoint.sh text eol=lf
# but keep LF for consistency across platforms. # but keep LF for consistency across platforms.
Dockerfile text eol=lf Dockerfile text eol=lf
*.dockerfile text eol=lf *.dockerfile text eol=lf
# Snapshot golden files — workspace/tests/snapshots/*.txt is consumed by
# byte-exact comparisons in test_platform_tools.py. A Windows contributor
# with auto-CRLF=true would otherwise convert \n → \r\n on checkout, the
# snapshot tests would fail mysteriously locally / pass in CI (or vice
# versa), and the regen instructions in the test-file header would
# produce LF files that disagree with the working-copy CRLF versions.
workspace/tests/snapshots/*.txt text eol=lf