Retire StageCommit and StageCommitPush once repo.commit covers their behaviour #1489

Open
opened 2026-10-27 13:40:36 +00:00 by sam · 0 comments
Owner

Both constructors are superseded by repo.commit. Before removing them, confirm repo.commit covers the no-change close and the baseline-fixed push. Known gap: the old StageCommitPush closed the issue on BuildNoChanges even when a baseline fix was committed, while repo.commit pushes in that case. Decide which is right and record it. Update the workflow.go comments that still describe StageCommitPush as live. Done when task deadcode stops listing both.


Imported from beads archie-core-oey9f · GitHub #1725 · type task · priority P3 · created 2026-10-14

Both constructors are superseded by repo.commit. Before removing them, confirm repo.commit covers the no-change close and the baseline-fixed push. Known gap: the old StageCommitPush closed the issue on BuildNoChanges even when a baseline fix was committed, while repo.commit pushes in that case. Decide which is right and record it. Update the workflow.go comments that still describe StageCommitPush as live. Done when task deadcode stops listing both. --- _Imported from beads `archie-core-oey9f` · GitHub #1725 · type task · priority P3 · created 2026-10-14_
sam added the lowtask labels 2026-10-27 13:40:36 +00:00
sam self-assigned this 2026-10-27 13:40:36 +00:00
sam added the deferred label 2026-11-15 17:26:16 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1489