Databricks Free Edition GitHub push fails with "Resolver error"

[wilsonz3]

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]

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]

@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.