[CI] Use concurrency to cancel-in-progress workflows on new commit#427
Conversation
|
BTW, looking at all the actions, it occurs to me that every commit gets tested twice? numcodecs/.github/workflows/ci-osx.yaml Lines 57 to 61 in 2ad7a12 But also when the wheel is built: numcodecs/.github/workflows/wheel.yaml Line 14 in 2ad7a12 Maybe the wheels action should use a simpler test command, like: |
|
Thanks again, @psobolewskiPhD! (Workflows launched)
MSTM. |
|
Not familiar with |
|
Sorry, "makes sense to me" :) |
thanks 😅
|
|
Gentle bump—I should have some time to return to this topic. |
|
Hey, @psobolewskiPhD. Thanks for the bump. Very appreciated.
Let's get this PR in. If you think we can fast-lane a new PR, let's do that. Otherwise, use the arm64 PR. If you would like to see this PR listed in the release notes, please feel free to add it in one of your (many) other PRs. 😄 |
This PR adds concurrency and cancel-in-progress to the CI workflows. See:
https://docs.github.com/en/actions/using-jobs/using-concurrency
What this means is if workflows are running when a new commit is pushed, they are canceled and restarted, rather than piling up.
I tested this on my fork, see: https://github.com/psobolewskiPhD/numcodecs/actions/runs/4600373158
TODO: