Skip to main content
Each workspace connects to one Git repository. You connect it on Settings > Git Repository, or in the repository step when you create a workspace. First you choose your provider, then how Paradime connects.

​
Choose your path

With the GitHub App or the GitLab connection, there is no key to manage, and each person commits and pushes as themselves after they link their account. Choose how Paradime connects shows these methods for GitHub and GitLab only when your company can use them.

​
Connect through the GitHub App

  1. Go to Settings > Git Repository.
  2. In Choose your provider, select GitHub.
  3. In Choose how Paradime connects, select GitHub App and click Continue.
  4. If the app is not installed yet, click Connect GitHub App and complete the install on GitHub. If you are not an owner of the GitHub organization, GitHub sends the request to the owners, and the page connects when they approve.
  5. In GitHub installation, select the installation that has access to your repository.
  6. In Repository, select the repository, then click Connect repository.
For the full steps, the switch from a deploy key, and pushing as yourself, see Connect through the GitHub App.

​
Connect through the GitLab connection

Your company installs the GitLab connection once. Then each workspace picks its project.
  1. If your company has no GitLab connection yet, install it:
  2. Go to Settings > Git Repository.
  3. In Choose your provider, select GitLab.
  4. In Choose how Paradime connects, select GitLab connection and click Continue.
  5. In Pick the project, select the project, then click Connect project.
For the switch from a deploy key, account linking, and how DinoAI agents work on GitLab, see Connect a GitLab repository.

​
Connect with a deploy key

Paradime can connect any repository with a deploy key, using a valid SSH Git URL. The steps are the same for every provider. Only the step where you add the deploy key differs.
For a deploy key connection, use the git@... or ssh://... version of your Git URL, not the https://... version. A deploy key works only over SSH.

​
Import a repository

  1. In Paradime, go to Settings → Git Repository.
  2. In Choose your provider, select your Git provider.
  3. For GitHub or GitLab, in Choose how Paradime connects, select Deploy key (SSH) and click Continue.
  4. In Repository, paste your repository’s SSH URL.
  5. Click Get deploy key.
  6. In Add the deploy key, copy the Deploy key that Paradime generates.
  7. Add the deploy key to your Git provider with write access (see the provider guides below), then click I’ve added the key.
  8. In Test & finish, save the connection with one of the two options below.
The deploy key needs read and write access. Paradime needs write access to push commits.
The deploy key is stable. It stays the same when you refresh or reopen the page, so you can copy it, install it in your provider, and come back later without the key changing.

​
Deploy key controls: Refetch and Regenerate

Two controls sit next to the deploy key:
  • Refetch copies the existing deploy key again. It does not change the key, so a key that you already installed in your Git provider keeps working. Use it when you need the same key a second time, for example to give it to a colleague.
  • Regenerate creates a new deploy key and replaces the old one. Because this action is destructive, Paradime asks you to confirm before it regenerates the key.
Regenerating invalidates the previous deploy key. A copy of the old key that is already installed in your Git provider stops working immediately. If you regenerate, install the new key in your Git provider, or the connection fails.

​
Save the connection

When you save, you can test the connection at once, or save it now and verify it later:

Test Connection

Paradime clones the repository and verifies read and write access with the deploy key. Use this when the deploy key is already installed in your Git provider.

Save without testing

Paradime saves the repository without cloning it and marks the connection Pending verification. Use this when you cannot install the deploy key yet, for example because someone else manages the provider. You can verify it later.
If the test fails, check that:
  • The deploy key exists on your Git provider.
  • The deploy key has write access.
  • If the repository is behind a firewall, the Paradime IP addresses are allowlisted.

​
Verify a pending connection

A connection saved with Save without testing stays Pending verification. The Repository card on the Git Repository page shows an amber badge and a banner.
While a connection is pending, the Code IDE, Bolt, the catalog, and DinoAI stay inactive. Verify the connection to activate them.
When the deploy key is installed in your Git provider:
  1. Go to Settings → Git Repository.
  2. On the Repository card, click Verify connection.
  3. Paradime checks the connection. If the check passes, Paradime clones the repository and activates it. The Code IDE, Bolt, and DinoAI start to work.
If verification fails, for example because the deploy key is not installed yet, the connection stays pending and Paradime shows an error. Install the key and try again.

​
Provider guides

Each provider has its own guide for adding the Paradime deploy key, available under Integrations:

GitHub

Add a deploy key to a GitHub repository.

GitLab

Add a deploy key to a GitLab project.

BitBucket

Add a deploy key to a BitBucket Cloud or Server repository.

Azure DevOps

Add an SSH key to an Azure DevOps repository.
To connect the workspace to a different repository, see Update connected git repository.