aszc-dev aceba439d1 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.

2026-05-25 18:40:18 +02:00

..

publish.yml

chore(publish): update GitHub Actions workflow for node publishing

2025-04-01 23:45:31 +02:00

tier0.yml

chore: slim PR to user-facing essentials

2026-05-25 18:37:04 +02:00

tier1.yml

ci(phase4): tiered test/CI infrastructure (Tier 0/1/2)

2026-05-23 23:11:35 +02:00

tier2.yml

ci: re-run Tier 2 on push while run-m2 label is present

2026-05-25 18:40:18 +02:00