You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(ci): duplicate edit and push runs leave cancelled required checks that block merges #597
Commit Lint and Public Contract Impact run on edited (Public Contract Impact also on labeled and unlabeled) and cancel in-progress runs in a shared concurrency group. When a push and a pull-request body or title edit arrive together, both events start a run on the same head SHA and one of them is cancelled. The cancelled run leaves cancelled check runs for required contexts next to the successful ones.
PR #594 stayed BLOCKED on 2026-10-07 with every required context green: runs 37629187643 (Commit Lint) and 37629187310 (Public Contract Impact) had been cancelled on head 4a792cc. Re-running only those two runs turned the merge state CLEAN. Which of two same-named check runs GitHub treats as current is not documented; the re-run result is the evidence.
It is not a one-off. From 2026-09-15 to 2026-10-07, 9 of 11 cancelled Commit Lint runs and 15 of 20 cancelled Public Contract Impact runs had a run of the same workflow on the same SHA started within 30 seconds. Workflows without edited (Zsh, CodeQL, Trunk, ZD Integration) had none.
Change
Keep the edited and label triggers, because Validate PR Title, Validate Issue Link and the contract label policy need them, but stop these two workflows from producing cancelled runs of required contexts. Both finish in well under a minute, so cancellation saves almost nothing. Set cancel-in-progress: false so a newer event queues behind the running one instead of cancelling it.
Impact: Medium. Any pull request whose body or title is edited around a push can be blocked; re-running the cancelled runs is the workaround.
Effort: XS. Two workflow files change.
Priority: P2 - Medium. It blocks merges intermittently, and the body counts 24 of 31 cancellations with a same-SHA twin.
Workstream: Human delivery.
Status: In Review. PR ci: stop cancelling required-check runs on pull request edits #600 is merged into next (43f6e93): commit-lint.yml and public-contract-impact.yml have no concurrency group, so neither cancels a run. The issue closes when next is promoted to main.
Activity
ci: stop cancelling required-check runs on pull request edits
ci: stop cancelling required-check runs on pull request edits
ci: stop cancelling required-check runs on pull request edits
ss-o commentedon Oct 8, 2026
Project 28 triage. Values set on this issue:
Bug. Cancelled runs of required contexts kept a pull request blocked while the same contexts had passed (fix(light): load classic zi light without tracking #594, evidence in the body).Medium. Any pull request whose body or title is edited around a push can be blocked; re-running the cancelled runs is the workaround.XS. Two workflow files change.P2 - Medium. It blocks merges intermittently, and the body counts 24 of 31 cancellations with a same-SHA twin.Human delivery.In Review. PR ci: stop cancelling required-check runs on pull request edits #600 is merged intonext(43f6e93):commit-lint.ymlandpublic-contract-impact.ymlhave no concurrency group, so neither cancels a run. The issue closes whennextis promoted tomain.github-actions commentedon Oct 8, 2026
Released to
mainby promotion #617; the fix merged intonextin #600.