> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing a repository

> Import an existing Git repository into Paradime using any valid SSH Git URL from GitHub, GitLab, BitBucket, Azure DevOps, or a self-hosted host.

Paradime imports a repository using any valid SSH Git URL that points to it. The steps below are the same for every provider; only the final step of adding the deploy key differs.

<Warning>
  You must use the `git@...` or `ssh:...` version of your git URL, not the `https://...` version. Paradime uses the SSH protocol to clone repositories, so it cannot clone repos supplied with the HTTP protocol.
</Warning>

## Import a repository

1. In Paradime, go to **Settings → Workspace**.
2. In the **Git Connections** section, click **Edit Repository**.
3. Paste your repository's SSH URL into the **Repository SSH URL** field.
4. Copy the **Deploy Key** that Paradime generates.
5. Add the Deploy Key to your Git provider with read and write access (see the provider guide below).
6. Back in Paradime, save the connection using one of the two options below.

<Info>
  Paradime generates a Deploy Key that must be added to your Git provider's repository configuration. This Deploy Key needs read and write access.
</Info>

<Note>
  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.
</Note>

## 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 anything you've already installed in your Git provider keeps working. Use it when you need to grab the same key a second time (for example, to hand it to a colleague).
* **Regenerate** creates a brand new Deploy Key and replaces the old one. Because it's a destructive action, Paradime asks you to confirm before regenerating.

<Warning>
  **Regenerating invalidates the previously generated Deploy Key.** Any copy of the old key that's already installed in your Git provider stops working immediately. If you regenerate, you must install the new key in your Git provider, otherwise the connection will fail.
</Warning>

## Save the connection

When you save, you can either test the connection right away or save it now and verify later:

<CardGroup cols={2}>
  <Card title="Test & Save" icon="circle-check">
    Paradime validates the connection and clones the repository immediately, then marks it **Verified**. Use this when the Deploy Key is already installed in your Git provider.
  </Card>

  <Card title="Save without testing" icon="clock">
    Paradime saves the repository without cloning it and marks the connection **Pending verification**. Use this when you can't install the Deploy Key yet (for example, someone else manages the provider). You can verify it later.
  </Card>
</CardGroup>

## Verify a pending connection

A connection saved with **Save without testing** stays in a **Pending verification** state, shown with an amber badge and banner in the **Git Connections** section.

<Warning>
  While a connection is pending, the [Code IDE](/products/code-ide/index), [Bolt](/products/bolt/index), and DinoAI stay inactive. Verify the connection to activate them.
</Warning>

Once the Deploy Key is installed in your Git provider:

1. Go to **Settings → Workspace**.
2. In the **Git Connections** section, click **Verify connection**.
3. Paradime checks the connection and, on success, clones the repository and promotes it to **Verified**. Code IDE, Bolt, and DinoAI activate.

If verification fails (for example, the Deploy Key isn't 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**:

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/integrations/github/connect-a-repository" horizontal>
    Add a deploy key to a GitHub repository.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/integrations/gitlab" horizontal>
    Add a deploy key to a GitLab repository.
  </Card>

  <Card title="BitBucket" icon="bitbucket" href="/integrations/bitbucket" horizontal>
    Add a deploy key to a BitBucket Cloud or Server repository.
  </Card>

  <Card title="Azure DevOps" icon="microsoft" href="/integrations/azure-devops" horizontal>
    Add an SSH key to an Azure DevOps repository.
  </Card>
</CardGroup>

<Info>
  Need to update your Git repository? See [Update connected git repository](/products/settings/git-repositories/update-connected-git-repository).
</Info>


## Related topics

- [Git Repositories](/products/settings/git-repositories/index.md)
- [Connecting a repository asynchronously](/guides/working-with-git/connecting-a-repository-asynchronously.md)
- [Connect a GitHub repository](/integrations/github/connect-a-repository.md)
- [Looker](/integrations/looker.md)
- [Update connected git repository](/products/settings/git-repositories/update-connected-git-repository.md)