How to Deploy a GitHub Repository Automatically on Every Push

Manually compiling containers and triggering deploys slows down development velocity. A modern CI/CD loop should be seamless: you run git push, the platform builds your source code, scans it for vulnerabilities, runs health checks, and rolls out the upgrade.

Why Automate Deployment?

Automation eliminates "it works on my machine" deployment bugs. By connecting your source code repository directly to your hosting platform, you ensure that production always matches your main code branch precisely, complete with build logs and version controls.

Setting up GitHub Auto-Deploy on Kubeletto

1. Install the GitHub App: Authorize Kubeletto to read your targeted repository.
2. Configure the Repository: Select your repository and deployment branch (e.g., main) in the console interface.
3. Configure Build Parameters: Specify build scripts or let Kubeletto auto-detect your project dependencies using buildpacks.
4. Save and Push: Every subsequent git commit pushed to your branch enqueues a fresh build worker.

Automatic Rollbacks for Safe Releases

What happens if a push contains a bug that fails to build or crash-loops on boot? Traditional servers might go offline. Kubeletto uses a release revision queue: the old version keeps serving traffic until the new version successfully completes its startup probes. If the build or boot fails, Kubeletto halts the roll-out and keeps your active site online.