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
{{ message }}
This repository was archived by the owner on May 15, 2021. It is now read-only.
In the scenario when the CI system is saturated and workflows get scheduled, auto cancel does not work as it only checks for in-progress runs that were created before the current run. The runs don't get canceled as long as the future workflow runs are in the queued state.
Describe the solution you'd like: 考えうる解決方法
It would be good to have an option to cancel all workflows but the latest one for a given workflow id. This can either be a default behaviour or can be enabled using a flag.
The text was updated successfully, but these errors were encountered:
Please describe your suggestion: 提案の概要
In the scenario when the CI system is saturated and workflows get scheduled, auto cancel does not work as it only checks for in-progress runs that were created before the current run. The runs don't get canceled as long as the future workflow runs are in the queued state.
Describe the solution you'd like: 考えうる解決方法
It would be good to have an option to cancel all workflows but the latest one for a given workflow id. This can either be a default behaviour or can be enabled using a flag.
The text was updated successfully, but these errors were encountered: