Git LFS
Git LFS is an add-on for large files. Git stores a small pointer, while a separate LFS service stores and sends the full file.
Another example
A game project versions 300 MB binary textures on an LFS-enabled remote. Commits hold pointers and approved users download the exact files. LFS does not make changing binary files easy to merge or remove storage cost.
Main parts
- 01tracked pattern
- 02pointer file
- 03LFS object
Use it when
Use this term for chosen large binary files when both the hosting service and team process support LFS.
Do not use it when
Do not use LFS to hide generated files that should be rebuilt or to get around repository rules.
Name used in code
Git pointer ↔ LFS object store Before you ship
Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback.
Outcome: Use Git LFS to release or recover the change safely, with a clear record. User context: A game project versions 300 MB binary textures on an LFS-enabled remote. Commits hold pointers and approved users download the exact files. LFS does not make changing binary files easy to merge or remove storage cost. Delivery concept or operation: Git LFS. Why it fits: Use this term for chosen large binary files when both the hosting service and team process support LFS. Do not use it when: Do not use LFS to hide generated files that should be rebuilt or to get around repository rules. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.
Check this request
Review the current use of Git LFS. Definition: Git LFS is an add-on for large files. Git stores a small pointer, while a separate LFS service stores and sends the full file. Release checks: Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.