From d822488db6f79dabd911eae5d20dc760ef476198 Mon Sep 17 00:00:00 2001 From: Rene Floor Date: Tue, 15 Sep 2026 12:00:12 +0200 Subject: [PATCH] ci(repo): key the PR title workflow's concurrency group to the PR MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Under `pull_request_target`, `github.ref` is the *base* branch, not the PR. Every PR targeting master therefore shared the concurrency group `PR is Conventional and Semantic-refs/heads/master`, and since the workflow sets `cancel-in-progress: true`, opening or pushing to any one PR cancelled the in-flight run of whichever unrelated PR happened to be running. A cancelled run reports as a failed check, so this surfaced as a red `semantic_changelog_update` on a PR that had nothing wrong with it, and cleared on a manual re-run — making it look like flake rather than a concurrency misconfiguration. Key the group off the PR number instead, matching what check_db_entities.yml already does (and reusing its comment). `github.ref` stays as the fallback for any event without a pull_request payload. The repo's other workflows are unaffected: they trigger on `pull_request` (where `github.ref` is the per-PR `refs/pull/N/merge`) or on push, schedule, and release events, where keying off `github.ref` is correct. Co-Authored-By: Claude Opus 5 --- .github/workflows/pr_title.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/pr_title.yml b/.github/workflows/pr_title.yml index 2f129ad0a6..12b763d547 100644 --- a/.github/workflows/pr_title.yml +++ b/.github/workflows/pr_title.yml @@ -10,7 +10,8 @@ on: - v9 concurrency: - group: ${{ github.workflow }}-${{ github.ref }} + # Use PR number — github.ref is the base branch under pull_request_target. + group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }} cancel-in-progress: true permissions: