Your home page mostly focuses on stuff that I thought GitHub already provides. How do features like block for approval, locks, etc differ from the built in capabilities native to GitHub actions? We have a “service deploy” workflow that pauses for approval after preparing the deploy but before it’s installed on the cluster using stock actions. We also “lock” deploys without third party stuff. When it comes to “cloud api”, GitHub has an API for triggering action runs too.
Here on HN you focus on monitor + rollback after deploy, which is more of a differentiator.
Here on HN you focus on monitor + rollback after deploy, which is more of a differentiator.
(I didn’t watch the video)