Skip to content

ci: give each push to main its own concurrency group - #103

Merged
thatsrue merged 1 commit into
mainfrom
chore/ci-concurrency
Nov 21, 2026
Merged

thatsrue merged 1 commit into
mainfrom
chore/ci-concurrency

Conversation

@thatsrue

Copy link
Copy Markdown
Collaborator

What changed

  • .github/workflows/ci.yml: the concurrency group was ci-${{ github.ref }} for every run. It is now ${{ github.event_name == 'pull_request' && format('{0}-{1}', github.workflow, github.head_ref) || github.run_id }}: pull request runs share a group per workflow and branch (and still cancel older runs, as cancel-in-progress already did), and every other run, a push to main included, gets a group of its own.

Why

With one ci-refs/heads/main group, a run queued behind another push to main was replaced by the next one, so that commit never got a CI result. 3 CI runs on main ended cancelled this way (between 2026-10-24 and 2026-10-31). The repository standards say pull request runs share a group per workflow and pull request, and that other runs get their own group "so a run on main is never replaced" ("CI", splitleafhq/.github docs/repo-standards.md).

No issue: ci.

How you checked it

  • actionlint .github/workflows/ci.yml: 0.

  • scripts/check through the pre-push hook: exit 0 (35 s).

  • A bug fix comes with a test that fails without it

  • Docs match how it works now

  • No secrets or private information

@thatsrue
thatsrue merged commit 8ac797e into main Nov 21, 2026
5 checks passed
@thatsrue
thatsrue deleted the chore/ci-concurrency branch November 21, 2026 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant