Faster workflow response / saving resources via timeout/concurrency policy #316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All the workflows normally finish within <5 minutes. If they take longer (there are several runs >30 minutes in the action history) they always fail and the causes are temporary issues with CDN / dependencies not solvable etc. There is no point then continuing those runs as they anyway fail. Thus setting an upper limit of 30 minutes to save some free Action minutes in the incubator org.
Also setting a concurrency policy for all workflows for faster PR responses when doing repeated pushes to PRs, inspired by conda.