@judoole Thanks for open sourcing github-deploy - it's been really helpful to get our Slack + GitHub Actions + AWS Beanstalk deployments rolling. I've blogged about it 👉https://getslashdeploy.com/blog/slack-deploy-github-actions-aws/ check it out!
Thanks @assimovt, that was a nice write up as well!
On my todolist is todo a write up of my findings as well. Now I have a great blogpost to reference :)
I ended up solving a very similar problem to this when building deliverybot (https://deliverybot.dev). This is the repo that I'm using to deploy to firebase from actions and set the correct deployment status: https://github.com/deliverybot/status.
It doesn't try and automatically wrap anything just builds on top of `if` statement functionality in GitHub actions basically. If the previous state was `failure()` then we push a failure status.
Nice @colinjfw !
We've rewritten the status action as well. Decided to use shell over node. Because I don't particularly like that commiting of the node_modules https://github.com/unacast/actions-github-deployment-status.