mirror of
https://github.com/pnpm/pnpm.git
synced 2026-07-14 17:52:44 -04:00
e3f2be02f0
GitHub's merge queue runs each entry on a temporary `gh-readonly-queue/**` branch, whose creation also fires a `push` event. For `ci.yml` (`on: [push, pull_request, merge_group]`) that produced two TS CI runs for the identical commit: one `push`, one `merge_group`. Both reach the reusable `test.yml`, whose concurrency group keys on `github.ref` with `cancel-in-progress: true`. Since the two runs share `github.ref`, their per-(platform, node, chunk) test jobs land in the same group and cancel each other. The Windows shards are gated only on compile-and-lint + build-pnpr, so both runs' Windows jobs start near-simultaneously and reliably collide. The `merge_group` run — the only one the queue's required `TS CI / Success` check reads — lost the race, so its cancelled test jobs failed `Success` and ejected the PR for "failed status checks". Restrict the `push` trigger to ignore `gh-readonly-queue/**` so only the `merge_group` run executes for queued commits. `pacquet-ci.yml` already scopes push to `main` and was unaffected. Apply the same `branches-ignore` to `audit.yml` to drop its redundant push run on those branches.