TempsTemps
On this page
  1. Connect with a personal access token

Connect GitLab

Link GitLab — either GitLab SaaS (gitlab.com) or a self-hosted instance — so Temps can read your repositories and deploy on every push. Start from Connect a Git Provider if you haven't opened the Git Providers page yet.

Connect GitLab

  1. 1

    On the Add Git Provider screen, choose GitLab.

  2. 2

    For self-hosted GitLab, enter your base URL (e.g. https://gitlab.yourcompany.com) in the GitLab Instance URL field; leave it as https://gitlab.com for GitLab SaaS.

  3. 3

    Generate a GitLab personal access token with the api and read_repository scopes.

  4. 4

    Paste the token into the Token field and click Connect.

    Checkpoint: Confirm the provider status shows Active on the Git Providers page.

Connect with a personal access token

  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.

A self-hosted GitLab instance must be reachable over HTTPS — plaintext http:// is rejected so your token is never sent in the clear.

Once connected, confirm the status shows Active and continue with Confirm the connection.

Was this page helpful?