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

coilysiren-pull-all skip-on-dirty is too aggressive #51

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

Originally filed by @coilysiren on 2026-05-15T01:06:54Z - https://github.com/coilysiren/infrastructure/issues/164

Symptom - 2026-05-14 04:43 run skipped 29/30 repos as "working tree dirty" and only pulled infrastructure. Almost certainly the same catalog-block.py canonical-sync drift that has been sitting uncommitted across multiple repos.

Why this matters - Daily pull-all is supposed to keep kai-server checkouts current. When it skips ~all repos for weeks at a time, kai-server diverges silently from origin and the user-facing surface (daily routines, repo-recall, etc.) runs against stale code.

Options

  • Detect the specific "regenerated canonical drift" case (e.g. only files matching a known canonical-sync allowlist) and git checkout -- them before pulling.
  • Or use git stash + git stash pop around the pull.
  • Or fall back to git pull --autostash with a final dirty-check.

Related to the missing auto-commit step in coilyco-ai's apply-catalog-block-hook (separate issue, coilyco-ai sweep).

_Originally filed by @coilysiren on 2026-05-15T01:06:54Z - [https://github.com/coilysiren/infrastructure/issues/164](https://github.com/coilysiren/infrastructure/issues/164)_ **Symptom** - 2026-05-14 04:43 run skipped 29/30 repos as "working tree dirty" and only pulled infrastructure. Almost certainly the same catalog-block.py canonical-sync drift that has been sitting uncommitted across multiple repos. **Why this matters** - Daily pull-all is supposed to keep kai-server checkouts current. When it skips ~all repos for weeks at a time, kai-server diverges silently from origin and the user-facing surface (daily routines, repo-recall, etc.) runs against stale code. **Options** - Detect the specific "regenerated canonical drift" case (e.g. only files matching a known canonical-sync allowlist) and `git checkout --` them before pulling. - Or use `git stash` + `git stash pop` around the pull. - Or fall back to `git pull --autostash` with a final dirty-check. Related to the missing auto-commit step in coilyco-ai's apply-catalog-block-hook (separate issue, coilyco-ai sweep).
coilysiren commented 2026-05-30 05:43:33 +00:00
Author
Owner
Copy link

Merged into #4 in the 2026-05-29 backlog burn-down. pull-all skip-on-dirty duplicate of #4 Reopen if it should stand alone.

Merged into #4 in the 2026-05-29 backlog burn-down. pull-all skip-on-dirty duplicate of #4 Reopen if it should stand alone.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dispatch/issue-294
tangled-knot
dispatch/issue-216
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
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#51
No description provided.