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_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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