What causes GIT_REPOSITORY_NOT_FOUND?

The remote repository URL was changed, renamed, or deleted in GitHub/GitLab/Azure DevOps. The personal access token or OAuth credential used for Git integration has been revoked. The Repos folder was created under a user account that no longer exists in the workspace

How do I fix GIT_REPOSITORY_NOT_FOUND?

Step 1: Navigate to Repos > your folder and verify the remote URL still exists in the Git provider.. Step 2: In User Settings > Git Integration, regenerate or replace the personal access token.. Step 3: Remove and re-add the Repos folder, or update the remote URL via the Repos API.. Step 4: For jobs using a Git source, open the job definition and re-select the repository and branch.

High severityconfiguration

Power BI Refresh Error:
GIT_REPOSITORY_NOT_FOUND

What does this error mean?

Databricks cannot locate the remote Git repository when checking out code for a job or Repos folder, usually due to a deleted repo, wrong URL, or revoked credentials.

Common causes

1The remote repository URL was changed, renamed, or deleted in GitHub/GitLab/Azure DevOps
2The personal access token or OAuth credential used for Git integration has been revoked
3The Repos folder was created under a user account that no longer exists in the workspace

How to fix it

1Step 1: Navigate to Repos > your folder and verify the remote URL still exists in the Git provider.
2Step 2: In User Settings > Git Integration, regenerate or replace the personal access token.
3Step 3: Remove and re-add the Repos folder, or update the remote URL via the Repos API.
4Step 4: For jobs using a Git source, open the job definition and re-select the repository and branch.

Frequently asked questions

Can I use an SSH key instead of a PAT to avoid token expiry?

Yes — Databricks Repos supports SSH keys for GitHub and GitLab. Configure the key pair in User Settings and update the remote URL to use the SSH format.

Will rotating the PAT fix jobs that are already scheduled?

Yes, as long as you update the credential in Databricks User Settings before the next run. The job reads the credential at checkout time, not at schedule time.