I’ve been trying to come up with a solution for this on and off for the past couple weeks. Based on my experience I came up with two ideas but it would require help from GitHub. 1. It seems like it would be great if an action was allowed to run regardless if the action it depended on succeeded or failed. If something like this we’re possible i believe we could have a simple deployment status action that sends the update based on the status of the previous actions, but allowing that would obviously be a flag/option the user enables. 2. Since the workflow is kicked off on deployment events maybe GitHub should fire back the deployment status per action automagically for us. If an action succeeds fire a success action, but if one fails fire off a failure. What do you think about those? I personally like #2 because it just seems cleaner to not have your workflow with a bunch of status actions. Also, in your case your actions don’t have to worry about firing off deployment statuses they just do their job. I also wonder how we can send a request like that in for consideration?
... View more