Unbind

Deploy from GitHub

Connect a repository and deploy it on every push.

Unbind can build a repository and deploy it again every time you push.

Connect GitHub

This is done once per GitHub account or organization. Anyone can connect their own GitHub.

Start the connection

Open the command panel, pick GitHub Repo, then Configure GitHub App. You can also press Connect GitHub under Account Settings > GitHub Apps or Team Settings > GitHub Apps.

Choose who can see the repositories

  • Only me: only you can see these repositories.
  • This team: members of the team you are in can see them too.

Starting from a team's settings skips this question: the app is shared with that team. From your account settings you pick the team. You can share it with more teams later.

Pick the account

Choose Personal for your own account or Organization and type the organization's name.

Create the GitHub App

A GitHub window opens with everything filled in. Confirm it. This creates a private GitHub App that belongs to you, not to us. It can read code and metadata, and it receives push events. You can change the app's name before you confirm. Confirm within 30 minutes, or connect again.

Pick the repositories

GitHub asks where to install the app. Choose all repositories or only some. Private repositories work the same as public ones.

When the window closes you see GitHub connected.

One connection per account

A connection made for your personal account cannot see an organization's repositories. Connect the organization as well.

Manage connections

A connection belongs to the person who made it. Your avatar > Account Settings > GitHub Apps lists yours, with the accounts each one is installed on and how many services build from them.

  • Visibility: pick the teams that can use it, or Only me to take it back. A team's picker shows your own connections and the ones shared with that team. A connection shared with one of your teams does not show up in your other teams. When several teams build from the same GitHub account, share one connection with all of them instead of installing another app. System admins can also pick All teams, which includes teams created later.
  • The link on an account row opens that installation on GitHub, where you change which repositories the app can see. An app that is not installed anywhere yet links to GitHub's install page instead.
  • Open on GitHub: the app's own settings page. If you rename the app or move it to another account there, Unbind shows the change within 10 minutes.
  • Remove: uninstalls the app from every account and forgets it. Services built from it keep running but stop deploying on push until you pick a repository for them again. Delete the app itself under GitHub > Settings > Developer settings > GitHub Apps afterwards.

Team Settings > GitHub Apps lists the connections shared with the team. Team editors can Stop Sharing a connection, which takes the repositories out of the team's picker without touching the services or the other teams. System admins can also change a shared connection's Visibility from here and share it with any team.

A connection shared with All teams shows up in every team. Its teams cannot stop sharing it one by one; the person who made it or a system admin changes its Visibility instead.

When the person who made a shared connection is deleted, the connection stays with its teams. If only one team has it, that team's editors can remove it. If several or all teams do, only a system admin can.

A service whose connection is neither yours nor shared with its team shows its repository and branch, but you cannot change them. It keeps deploying on push. Ask the owner to share the connection with the service's team.

Create the service

Open the command panel, pick GitHub Repo and choose a repository. Unbind creates the service right away and looks at the code to work out the framework and the port it listens on.

From the API or an agent, list-github-repositories takes the team you build in and lists the repositories you can build there, each with the installation_id that create-service takes as github_installation_id. Connecting, sharing and removing connections stays in the UI.

Before the first deployment you can check:

  • Repository and Branch: the default branch is selected. Pick another one if you need to.
  • Domain and port: a generated domain is suggested. See Domains.
  • Variables: add what the app needs. See Variables.
  • Advanced Settings: the builder, its commands and the watch paths. See Builds.

Press Deploy.

Deploy on every push

Services created from GitHub deploy on every push to their branch. The Auto Deploy switch next to the branch turns this off, on the first deploy and later under Source > Branch in the service settings. With auto deploy off, pushes are ignored and the service only deploys when you trigger it. You can change the branch later under Source as well.

Change the repository

Under Source > Repository in the service settings you can pick any repository the GitHub App can reach. The branch resets to the new repository's default branch, so check it before you deploy. Unbind rebuilds the service from the new repository, looks at the code again to work out the framework and the port, and from then on deploys on pushes to the new repository. Earlier deployments stay in the history, but they cannot be rebuilt since their commits belong to the old repository.

Watch paths

In a monorepo you do not want every push to redeploy every service. Under Build > Watch Paths, or under Advanced Settings before the first deploy, add gitignore-style patterns. A push then deploys only when one of the changed files matches. Watch paths only apply while auto deploy is on. Over the API or MCP, send watch_paths when you create the service.

apps/web/**
packages/ui/**
!**/*.md
  • Empty list: every push deploys.
  • Order matters: the last pattern that matches a file wins, so put ! exclusions at the end.
  • Limits: up to 100 patterns, 256 characters each.

Some pushes always deploy

GitHub does not list changed files for force pushes, for a branch that was just created, or for very large pushes. Those deploy no matter what the watch paths say.

On this page