Highdocs
Deploy/Git & auto-deploy

Git & auto-deploy

Connect a repository once and every push can build and deploy itself — no CI pipeline to wire up.

Connect a private repo

A public repo needs nothing. For a private one, connect it one of two ways depending on its URL:

  • SSH (git@…) — generate a deploy key and add the public half to your repo as a read-only deploy key. The private half stays on the hub.
  • HTTPS — configure credentials: a username and a personal access token. The token is write-only; High never hands it back.

Turn on the webhook

Enable the push webhook and High gives you a receiver URL and a secret. Paste both into your git provider's webhook settings for push events. That's the only wiring step.

Auto-release a branch

Point a stage at a branch and successful builds of that branch release to it automatically. Track main on dev for push-to-deploy on your default branch, keep prod manual, or track a release branch — whatever matches how you ship.

{
  "tool": "generate_deploy_key",
  "arguments": { "projectId": "p-acme" }
}
# add the returned public key to the repo as a read-only deploy key
{
  "tool": "enable_git_webhook",
  "arguments": { "projectId": "p-acme" }
}
# paste the returned URL + secret into your provider (push events)
{
  "tool": "set_auto_release",
  "arguments": {
    "stageId": "s-dev", "enabled": true, "ref": "main"
  }
}

✓ pushes to main now build and deploy to dev
Push to deploy

Once the webhook is on and a stage tracks a branch, a push runs the whole pipeline — build then release — in the same phases a manual deploy shows. A build that fails never releases, so a bad commit can't take a stage down.