From fcfa05fc4187f134673ca5a2a0a9e77a0b21bc7f Mon Sep 17 00:00:00 2001 From: "Vincent (Wen Yu) Ge" Date: Fri, 24 Jul 2026 14:44:53 -0400 Subject: [PATCH] fix(ci): concurrency group cancels the previous fleet on re-trigger No concurrency existed, so every trigger stacked a new 40-cell fleet beside the old one and mid-flight runs could only be hunted down one by one. Fleets now group by source + wizard/context-mill ref with cancel-in-progress; manual dispatches without refs fall back to the run id and never self-cancel. Generated-By: PostHog Code Task-Id: 2d43c175-646e-4d73-a974-760280c8c95b --- .github/workflows/wizard-ci.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/wizard-ci.yml b/.github/workflows/wizard-ci.yml index 66ddac978..4fd34fb10 100644 --- a/.github/workflows/wizard-ci.yml +++ b/.github/workflows/wizard-ci.yml @@ -63,6 +63,13 @@ on: repository_dispatch: types: [wizard-ci-trigger] +# One fleet per source ref: a re-trigger for the same wizard/context-mill ref +# cancels the previous mid-flight fleet instead of stacking beside it. Manual +# dispatches with no refs fall back to the run id (never self-grouped). +concurrency: + group: wizard-ci-${{ github.event.client_payload.source || 'manual' }}-${{ github.event.client_payload.wizard_ref || inputs.wizard_ref || github.run_id }}-${{ github.event.client_payload.context_mill_ref || inputs.context_mill_ref || '' }} + cancel-in-progress: true + jobs: # ============================================================================ # DISCOVER: Find and select apps to run