[jitl]

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.

(I didn’t watch the video)

[awenix]

If you are referring to https://docs.github.com/en/actions/deployment/targeting-diff..., unfortunately i haven't played with it, and agree that it does offer most of the features offered by the product. As you mentioned the differentiator is the automatic rollback and support for external monitoring (datadog as of now). Would love to learn more about how you are using Github actions so i can make the product better, if you can drop an email to hello @ nixmade.com

For Cloud API, my post have been a little confusing, was suggesting/hoping 3rd party services to integrate with open source orchestrator https://github.com/nixmade/orchestrator so they can have their own version of pippy (not Github Actions).

[1oooqooq]

same. Read the features and assumed Github Actions were already Pipelines for GitHub Actions.