Concurrency: cancel-pending parameter?

Current implementation of concurrency cancels all the pending workflow instances of the same concurrency group when a new workflow (of the same concurrency group) is started.

Is it possible to keep them in pending state and let them run one by one? It is usefull if you want to serialize deployments but don’t want to have some of them skipped because of this.

4 Likes

Same issue for us, I commented with our use case here: How to limit concurrent workflow runs - #48 by jasperroel

4 Likes

We have the same issue. We need our GitHub workflows to run sequentially but the default behaviour of the concurrency parameter is to cancel the previous pending workflows.

Same here, seems like Pending only works with one workflow and cancel the others…