Feature Requests

The requires tag in workflows really limits what is possible. Requires makes a lot of sense for the deployment scenario used to demo it, but waiting for a group of jobs to complete (pass or fail) should be an option. Scenario: Setup -> Run multiple sets of tests in parallel -> Combine test results/coverage results/artifacts and report to PR That scenario above isn’t possible because if a single test fails in any of the jobs running in parallel the the fan-in step won’t run. CCI-I-344

The Workflows results page (perhaps as well as other pages) could differentiate between passing and failing jobs more clearly as users with red/green colorblindness may have difficulty picking out a failed red job from a list of green ones. CCI-I-803

Request to have the ability to set a workflow to trigger at the end of the pipeline. This could be used to:Perform a cleanup or teardown of resourcesEmulate sending webhook data (containing infromation about the pipeline)Trigger 3rd party integrations. CCI-I-1512

A button on the releases dashboard to cancel an active release