Skip to main content
Each GitLab connection has a card on its integration page: Settings > Integrations > GitLab, or GitLab Self-Managed. The card shows if the connection works, and has the actions to repair it.

​
What the card shows

Paradime checks every connection each day. To check now, click Check now.

​
Connection states

When a connection is Suspended, click Reconnect with a new token and run the install again. See Connect gitlab.com or Connect GitLab Self-Managed.

​
Webhook states

​
Repairs that Paradime makes

When the bot role is Maintainer, the daily check repairs webhooks. If GitLab disabled a webhook, or the webhook is gone, Paradime creates a new webhook with a new secret and deletes the disabled one. Each repair is in the audit log. A Developer bot cannot manage webhooks, so you repair them yourself.

​
Re-install the webhooks

  1. On the connection card, click Re-install hooks.
  2. If the bot is a Developer, paste an Owner token from a project Maintainer or group Owner. Paradime uses it once to create the webhooks again, and does not store it.
If you do not paste a token, Paradime makes a new secret for each webhook. The webhooks already in GitLab stop working until you put the new secret in them:
  1. In GitLab, open each project’s Settings > Webhooks and edit the Paradime webhook.
  2. Paste the new Secret token, then save.
  3. In Paradime, click I’ve updated the hooks.
To see why a webhook failed, open the project’s Settings > Webhooks in GitLab and look at the recent events of the Paradime webhook.

​
Token rotation

Paradime rotates the bot token by itself when GitLab allows it:
  • The token needs the self_rotate scope, and GitLab 17.9 or later. Install for me adds the scope when your GitLab version supports it. For Use my own bot, add it when you create the token.
  • Paradime rotates the token when 80% of its lifetime has passed. The new token has the same lifetime.
  • Paradime saves the new token before it uses it. If the rotation fails, the connection shows Suspended only when the old token no longer works.
A token that rotates shows Rotates automatically on the card. A token that cannot rotate shows its expiry date. Thirty days before it expires, the card warns you: The bot token expires in <n> days. Click Reconnect with a new token before that date, or Turbo CI stops on GitLab. To stop workspaces from reaching a project through the connection:
  1. On the connection card, find the project and click Unlink.
  2. Select I understand, unlink this project and confirm.
Every workspace that reached the project through the connection stops cloning over HTTPS. A workspace with a deploy key falls back to it. A workspace without one is marked disconnected, and you connect it again on its Git Repository page.

​
Add another top-level group

On gitlab.com, one connection covers one top-level group. Click Install on another top-level group to connect projects in another group. Each group gets its own card.

​
Disconnect GitLab

  1. On the connection card, click Disconnect.
  2. If the bot cannot delete webhooks, paste an Owner token (optional). Paradime uses it once to remove the webhooks, and does not store it.
  3. Select I understand, disconnect GitLab and confirm.
Paradime revokes its bot token and unlinks every workspace from its project. Turbo CI, on-merge runs, and Lineage Diff stop on GitLab. Workspaces that still have a deploy key keep cloning with it. If Paradime could not remove the webhooks, it lists them with links. Remove each one from the project’s Settings > Webhooks, so GitLab stops sending events.