From aceba439d1b5e4d1f8d755a5893953ad4166354f Mon Sep 17 00:00:00 2001 From: aszc-dev Date: Mon, 25 May 2026 18:40:18 +0200 Subject: [PATCH] ci: re-run Tier 2 on push while run-m2 label is present Tier 2 only triggered on the 'labeled' event, so a new push to a PR already carrying run-m2 never re-ran it and the M2/ANE result went stale. Add synchronize/reopened to the pull_request trigger; the existing run-m2 gate in the job 'if' keeps it from running on unlabeled PRs. --- .github/workflows/tier2.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/tier2.yml b/.github/workflows/tier2.yml index 98943f4..ccfc913 100644 --- a/.github/workflows/tier2.yml +++ b/.github/workflows/tier2.yml @@ -2,7 +2,11 @@ name: Tier 2 — M2 / ANE (self-hosted) on: pull_request: - types: [labeled] + # `labeled` fires when run-m2 is first added; `synchronize`/`reopened` + # re-run on every subsequent push while the label is present, so the + # result tracks the PR head instead of going stale. The `if` below keeps + # the run gated on the run-m2 label for all pull_request events. + types: [labeled, synchronize, reopened] schedule: # Nightly at 04:00 UTC (~05/06 in PL). Keeps the M2 path honest # without burning the runner on every PR.