From 9d7625c4ad0cc6680b2f6cffb3b1e40c02cf71ac Mon Sep 17 00:00:00 2001 From: Tom Boucher Date: Thu, 2 Jul 2026 08:46:49 -0400 Subject: [PATCH] ci: per-issue concurrency group for auto-label workflow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The auto-label-issues concurrency group was ${workflow}-${ref}, but for issues: events github.ref is the default branch for EVERY issue, so the group was global. With cancel-in-progress:true, a burst of new issues (each opened seconds apart) cascaded cancellations — only the last issue in the burst survived and got needs-triage; earlier ones were cancelled mid-flight and left unlabeled. Observed twice today: #1911/#1912 (nabki batch) and the #1900/#1904 epic bursts. Make the group per-issue (github.event.issue.number) so runs no longer collide across issues. cancel-in-progress is now per-issue (harmless). --- .github/workflows/auto-label-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/auto-label-issues.yml b/.github/workflows/auto-label-issues.yml index 2b19882cb..109a25c2b 100644 --- a/.github/workflows/auto-label-issues.yml +++ b/.github/workflows/auto-label-issues.yml @@ -5,7 +5,7 @@ on: types: [opened] concurrency: - group: ${{ github.workflow }}-${{ github.ref }} + group: ${{ github.workflow }}-${{ github.event.issue.number }} cancel-in-progress: true jobs: