Skip to main content
November 4, 2026
The Paradime and GitLab logos side by side, with the text Paradime + GitLab
Paradime now connects to GitLab directly, the same way it does with GitHub. A GitLab connection is a Paradime bot that receives merge request and comment events from your projects. It is the base for the native Turbo CI, on-merge runs, Lineage Diff, HTTPS clones, and DinoAI reviews in this release. Go to Settings > Integrations and pick GitLab for gitlab.com, or GitLab Self-Managed for your own instance (GitLab 16.0 or later). You can also connect from the repository step when you create a workspace.
  • Install in one step. Choose Install for me and Paradime creates a paradime service account and the webhooks. Give it access with Sign in with GitLab as an Owner of the top-level group (gitlab.com), or with a one-time api token. Paradime keeps neither. You can also choose Use my own bot and paste a token with the api and write_repository scopes. See Connect GitLab on gitlab.com.
  • GitLab Self-Managed. Enter your instance URL, and optionally a separate sign-in URL and a CA certificate for a private CA. Paradime registers its OAuth application on your instance, so people can link their GitLab account. See GitLab Self-Managed.
  • Every field explained. Each install page lists every field, what to enter, and where to find it in GitLab, with links to GitLab’s own docs.
  • Check the connection. Each connection has a health card with its state, the token expiry, and the state of each webhook. Paradime checks every connection each day, and a Maintainer bot repairs webhooks that GitLab disabled. See Connection health.
  • The token rotates by itself. On GitLab 17.9 or later, Paradime rotates the bot token when 80% of its lifetime has passed, so it doesn’t expire. See Token rotation.
Shipped in Paradime v6.24.0.