From 9524d4bf4f43efd35b07208e71f11104da619e15 Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Tue, 23 Jun 2026 22:34:19 -0700 Subject: [PATCH] Key merge-bot concurrency on PR number, not github.ref The pull_request_target switch (#201) changed github.ref from the PR merge ref to the base branch, so the concurrency group serialized every bot PR against a base into one queue - delaying auto-merge/disable when multiple Dependabot/codegen PRs are open. Key on github.event.pull_request.number so each PR's events still process in arrival order while different PRs run concurrently. Surfaced by Copilot on the NxWitness re-sync (#448). Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/merge-bot-pull-request.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/merge-bot-pull-request.yml b/.github/workflows/merge-bot-pull-request.yml index 8795208..85d3b0e 100644 --- a/.github/workflows/merge-bot-pull-request.yml +++ b/.github/workflows/merge-bot-pull-request.yml @@ -11,10 +11,11 @@ on: pull_request_target: types: [opened, reopened, synchronize] -# `cancel-in-progress: false` is required so events process to completion in arrival order: a follow-up -# synchronize must not cancel an in-flight `opened` run before it enables auto-merge. +# Per-PR group: under `pull_request_target` `github.ref` is the base branch, which would serialize every bot PR +# against that base; key on the PR number so each PR's events queue independently. `cancel-in-progress: false` so a +# follow-up synchronize doesn't cancel an in-flight `opened` run before it enables auto-merge. concurrency: - group: ${{ github.workflow }}-${{ github.ref }} + group: ${{ github.workflow }}-${{ github.event.pull_request.number }} cancel-in-progress: false jobs: