TempsTemps
On this page
  1. Before you start
  2. Connect GitHub
  3. Connect GitLab
  4. Confirm the connection
  5. Troubleshooting

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).
  • A GitHub or GitLab account with access to the repositories you want to deploy.

Open your Temps dashboard, and in the sidebar click Git Providers, then Add Git Provider. Choose GitHub or GitLab and follow the matching section below.

Connect GitHub

You have two methods. The GitHub App is recommended — it uses fine-grained permissions and enables webhook-triggered deployments. Use a personal access token only for quick setups.

  1. On the Add Git Provider screen, choose GitHub, then click Create GitHub App.
  2. Your browser is redirected to GitHub.com (same tab).
  3. GitHub asks which repositories Temps may access — choose All repositories or Only select repositories.
  4. Click Install & Authorize.
  5. GitHub redirects you back to Temps automatically.
  6. The Git Providers page now lists your provider with status Active.

Not redirected within ~10 seconds? Switch back to the Temps browser tab — the connection is often already established. Reload the Git Providers page and check the status.

To change which repositories Temps can see later, go to github.com/settings/installations → Configure → Repository access.

Method 2: Personal access token

  1. Generate a token at github.com/settings/tokens.
  2. Choose a classic token and check the repo scope (the entire checkbox, not individual sub-items).
  3. Copy the token.
  4. Back in Temps, on the Add Git Provider screen choose GitHub → Personal Access Token, paste the token into the Token field, and click Connect.

Fine-grained tokens also work — grant Contents: Read & write (and Webhooks: Read & write if you want push-triggered deploys) on the repositories you intend to deploy.

Connect GitLab

  1. On the Add Git Provider screen, choose GitLab.
  2. Self-hosted GitLab? A GitLab Instance URL field appears — enter your base URL, e.g. https://gitlab.yourcompany.com. Leave it as https://gitlab.com for GitLab SaaS.
  3. Generate a personal access token at gitlab.com/-/user_settings/personal_access_tokens (or the equivalent path on your self-hosted instance) with the api and read_repository scopes.
  4. Paste the token into the Token field and click Connect.

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.

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 steps 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 above.

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.

Can I connect both GitHub and GitLab? Yes — add each provider separately on the Git Providers page. You can also connect multiple accounts of the same provider.

Was this page helpful?