ci: don't cancel-in-progress for main-branch runs (only pull_request) #152

Merged
sharang merged 1 commits from fix/ci-concurrency-no-cancel-main into main 2026-07-12 22:08:59 +00:00
Owner

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 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.
sharang added the infrastructure label 2026-07-12 21:59:12 +00:00
sharang added 1 commit 2026-07-12 21:59:12 +00:00
ci: don't cancel-in-progress for main-branch runs (only pull_request)
CI / Check (pull_request) Successful in 6m31s
CI / Detect Changes (pull_request) Has been skipped
CI / Deploy Agent (pull_request) Has been skipped
CI / Deploy Dashboard (pull_request) Has been skipped
CI / Deploy Docs (pull_request) Has been skipped
CI / Deploy MCP (pull_request) Has been skipped
b83cb45ccb
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 main 2026-07-12 22:08:59 +00:00
Sign in to join this conversation.