You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new commit on a pull request makes the previous run's result
irrelevant, but the runners keep going: pushing three commits in quick
succession earlier today left nine Spack legs building a superseded
commit for close to two hours.
Add a concurrency group to the seven workflows that run on
'pull_request'. Cancellation is limited to that event, so pushes to
'main' and 'release' still finish -- the Spack workflow populates the
build cache from them, and a cancelled run skips those push steps.
Merge queue runs are unaffected: they carry a
'refs/heads/gh-readonly-queue/...' ref, so they form their own group, and
'cancel-in-progress' is false for anything that is not a pull request.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments