coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Wire git-lfs into the pre-commit pre-push hook #36

New issue
Closed
opened 2026-05-23 20:54:31 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:54:31 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-21T06:35:33Z - https://github.com/coilysiren/infrastructure/issues/221

Problem - infrastructure's pre-push hook is owned by pre-commit, so git lfs install cannot install its own pre-push uploader hook. Git LFS was set up in --manual mode as a workaround.

Symptom - committing an LFS-tracked file and running plain git push pushes the pointer commit but not the object. Anyone cloning then gets a pointer with no object behind it. The tower GLB commits (#215, #219) only succeeded because the objects were uploaded by hand with git lfs push.

Next:

  • Add git-lfs to the pre-commit config so the pre-push hook chains both, or merge the git-lfs pre-push line into the existing pre-commit-generated hook.
  • Verify a fresh LFS commit plus plain git push uploads objects automatically.
_Originally filed by @coilysiren on 2026-05-21T06:35:33Z - [https://github.com/coilysiren/infrastructure/issues/221](https://github.com/coilysiren/infrastructure/issues/221)_ **Problem** - infrastructure's pre-push hook is owned by pre-commit, so `git lfs install` cannot install its own pre-push uploader hook. Git LFS was set up in `--manual` mode as a workaround. **Symptom** - committing an LFS-tracked file and running plain `git push` pushes the pointer commit but not the object. Anyone cloning then gets a pointer with no object behind it. The tower GLB commits (#215, #219) only succeeded because the objects were uploaded by hand with `git lfs push`. Next: - [ ] Add git-lfs to the pre-commit config so the pre-push hook chains both, or merge the git-lfs pre-push line into the existing pre-commit-generated hook. - [ ] Verify a fresh LFS commit plus plain `git push` uploads objects automatically.
coilysiren commented 2026-06-17 08:22:55 +00:00
Author
Owner
Copy link

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:22:55 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#36
No description provided.