GitLab

GitLab hosts your dbt™ repositories. Paradime connects to GitLab through a GitLab connection. The connection is a Paradime bot in your GitLab that receives merge request and comment events from your projects, and posts statuses and notes back. One GitLab connection gives you:

• CI/CD with no pipeline file. Turbo CI, on-merge runs, and Lineage Diff run on your merge requests without a .gitlab-ci.yml job or a Paradime API key.
• Repository clones over HTTPS. The Code IDE, Bolt, DinoAI agents, and dbt deps reach the project with short-lived tokens. There is no deploy key to manage.
• DinoAI agents that work as your people. An agent pushes only to its own branch, and the merge requests it opens show the person who started the session as the author.
• DinoAI Code Review and @paradime. DinoAI reviews merge requests and answers mentions in merge request comments.

​

What you can do

With a linked GitLab account, DinoAI in the Code IDE can also read, list, open, and comment on merge requests as you. Create MR with DinoAI in Git Lite opens the merge request on GitLab, and you can edit schedule and agent YAML from the Bolt UI.

​

gitlab.com or GitLab Self-Managed

Paradime has two GitLab integrations. Pick the one that matches where your projects live.

​

What the Paradime bot does in GitLab

Paradime works in GitLab through one bot user per connection:

• Install for me creates a GitLab service account named paradime, with a token named paradime. The token has the api and write_repository scopes. On GitLab 17.9 or later, it also has the self_rotate scope, so Paradime can rotate it.
• Use my own bot uses a bot user, a group access token, or a project access token that you manage.

The bot is a member of each connected project, with the Developer or Maintainer role. With that role, the bot:

• Receives Merge request events and Comments from a project webhook on each project.
• Posts commit statuses, such as Paradime Turbo CI, Paradime Lineage Diff, and Paradime Code Review.
• Posts and updates merge request notes, such as the merge run summary and the DinoAI failure summary.
• Gives Bolt runs and DinoAI agents short-lived tokens to clone the project. An agent’s token can push only to the agent’s own branch.

A Maintainer bot can also repair the project webhooks when GitLab disables them. A Developer bot cannot manage webhooks, so a project Maintainer repairs them. See Check the connection health.

​

Network requirements

• GitLab to Paradime. GitLab sends webhooks to https://api.<your Paradime region>.paradime.io/api/v1/<company token>/webhook/gitlab. For example, the US region uses the host api.us.paradime.io. If your network limits outbound traffic from GitLab, allow this host.
• Paradime to GitLab. On GitLab Self-Managed, Paradime calls your GitLab API and clones over https. If your instance is behind a firewall, allow the Paradime IP addresses.

​

DinoAI on merge requests

A DinoAI Code Review reviewer works on GitLab merge requests the same way it works on GitHub pull requests. On GitLab:

• DinoAI posts all its findings at once as one GitLab review, with comments on the changed lines.
• The Paradime Code Review commit status shows on the merge request.
• On GitLab 19.3 or later, a blocking reviewer sets its reviewer state to Requested changes when findings are open, or Reviewed when none are.

To bring DinoAI into a merge request, mention @paradime, @dinoai, or the Paradime bot’s username in a comment. DinoAI reacts with 👀, then answers in the same thread. To use a mention, you need the Developer role or higher on the GitLab project, and your GitLab account linked to a Paradime account that can run DinoAI agents in the workspace. If your account is not linked, DinoAI replies with the steps to link it. DinoAI does not answer mentions on merge requests from forks. See Mentions.

​

Set up GitLab