Deploy a private repository
Connect a GitHub App to deploy from private repositories, manage repository access and troubleshoot missing repositories.
Private GitHub repositories deploy through a GitHub App that you install on your own account or organization. Each connection is private to the Zoophost organization that created it.
Before you start
You need permission to install a GitHub App on the repository owner — usually the repository owner or an organization admin on GitHub. In Zoophost, connecting an app requires owner or admin in the workspace.
Connect GitHub
- Console → GitHub.
- Choose Connect GitHub.
- GitHub opens with a prefilled app manifest. Review and create the app.
- Approve the callback and choose which repositories the app may access. You can grant all repositories or only selected ones.
- Back in the console, the app card shows the app name, App ID and the account it is installed for.
Use Load repositories on the app card to list what the installation can see. The list shows the full name, a private badge and a Deploy link.
Deploy from the private repository
Either:
- Click Deploy next to a repository in the GitHub list. The source step is prefilled, or
- Start New deployment → GitHub and choose the GitHub App, Repository and Branch.
Then choose a Build pack, name the app, pick a plan slot and deploy. Everything after the source step is identical to a public Git deploy.
Repository and branch selection
The Deploy link pre-fills the repository and its default branch. Branches marked default or protected in the list are the ones GitHub reports as such. You can type another branch in the deployment wizard if it is not listed.
Auto deploy
Private repositories follow the same setting as public ones: Settings → Source → Auto deploy on push. Leave it on to deploy on every push to the selected branch, or use Redeploy for manual releases.
Managing the connection
- Manage on the app card opens the app's settings on GitHub, where you can change repository access.
- Removing the app in Zoophost stops deployments from its repositories. The app remains installed on GitHub until you uninstall it there.
- Deleting or transferring the GitHub repository breaks the connection; remove and reconnect the app.
Troubleshooting
No repositories listed
- The installation may not include any repositories. Open the app in GitHub and grant access.
- The GitHub account that installed the app may not be the one that owns the repository.
- Reload the console page and use Load repositories again.
Repository listed but the build fails immediately
The app can see the repository but cannot clone the selected branch. Check the branch name and that the app still has access after any repository transfer.
“Connect GitHub” does nothing or returns an error
Pop-up blockers and corporate proxies sometimes break the manifest flow. Allow pop-ups for the console, or try a different browser.
Push does not trigger a deploy
Confirm Auto deploy on push is on and that the repository's webhook exists in GitHub. Reconnecting the app recreates it.
Next
- github app
- private repo
- deploy
- permissions
- repository
Ready to use this
Git-push containers, previews and custom domains, billed monthly in INR.
- 5 websites on the smallest plan
- Free SSL and custom domains

