Skip to content

Add .gitattributes marking MetObjects.csv as Git LFS - #67

Open
mgajda wants to merge 1 commit into
metmuseum:masterfrom
mgajda:fix/lfs-gitattributes
Open

Add .gitattributes marking MetObjects.csv as Git LFS#67
mgajda wants to merge 1 commit into
metmuseum:masterfrom
mgajda:fix/lfs-gitattributes

Conversation

@mgajda

@mgajda mgajda commented Aug 6, 2026

Copy link
Copy Markdown

Fixes #66 — MetObjects.csv is LFS-tracked but the repo ships no filter=lfs attribute, so git lfs clone/pull silently leave the 134-byte pointer (verified on git-lfs 3.7.1).

MetObjects.csv filter=lfs diff=lfs merge=lfs -text

Verified locally: with this attribute, git lfs pull materializes the 317 MB CSV (sha256 matches the pointer oid).

Related

#63 by @aomiki (opened 2026-03-29) addresses the same root cause with a broader pattern (*.csv filter=lfs diff=lfs merge=lfs -text). This PR is the narrower single-file variant. Either resolves the issue; pick one and close the other.

Without filter=lfs on MetObjects.csv, modern git-lfs (>=3.x) cannot
discover the file, so git lfs clone/pull silently no-op and leave the
134-byte pointer in the working tree instead of the 317 MB CSV. This
restores the documented git lfs clone workflow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MetObjects.csv is LFS-tracked but no .gitattributes ships, so git lfs clone/pull silently leave a pointer

1 participant