Development record
A push to an open pull request started only some of its workflows: after b36b551ac was pushed to #904 (2026-10-10, about 22:50Z) only external-review ran, ci and attribution never triggered, and the pull request sat BLOCKED with eight of its nine required checks missing until it was closed and reopened. Nothing noticed: the checks were not failing, only absent.
A push to an open pull request started only some of its workflows: after b36b551ac was pushed to #904 (2026-10-10, about 22:50Z) only external-review ran, ci and attribution never triggered, and the pull request sat BLOCKED with eight of its nine required checks missing until it was closed and reopened. Nothing noticed: the checks were not failing, only absent.
Likely cause (2026-10-11, abcd-0b). GitHub runs no pull_request workflow while it reports a pull request as mergeable CONFLICTING (DIRTY), because it cannot build the test merge commit; pull_request_target workflows such as external-review run on the base branch and still fire. #919 and #920 showed exactly this on 2026-10-11: a body edit and a close and reopen started only external-review. A local merge of main into #919 was clean, so the conflict is probably the forge ignoring the .abcd/work/DECISIONS.md union driver, as with #902 (iss-2610110908443341; root cause iss-2609100507439414). Whether #904 was conflicting at 22:50Z on 2026-10-10 is not yet checked.
Frontmatter
| id | iss-2610110941283143 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610110941283143-a-push-to-an-open-pull-request-started.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2609100507439414A managed repository's shared append-only files conflict on nearly every merge, and abcd propagates neither of the two remedies it has already adopted for itself.
- iss-2610110908443341The implement loop arms a pull request that GitHub reports as conflicting and then waits on it in silence. #902, lane-1 of run-2610101724174688, had appended to .abcd/work/DECISIONS.md while later merges to main appended too. Local git merges that cleanly through the union driver; the forge ignores the driver, so #902 was armed but never entered the queue. For 13 hours every implement step said only 'pull request #902 is not merged yet', and the loop's rule that nothing is pushed after arming left it no way out.