Connect GitHub and deploy from your repository

Connecting your GitHub account lets strackt browse your repositories, pull your code, and — if you want — deploy automatically every time you push. You connect once, and from then on every application your team adds can pick a repository from your account.

Connect your GitHub account

Choose Connect GitHub and authorize the access GitHub asks you to approve. strackt needs permission to read your repositories and to set up deployments on them. Once you approve, GitHub sends you back to strackt and your account shows as connected.

You only do this once per team. After that, GitHub appears as an available source whenever anyone on your team adds or configures an application.

What strackt sets up for you

When you link a repository to an application, strackt prepares everything it needs to deploy from it — you don't manage any of it by hand:

• It adds a read-only deploy key to that repository on GitHub, so it can pull your code. The key is read-only — strackt can never push to your repository.
• It sets up a webhook so it knows the moment you push new code.

You don't create or copy SSH keys, and you don't configure anything on GitHub yourself — strackt does it the instant you link the repository.

Deploy automatically on push

With auto-deploy turned on, pushing to your application's configured branch deploys it automatically — no need to come back to strackt and trigger a deploy. Push to a different branch and nothing happens; only the branch your application tracks triggers a deploy.

Prefer to deploy on your own schedule? Turn auto-deploy off, and strackt only deploys when you ask it to.

If setup didn't finish

If strackt couldn't finish setting up the deploy key or the webhook — for example, GitHub temporarily refused the request — your application shows a Setup incomplete badge on its deployment settings, with a short message describing what went wrong. Read the message, address it, and retry. Once setup succeeds (or you disconnect the repository), the message clears on its own.

Disconnect

Disconnecting removes strackt's access cleanly: it revokes the read-only deploy key and removes the webhook from your repository on GitHub, so nothing is left behind on your account.

What to do next

• Ready to add an application from a connected repository? See Add and deploy an application.
• Want to understand what happens on each deploy? See How deploys work.