Skip to content

Keep push and manual CI runs from cancelling each other - #3

Merged
Commanderx-code merged 1 commit into
mainfrom
ci/concurrency
Sep 24, 2026
Merged

Commanderx-code merged 1 commit into
mainfrom
ci/concurrency

Conversation

@Commanderx-code

Copy link
Copy Markdown
Owner

Problem

The workflow's concurrency group was linux-packages-${{ github.ref }} with cancel-in-progress: true. Starting the arch_release dispatch on main cancelled the in-progress push run for the PR #2 merge commit (a432782), leaving it with cancelled checks. Consecutive pushes to main also cancelled each other; for example, ffa813a's run was cancelled by 0dbe328.

Fix

  • The group now includes github.event_name, so dispatch, push, tag and PR runs never share a group.
  • cancel-in-progress is on only for pull_request, where a new push supersedes the old run. Every commit on main and every tag keeps a complete result.

🤖 Generated with Claude Code

The concurrency group was keyed only on the ref, so an arch_release
dispatch on main cancelled the in-progress push run for the same
commit. Key the group on the event too, and only cancel superseded
pull request runs so main and tag runs always complete.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Commanderx-code
Commanderx-code merged commit 7555bec into main Sep 24, 2026
7 checks passed
@Commanderx-code
Commanderx-code deleted the ci/concurrency branch September 24, 2026 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant