Follow-up found during the July review/merge cycle.
.github/workflows/ci.yml triggers on both push and pull_request, so each push to a PR branch spawns two full CI runs on the same commit. Observed repeatedly this cycle (e.g. the same macOS leg producing one pass + one flaky fail for one commit), which doubles cost and doubles flake exposure per commit.
Proposed fix: add a concurrency group keyed on the workflow + ref with cancel-in-progress: true, and/or scope the triggers (e.g. push only on main, pull_request for PRs) so each commit runs the suite once.
Follow-up found during the July review/merge cycle.
.github/workflows/ci.ymltriggers on bothpushandpull_request, so each push to a PR branch spawns two full CI runs on the same commit. Observed repeatedly this cycle (e.g. the same macOS leg producing one pass + one flaky fail for one commit), which doubles cost and doubles flake exposure per commit.Proposed fix: add a
concurrencygroup keyed on the workflow + ref withcancel-in-progress: true, and/or scope the triggers (e.g.pushonly onmain,pull_requestfor PRs) so each commit runs the suite once.