Databricks Repos

[johann_blake]

Hi everyone!

I've set up an Azure cloud environment for the analytical team that I am part of and everythings is working wonderfully except Databricks Repos. Whenever we open Databricks, we find ourselves in the branch that the most recent person worked in, and will have to either commit or discard their changes in order to switch to our own branch. Is this expected behaviour or have I configured something incorrectly? I imagine this could become quite messy when/if we become a large team and ideally we should remain in the branch we worked in last. Have anyone else experienced this, or know where I might have done something wrong? For your information, we've connected to GitHub with the Databricks app.

Thanks in advance!

[feiyun0112]

 use a separate a Databricks Git folder mapped to a remote Git repo for each user who works in their own development branch .

Run Git operations on Databricks Repos | Databricks on AWS

[HelenDaniels]

Thanks for the link, you made my day.