DEPLOYMENTS

Deploying a private repository

Connect GitHub with one click, or use access tokens for GitHub, GitLab and Bitbucket.

You don't need to make your repository public to deploy it on Blistra. There are two ways to deploy private code — pick whichever fits you best.

Option 1 — Connect GitHub (recommended)

The simplest path: click Connect GitHub on the website creation screen, authorize Blistra once, and pick your repository from the list — public and private repos both appear. No tokens to copy, nothing to rotate manually.

When you deploy a connected repository, Blistra can also register the push webhook for you automatically, so every git push deploys — see automatic deployments.

What access does it request? The connection requests the repo scope so Blistra can clone your private repositories on your behalf. The token is stored encrypted and you can disconnect at any time from the create-website screen or by revoking "Blistra" under GitHub → Settings → Applications.

Option 2 — Access token

If you'd rather not connect your account (or you're on GitLab / Bitbucket), create a read-only token on your Git provider and paste it into the Access token field — it's under Private repository? on the deploy form.

Tokens are stored encrypted, used only to clone your repository during deployment, and are never shown in deployment logs or error messages.

GitHub — fine-grained personal access token

  1. Go to GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens and click Generate new token.
  2. Set a token name (e.g. Blistra deploy) and an expiry.
  3. Under Repository access, choose Only select repositories and pick the repo you're deploying.
  4. Under Permissions → Repository permissions, set Contents to Read. (Metadata read is added automatically.)
  5. Click Generate token and paste it into the Access token field.

A classic PAT with the repo scope also works, but fine-grained tokens are safer because they're limited to one repository.

GitLab — project access token or PAT

  1. On your project, go to Settings → Access Tokens (or use a personal access token from your profile).
  2. Create a token with the read_repository scope.
  3. Paste it into the Access token field.

Bitbucket — app password

  1. Go to Personal settings → App passwords.
  2. Create an app password with Repositories → Read permission.
  3. Paste it into the Access token field.

Using the token

  1. On Websites → Add Website (or the Deploy page of an existing site), choose Git repository.
  2. Paste your repository's HTTPS URL — e.g. https://github.com/you/your-repo.
  3. Expand Private repository? and paste your token.
  4. Deploy — we clone, detect the framework, build and publish.

Good to know

  • Saved for redeploys. Once a token is saved on a website, every future deploy — including automatic push deployments — uses it. You don't re-enter it.
  • Rotate anytime. Paste a new token on the deploy form to replace the saved one; leave the field blank to keep the existing token.
  • HTTPS only. We clone over HTTPS. Don't paste credentials into the URL itself — that format is rejected; use the token field instead.
  • Least privilege. Give the token read-only access to the single repository you're deploying — never your whole account.
  • Revoking. Deleting the token on GitHub/GitLab/Bitbucket stops Blistra's access immediately. Remove the saved token by deploying with a new one, or ask support to clear it.

Related guides

Automatic deployments on git push