Choose how Paradime connects
When you connect a repository, you first choose your Git provider. For GitHub and GitLab, you then choose how Paradime connects. For a step-by-step comparison of every path, see Importing a repository.
Other providers, such as Bitbucket and Azure DevOps, use the deploy key.
The deploy key is stable. It stays the same across page refreshes until you regenerate it. A workspace on the GitHub App or the GitLab connection keeps its deploy key on file, so it can switch back to SSH at any time.
The connected repository
When a workspace is connected, the page shows a Repository card with three rows:- Provider: the Git platform, such as GitHub or GitLab.
- Connected with: the method, such as Deploy key (SSH), GitHub App with the installation it uses, or GitLab connection.
- Repository: a link to the repository.
Connect through the GitHub App
Clone over HTTPS with no deploy key, and push as yourself.
Connect through the GitLab connection
Clone a gitlab.com or GitLab Self-Managed project over HTTPS, with no deploy key.
Importing a repository
Compare every path, and connect with an SSH Git URL and a deploy key.
Update connected repository
Disconnect the workspace and connect another repository.
Supported Git providers
Paradime works with every major Git provider. Each provider has its own guide under Integrations:GitHub
Connect through the GitHub App, or add a deploy key to a GitHub repository.
GitLab
Connect gitlab.com or GitLab Self-Managed through a GitLab connection, or add a deploy key to a GitLab project.
BitBucket
Connect a BitBucket Cloud or Server repository.
Azure DevOps
Connect an Azure DevOps repository.
Don’t see your Git provider? Any provider that supports SSH deploy keys works. Contact us and we’ll help you set it up.