Connect GitHub and deploy a repository

GitHub is the most convenient way to deploy on DployHub. Once your account is connected you can pick any repository you have access to, including private ones, and every push to the chosen branch can build and deploy automatically to staging.

Connect your GitHub account

1. 1

   Start a new app

   Go to Apps, then New app (/portal/apps/new).

2. 2

   Choose GitHub as the source

   Select GitHub and click Connect your GitHub account. You are sent to GitHub to approve access and then returned to the form.

3. 3

   Pick a repository and branch

   Choose the repository from the list and the branch you want to deploy, for example main. Pushes to this branch trigger deploys.

4. 4

   Finish the app

   Leave "Figure it out for me" selected or pick a build type, name the app, choose resources and create it.

How auto-deploy works

When you create an app from GitHub we register a push webhook on the repository. Each push to the app branch starts a build and deploys the result to staging. The commit hash and commit message are recorded with the deployment, so the Deployments tab shows exactly which change is running.

Auto-deploy is on by default for GitHub apps. You can switch it off in the app Settings if you prefer to deploy manually with the Deploy button. If you want every successful staging deploy to reach live without pressing Go live, turn on auto go-live in Settings.

Monorepos and subfolders

If the app lives in a subfolder of the repository, set Folder with your app to that path, for example apps/web. Detection, the build and the Dockerfile path are all relative to that folder. See Build settings for every field.

A typical workflow

1. Work on a feature branch and open a pull request as usual.
2. Merge into the app branch. The push triggers a build and a staging deploy.
3. Open the staging address and check the change.
4. Press Go live. The exact image from staging is promoted to live in seconds, with no rebuild.

Troubleshooting

• Repository missing from the list: make sure the connected GitHub account can access it.
• Push did not deploy: check that the push was to the app branch and that auto-deploy is on in Settings.
• Build failed after a push: open the deployment in the Deployments tab to read the build log, then see Build failed.

Still stuck? Raise a ticket and attach the app and the deployment so we see the status and recent logs straight away.