Appearance
Auto-Deploy & Redeploys
Auto-deploy
Once a service is connected to a GitHub repo and branch, every push to that branch triggers a new deployment automatically — no separate "enable auto-deploy" step. Infrly picks up the push via a GitHub webhook within seconds and queues a fresh build of the new commit.
Pushing to a different branch than the one your service is configured for does nothing — only the configured branch triggers a deploy. Change which branch a service tracks from its settings at any time.
Manual redeploy
Click Redeploy on a service to build and deploy its current branch again without needing a new commit — useful after changing an environment variable, or just to retry a deploy that failed for a transient reason (a flaky network blip during clone, for example).
Zero-surprise rollout
A redeploy — whether triggered by a push or a manual click — never takes your service offline while the new version builds and starts. The previous version keeps serving traffic the entire time; only once the new version passes its health check does traffic switch over. If the new version never becomes healthy, the previous one is simply left running and the deployment is marked failed — nothing about a bad deploy ever takes down a service that was working before it.
This applies to Web Services (which have something to keep running) — a Static Site redeploy is a fresh build published on success; on failure, the previously published version stays live.
Watching a deploy happen
Every deployment — automatic or manual — shows up in the service's deployment history with its own live log. See Deployment & Runtime Logs.