Databricks Community

wilsonz3 · 4 weeks ago

Hi,

I'm using Databricks Free Edition and connected a GitHub repository through the Databricks GitHub integration.

I can clone/connect to the repository and create/edit files, but when I try to Commit & Push, Databricks returns:

Error pushing changes
Resolver error

There is no additional compiler/error message. The UI displays links to the Repos limitations and FAQs documentation.

On GitHub, the Databricks GitHub App is installed with:

Read access to metadata
Read/write access to code and workflows
Repository access set to All repositories

I also added a Git credential under my Databricks Settings, but pushing still results in the Resolver error.

Satyasai · 3 weeks ago

Hi @wilsonz3
Have you tried thes steps?

Databricks Git integration seems to be more reliable using Fine-Grained or Classic Personal Access Token rather than using the GitHub App authorization.

Go to https://github.com/settings/tokens and under Developer settings select Personal access tokens and then Tokens (classic) (or Fine-Grained).

Create personal access token with repo scope (repo:status, repo_deployment, public_repo, repo:invite, security_events).

Go to User Settings -> Linked accounts / Git integration and update your credentials:

Git provider: select GitHub explicitly

Git provider username or email: your GitHub username

Personal access token: the personal access token you have just created for GitHub.

data_pulse · 3 weeks ago

@wilsonz3

I tested this in Databricks Free Edition using the Databricks GitHub App and was able to clone, commit, push and pull successfully including a direct git push from the Git folder. So this doesn’t appear to be a general Free Edition limitation.

Databricks now supports standard Git commands from the web terminal for Git folders with CLI access. Try the below from a notebook and run it in bash mode.

%sh
cd /Workspace/Users/<user>/<git-folder>

git status
git remote -v
git branch --show-current
git push -v

Run that from the repo root, not the .git directory. Replace the git folder path in above.

git push -v may expose the actual GitHub side reason such as stale/conflicting credentials, repo authorization etc.

If no issues, should see something like below:

Also try below things and triage:

Try pushing to a new unprotected branch, not main branch.
Ensure Databricks GitHub App is authorized for that exact repository/org.
If you added both a linked GitHub account and a separate Git credential/PAT, remove the extra credential and test with one auth method only.
Delete/re-clone the Git folder in Databricks to rule out stale local repo state.
Try the same steps against a brand new GitHub repo. If that works, the issue is specific to the original repo/config.

anuj_lathi · Friday

This almost always comes down to which Git credential the push is actually using, or that credential lacking write permission. The GitHub App's repo permissions on the GitHub side aren't the problem. Installing the app on the repo doesn't authenticate you; the credential stored in Databricks does.

What I'd check, in order

1. Look at your credentials under Settings → Linked accounts

Go to your username → Settings → Linked accounts. Each Git provider has one default credential per user, and Databricks uses it for Git folder operations unless the folder specifies a different one [1]. Because you've tried several things, you likely have more than one GitHub credential, and the default may be a stale or read-only one. Note that the Databricks GitHub App allows only one linked credential [1]. Delete anything stale and keep a single credential you know is good.

2. Pin the credential on the Git folder

Open the Git folder → Git settings tab → under Git credential, pick the credential explicitly and Save [1]. This removes any ambiguity about the default.

3. Re-link or recreate the credential

If you used the GitHub app/OAuth link, approve the required permissions or re-link your GitHub account [1]. The cleanest way is to remove the credential, then Add Git credential → GitHub, and complete the OAuth flow again.

4. If you use a PAT, make sure it has write access

You can clone public repos with no credentials, but pushing needs a credential with Write permissions [1]. For a PAT:

Classic token: the repo scope.
Fine-grained token: Repository Contents: Read and write, and the token must be granted access to this specific repo.
If the repo is in an org with SAML SSO, authorize the token for SSO [1].

5. Set a real Git provider email

Enter your actual email in the Git provider email field. If it's blank, Databricks falls back to your username as the email, which breaks commit attribution [1]. Update it if the credential was created before that field existed.

6. Rule out workspace-side role and GitHub-side branch rules

If your workspace uses RBAC and you're acting as a group/role, the push uses the role's credential. A read-only group token can clone but can't push [1].
On GitHub, check branch protection on the branch you're pushing to. As a quick test, create a new branch in the Git folder and commit/push there. If that works, your credential is fine and a rule on main is blocking you.

Next step

In most cases, steps 1–3 fix this: one clean, default, write-capable credential, explicitly selected on the folder. If it still fails after that, switch to a PAT with the scopes above as a diagnostic. If the PAT pushes successfully, the problem is in the OAuth/app link rather than your repo or workspace. Also run through the Git folders errors and troubleshooting page [2], since the "Resolver error" message itself gives you very little to go on.