Skip to main content
To move a workspace to another repository, disconnect the current repository, then connect the new one. You can pick any provider and any method for the new repository: the GitHub App, a GitLab connection, or a deploy key.
Until you connect the new repository:
  • All Bolt schedules fail, and their alerts fire on every failed run.
  • The Code IDE stops working, and developers lose access to the dbt™ models.
Do this when no Bolt schedule is due to run.

​
Disconnect the current repository

  1. Go to Settings → Git Repository.
  2. On the Repository card, click Change repository.
  3. Read the impact list, type disconnect, and confirm.
When you disconnect, Paradime:
  • Clears the workspace’s repository settings: the repository URL, the provider, the dbt™ project path, the default branch, the schedule deployment branch, and the connection method.
  • Regenerates the deploy key. The current key stops working immediately.
  • Writes an entry to the audit logs.
Your company’s GitHub App installations and GitLab connections stay connected. You can pick another repository at once.

​
Connect the new repository

After the disconnect, the page shows the connect steps again. Choose your provider and how Paradime connects:
If you use a deploy key, you need the new key. The old key stopped working when you disconnected. Remove the old key from the previous repository’s deploy keys.

​
Switch the connection method only

To keep the same repository and change only how Paradime reaches it, you do not need to disconnect. On a GitHub workspace, use the banner on the Git Repository page to switch between the deploy key and the GitHub App. See Switch an existing workspace to the GitHub App.