-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add include-on-hold option to treat on-hold workflows as running in queue #13
Conversation
Thanks for the submission! I will run it through a test tomorrow and if it works we can merge it in! |
My bash incompetence is showing, went ahead and fixed those shellcheck errors :) |
Your development orb has been published. It will expire in 30 days. |
@tkoft will you try to test out the preview orb #13 (comment) and let us know how it goes? I also have allowed forks to run CI now so let's see if there are any additional changes that will kick off CI. |
@tkoft , have you been able to verify this works as expected? |
Your development orb has been published. It will expire in 30 days. |
1 similar comment
Your development orb has been published. It will expire in 30 days. |
Your orb has been published to the CircleCI Orb Registry. |
Manual approval jobs in CircleCI often are used to block workflows. This change prevents later workflows from running while a previous one is still on hold for manual approval.
For pipelines that just need to ensure jobs don't run concurrently and don't care what order workflows finish in, this option is by default set to false (the current behavior).