Two back-to-back merges to main cancelled the first merge's deploy: the second push started a run in the same concurrency group with cancel-in-progress: true, killing the first's Deploy Agent mid-build and leaving the agent un-deployed (exactly what happened merging #146 then #147).
Fix: cancel-in-progress: ${{ github.event_name == 'pull_request' }} — stale PR CI still cancels, but main-branch deploys always run to completion.
Two back-to-back merges to main cancelled the first merge's deploy: the second push started a run in the same concurrency group with `cancel-in-progress: true`, killing the first's **Deploy Agent** mid-build and leaving the agent un-deployed (exactly what happened merging #146 then #147).
Fix: `cancel-in-progress: ${{ github.event_name == 'pull_request' }}` — stale PR CI still cancels, but **main-branch deploys always run to completion**.
Refs #118.
Two back-to-back merges to main cancelled the first merge's deploy: the second
push started a new run in the same concurrency group with cancel-in-progress,
killing the first's Deploy Agent mid-build and leaving the agent un-deployed.
Make cancellation conditional on the event being a pull_request, so stale PR CI
still cancels but main-branch deploys always run to completion.
Refs #118.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
sharang
merged commit 9e70bd1c8e into main2026-07-12 22:08:59 +00:00
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.
Two back-to-back merges to main cancelled the first merge's deploy: the second push started a run in the same concurrency group with
cancel-in-progress: true, killing the first's Deploy Agent mid-build and leaving the agent un-deployed (exactly what happened merging #146 then #147).Fix:
cancel-in-progress: ${{ github.event_name == 'pull_request' }}— stale PR CI still cancels, but main-branch deploys always run to completion.Refs #118.