Connect a Git Provider
Before Temps can deploy your code, it needs read access to your repositories. Connecting a Git provider is a one-time step — once linked, every push to a tracked branch can trigger an automatic deployment.
This is a prerequisite for creating a project from a repository. If you tried to create a project and the repository list was empty, you are in the right place — no provider is connected yet.
Before you start
You will need:
- A running Temps server and an admin account (see Quickstart).
- An account on GitHub, GitLab, Bitbucket, or Gitea (or Forgejo), or any HTTPS-accessible git server, with access to the repositories you want to deploy.
Open your Temps dashboard in a browser. This is the URL where your server is reachable — the value you set as the base URL during install (for example https://temps.yourdomain.com), or http://<your-server-ip>:8080 if you are running it directly without a domain. Log in with your admin account. In the sidebar click Git Providers, then Add Git Provider, and choose the provider you use.
Every provider URL must use HTTPS — plaintext http:// is rejected so your
access token is never sent in the clear. Put TLS in front of a self-hosted Gitea
or git server before connecting it.
Choose your provider
Pick the guide that matches where your code lives:
- Connect GitHub — GitHub App (recommended) or a personal access token.
- Connect GitLab — GitLab SaaS or self-hosted, with a personal access token.
- Connect Bitbucket — Bitbucket Cloud with an access token or app password; the webhook is registered for you.
- Connect Gitea — self-hosted Gitea, Forgejo, or Codeberg with a personal access token.
- Other Git Providers — any HTTPS git server (Azure DevOps, Gogs, SourceHut, Bitbucket Data Center, or your own) via a manual clone URL.
You can connect more than one — add GitHub, GitLab, Bitbucket, Gitea, and any number of Other Git Providers separately on the Git Providers page, and even multiple accounts of the same provider.
Confirm the connection
After connecting, the Git Providers page should show your provider with status Active. This is the signal that you are ready to deploy.
Next, head to Projects → New Project, open the Browse Repositories tab, and your repositories will appear in the list. Continue with Deploy a Project.
For an Other Git Providers connection there is no repository browser — the project uses the clone URL you entered when connecting.
Troubleshooting
The repository list is empty when creating a project. Your provider is not connected, or the connection did not complete. Return to Git Providers and confirm the status shows Active. If it shows Error or nothing is listed, reconnect using the matching provider guide above.
Status shows "Error". The token expired or was revoked, or (for the GitHub App) the redirect never completed. Remove the provider and add it again. For tokens, regenerate with the scopes listed in the provider's guide.
A specific repository is missing from the list. For the GitHub App, the installation is likely scoped to Only select repositories and that repo was not included — go to github.com/settings/installations → Configure and add it. For tokens, confirm the token's account has access to that repository.
A repository won't connect over http://.
Provider and clone URLs must be HTTPS. Put TLS in front of a self-hosted Gitea or generic git server (a reverse proxy with a certificate) and use the https:// URL.
Can I connect more than one provider? Yes — add GitHub, GitLab, Bitbucket, Gitea, and any number of Other Git Providers separately on the Git Providers page. You can also connect multiple accounts of the same provider.