My main build workflow consits of about 15 actions. Any of these actions can fail leading to the fail of whole workflow. Putting the same failure handling to every action is not always possible especially when using some 3d party public actions. Besides that, the failure handling itself is not a single step. It contains of 5 actions. For that reason I would like keep the Failure handling separeted and bundeled as its own workflow consisting of multiple actions. I would like that the "failure workflow" gets triggered whenever "main build workflow" fails (due to failure of any of its actions) Or even more broadly I would like to chain workflows. So that sencond one kicks of when the first is finished. I hoped to use "check_suite event" as a trigger, but this did not work out for some reason :(
... View more
Assuming I have a repository with and two github actions workflows. (1st workflow consists of about 15 actions, 2nd workflow consists of 5 actions) The first one is triggered "on push" The second one should trigger after first one fails or succeds to do some side work (i.e. send notifications, create report etc). Especially interesting is the failure case. I have tried to set "on ="check_suite"" for the second workflow. But it does not get triggered. (When I query explecitely the check-suites API, I see the updated information about runs, but I need a trigger on that) I should be missing something basic concept here...
... View more