Auto Deploy on Push

CI/CD

Auto Deploy on Push

5 min readUpdated August 2026

GitHub auto-deploy is configured on the project: connect the GitHub App, then enable Autodeploy on each git-backed app. A push to the connected branch starts a build and a rolling deploy. There is no deploy-hook URL to copy.

Build settings live on the app Settings tab → jump Build. The folder label is Build path, relative to the repo root. Watch rollouts on the Deployment tab. Settings changes apply when you Commit on the canvas.

Autodeploy is toggled on in the app's Build settings, a git push runs in the terminal, and the webhook rolls out the new deploy.

Deploy pipeline

git push

commit

Webhook

GitHub App

Build

image

Registry

image pushed

Rolling

deploy

Live

healthy

Build log

Deployment tab, api, commit a3f9c12

00:00 Cloning github.com/acmecorp/my-api (branch: main)

00:01 Checked out commit a3f9c12 — "feat: add rate limiting middleware"

00:02 Build path: .

00:18 Building production image...

00:41 Image built: sha256:d4e8f1a2b3c9...

00:48 Image pushed

00:49 Rolling update starting...

01:17 Deploy complete. Live: https://api.stackblaze.app

Settings → Build

Autodeploy

Deploy automatically when you push to the connected branch

Branch

The GitHub branch this app builds from

main

Build path

Build context relative to the repo root

.

Under the hood

  • Project GitHub App: connecting GitHub on the project installs the webhook. Auto-deploy is not a per-app hook URL you paste into CI.
  • Autodeploy switch: lives on Settings → Build for each git-backed app. Commit on the canvas applies the change.
  • External CI: POST /api/deployments/build/{pipeline}/{phase}/{app} with { buildstrategy, repository, reference } queues a build when you cannot rely on the git push.

Step by step

01

Connect GitHub on the project

On the phase canvas, use + Service → Git repository, then Connect Stackblaze to GitHub. That installs the GitHub App and lists repos you can deploy. GitHub auto-deploy uses this project connection — there is no deploy-hook URL.

02

Turn Autodeploy on

Open the app Settings tab and jump to Build. Confirm Repository, Branch, and Build path. Turn Autodeploy to Enabled. Commit the change on the canvas.

03

Push the connected branch

A push to that branch notifies StackBlaze through the GitHub App webhook. The control plane starts a build and a rolling deploy. Docker-image apps do not build from git — use Redeploy or change the tag instead.

04

Watch the Deployment tab

Open the app Deployment tab for the in-progress build and rollout. Logs stream as the image builds and the new revision goes live.

05

Trigger a build from CI (optional)

If you need to queue a build without a git push, POST /api/deployments/build/{pipeline}/{phase}/{app} with JSON { buildstrategy, repository, reference } and Authorization: Bearer $STACKBLAZE_TOKEN. Prefer the project GitHub webhook when you can.