Deploy on push

GitHub

Kuberns receives signed GitHub webhook events. For a push event, it extracts repository, branch, commit, compare URL, message, and committer data.

When the repository and branch match a configured environment, Kuberns:

1. Records a Git push activity.
2. Creates build history for the commit.
3. Queues the deployment pipeline.

Trial accounts are currently limited by backend policy to two processed GitHub push events per day.

Skip pushes that only change certain files

A push that only changes files such as README.md or the docs folder does not need a new deployment. List those paths as ignored paths in Settings → Advanced settings, and Kuberns skips any push where every changed file matches one of them. A push that changes any other file deploys as usual.

If the deployment leaves the app down

When you set a health check path, Kuberns requests it after each deployment. If a Git push deployment leaves the application down, Kuberns restores the previous version. You can also choose an earlier version yourself with a rollback.