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
I use this action to trigger a slack notification once every job has finished in a PR workflow.
My problem is I use n1hility/cancel-previous-runs to cancel previous run attached to that PR and wait-for-status report those cancelled jobs as errors.
Can it be possible to report them as cancellation?
Hey @tbekaert that should be possible and not too hard to do. Might export it as a conclusion tho because it would be a BC break to replace failure for cancelled cases.
I just want to warn that GitHub's branch protection treats skipped and neutral statuses (that are often results of dependent job cancellation) as "not failure == success". So such an ask might be dangerous if used carelessly.
I've got some bits of explanation in another action's readme: https://github.com/marketplace/actions/alls-green#why.
Hi !
I use this action to trigger a slack notification once every job has finished in a PR workflow.
My problem is I use n1hility/cancel-previous-runs to cancel previous run attached to that PR and wait-for-status report those cancelled jobs as errors.
Can it be possible to report them as cancellation?
Here is the slack job I use, for reference:
Thanks :)
The text was updated successfully, but these errors were encountered: