cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Databricks Repos are pushing all changes to GitHub

Simmy
New Contributor II

When I make any changes within a repo, when I go to commit and push to GitHub if I uncheck any changes that I don't want pushed, still get pushed to Github. Any help would be appreciated

3 REPLIES 3

Anonymous
Not applicable

@Andrew Simpson​ :

If you are using the Databricks Repos feature to push changes to a GitHub repository and are experiencing issues with changes being pushed even after you have unchecked them, there are a few things you can try to resolve this issue:

  1. Ensure that you have unchecked the correct changes: When you make changes to files within a Databricks Repo, the changes are automatically staged for commit. If you want to exclude specific changes from being committed, you need to uncheck those changes in the "Commit Changes" dialog. Make sure that you have unchecked the correct changes and that you have clicked on the "Commit" button to save your changes.
  2. Verify your Git configuration: Databricks Repos uses Git to interact with GitHub. Ensure that you have configured Git correctly on your local machine, and that your local Git client is using the correct GitHub credentials to push changes to the remote repository.
  3. Try using Git command-line tools: If you continue to experience issues with Databricks Repos, try using Git command-line tools to push changes to your GitHub repository. This can help you identify any issues with the Databricks Repos integration and allow you to push changes more reliably.

Hope one of the above helps! Please let me know if further questions.

Anonymous
Not applicable

Hi @Andrew Simpson​ 

Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help. 

We'd love to hear from you.

Thanks!

Simmy
New Contributor II

Hi @Vidula Khanna​ 

Problem is now resolved thanks, didn't have to do anything different, the functionality just started working as expected.

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.