Skip to main content
A workspace can reach its GitLab project in two ways: Before you connect a workspace through the GitLab connection, install the connection on the project. See Connect gitlab.com or Connect GitLab Self-Managed.

​
Connect a workspace through the GitLab connection

  1. In Paradime, go to Settings > Git Repository.
  2. In Choose your provider, select GitLab.
  3. In Choose how Paradime connects, select GitLab connection and click Continue.
  4. If your company has no GitLab connection that covers the project yet, click Set up the GitLab connection. Paradime opens the GitLab integration page. Install the connection, then come back to this page.
  5. In Pick the project, select the project. The list shows only the projects that a GitLab connection reaches.
  6. Click Connect project.
Paradime clones the project over HTTPS. The Repository card then shows Connected with: GitLab connection and the project path.

​
In workspace setup

When you create a new workspace, the repository step has the same choice:
  1. Choose GitLab, then GitLab connection.
  2. If GitLab is not connected yet, choose GitLab (your projects live on gitlab.com) or GitLab Self-Managed (your company runs its own GitLab instance), and install the connection in the same step.
  3. In Pick the project, select the project and click Connect project.
A workspace that already has a repository can connect only that same project through the GitLab connection. To use a different project, click Change repository first. See Update connected git repository.

​
Switch a deploy-key workspace to HTTPS

When a GitLab connection already covers the project of a workspace that uses a deploy key, the Git Repository page shows a banner: Switch to HTTPS: the GitLab connection to <host> already covers this project.
  1. Go to Settings > Git Repository.
  2. In the banner, click Switch to HTTPS through GitLab.
The repository does not change, only how Paradime reaches it. The deploy key stays on file. To clone over SSH again, click Switch back to the deploy key in the banner.

​
What changes for the workspace

On a workspace connected through the GitLab connection, every part of Paradime uses HTTPS: To use git in the Code IDE on a workspace connected through GitLab, each person links their own GitLab account. Their commits and pushes are then made as them.
  1. Go to Settings > Integrations and open the Personal tab.
  2. On the GitLab tile, click Connect.
  3. Sign in to GitLab and authorize Paradime.
The tile then shows Connected as @<your GitLab username>. If you push from the Code IDE before you link your account, the git error has a link. The link opens a page that starts the GitLab sign-in in one click.
On GitLab Self-Managed, the GitLab tile shows only when the Paradime OAuth application is registered on your instance. See Register the OAuth application. If your company set a sign-in URL, your browser opens GitLab at that address.

​
DinoAI agents on GitLab

On a workspace connected through the GitLab connection, a DinoAI agent session works on GitLab like this:
  • The agent pushes only to its own branch, paradime/<session id>. It cannot push to main or to any other branch.
  • When the agent opens a merge request, GitLab shows the person who started the session as its author, if they linked their GitLab account. Otherwise the Paradime bot opens it. The agent never sees the person’s token.
  • The agent’s commits have DinoAI as the author and the person who started the session as a co-author.
  • The agent can read the project and its merge requests, open a merge request from its own branch, and comment on that merge request. It cannot approve, merge, or edit merge requests, or change project settings.

​
When the connection cannot reach the project

The Git Repository page tells you when a workspace loses its GitLab connection:

​
Connect with a deploy key

You can also connect a GitLab project with an SSH deploy key. If the project is also on a GitLab connection, Turbo CI, on-merge runs, and Lineage Diff still work with no pipeline. If it is not, they need a GitLab pipeline.
With a deploy key, use the git@... or ssh://... version of your Git URL, not the https://... version.
Create a service account user in GitLab, for example paradime.gitlab.maintainer@yourcompany.com, with write access to the project, and let this user own the deploy key.
  1. In Paradime, import your repository with its SSH URL to generate a deploy key. See Importing a repository.
  2. In GitLab, open your project’s Settings > Repository.
  3. Expand Deploy keys and paste the deploy key from Paradime.
  4. Select Grant write permissions to this key, then save the key.
Configuring a GitLab deploy key
For more detail, see GitLab’s guide on deploy keys.