Skip to main content
Connect a GitHub repository to Paradime using an SSH deploy key. Once connected, Paradime can read and write files in your dbt™ project so you can develop in the Code IDE, run schedules in Bolt, and use CI/CD.
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.
We advise creating a service account user in your GitHub account like paradime.github.maintainer@yourcompany.com with admin access to the repository, and letting this user own the deploy key. GitHub shows whoever owns the key as the person who pushed every branch from Paradime (see the FAQ below).

​
Add the deploy key

  1. In Paradime, import your repository using its SSH URL to generate a deploy key. See Importing a repository.
  2. In GitHub, navigate to the Deploy keys tab of your repository’s settings page.
  3. Give the key a name and paste in the deploy key generated by Paradime.
  4. Check the Allow write access checkbox, then save the key.
After adding this key, Paradime can read and write files in your dbt™ project.
Configuring a GitHub deploy key
For more detail, see GitHub’s guide on managing deploy keys.

​
FAQ

​
Why does GitHub show one person pushing every branch from Paradime?

Paradime pushes to your repository with the workspace’s deploy key. That covers the pushes you make from the Code IDE and the pushes DinoAI makes, in the Code IDE or as an agent. GitHub credits every push made with a deploy key to the person who added the key to the repository. If a teammate added the key from their own GitHub account, GitHub shows them as the person who pushed every branch from Paradime. Commits are not affected. Each commit keeps the name and email of the person who made it in Paradime, or DinoAI for agent sessions. GitHub also treats that person as the pusher in branch protection. If your branch protection requires approval of the most recent reviewable push, their approval doesn’t count on those pull requests. To show a service account instead, have the service account add the same deploy key again:
  1. In Paradime, go to Settings → Git Repository and copy the deploy key.
  2. In GitHub, open the Deploy keys tab of your repository’s settings page and delete the Paradime key.
  3. Sign in to GitHub as the service account, add the deploy key again, and check the Allow write access checkbox.
The service account needs admin access to the repository, because only admins can add deploy keys. Paradime can’t reach the repository between steps 2 and 3, so do this when no Bolt schedule is due to run. Each workspace has its own deploy key, so repeat these steps for each workspace.