DEPLOYMENTS

Automatic deployments on git push

Deploy on every push — no manual steps. Works with connected accounts and webhooks.

Once your website is deployed from a Git repository, Blistra can redeploy it automatically every time you push — no manual deploy button, no CI pipeline to maintain.

How it works

  1. Your Git provider sends a push webhook to Blistra.
  2. Blistra verifies the webhook signature against your website's secret.
  3. A deployment is queued — the latest commit is cloned, built and published.

If your repository is private, deployments use your saved access token or connected GitHub account automatically — see deploying a private repository.

Automatic setup — connected GitHub account

If you deployed by picking a repository after clicking Connect GitHub, Blistra registers the webhook for you during setup. Push to your default branch and watch the deployment appear — nothing else to configure.

Manual setup — any Git provider

  1. Open your website in the dashboard and scroll to Auto-deploy.
  2. Toggle auto-deploy on — a unique webhook secret is generated automatically.
  3. Copy the webhook URL shown on the same card.
  4. In your repository settings, add a webhook:
    • GitHub: Repo → Settings → Webhooks → Add webhook. Content type application/json, secret = your webhook secret, event = Just the push event.
    • GitLab: Project → Settings → Webhooks. Enable the Push events trigger, secret token = your webhook secret.
    • Bitbucket: Repository → Settings → Webhooks → Add webhook, trigger = Repository push.
  5. Push a commit — a new deployment appears under Deployments within seconds.
The webhook secret proves the request really came from your repository. Keep it private — you can regenerate it at any time from the auto-deploy card, but you'll need to update the webhook on your Git provider afterwards.

Details

  • Only push events trigger deployments — pull requests, comments and other events are ignored.
  • Deployments clone your repository's default branch at the latest commit — or a different branch if you set a deploy branch under Settings → Deploy options. Pushes to any other branch are ignored.
  • If your app lives in a subdirectory of the repository (e.g. a monorepo), set base directory under Settings → Deploy options — build commands and runtime detection run inside that folder.
  • Every deployment appears in your deployment history with full logs (including the deployed commit), and creates a snapshot you can roll back to.
  • Toggling auto-deploy off stops new webhook deployments; the webhook on your provider can stay (it will be refused).

Related guides

Deploying a private repository