Forum Discussion
Notebook Git Binding Not Autobinding
Recently the option to autobind notebooks to target workspace was introduced which if enabled I would expect notebooks to take on the target lakehouses when you sync a git branch; however, this doesn't appear to be working.
I have tried:
- creating a new workspace, then attaching to git and syncing - still connected to original workspace
- branching out to new workspace selecting all items - still connected to original workspace
- branching out to new workspace, selecting only lakehouses first, then bringing in remaining items - still connected to original workspace
Yet, on existing git connected workspaces, I see metadata changes ocurring for autobinding (even this has caused irrecoverable conflicts/errors after enabling this setting).
Can anyone explain to me how this is supposed to work? I feel like the steps I've taken should have autobinded. Is there a more conveluted process to follow for this to work?
Thank you.
JJ
*Update* - When you first enable this setting, the metadata changes for each enabled notebook. It looks like you need to have an initial commit of this metadata change to your main branch before you can branch out and have it autobind. That is my working theory at this moment. The workspace connected to my main branch had shown updates to all notebooks because of this enabled git binding feature. The problem was git policies restricted my ability to commit these changes. I disabled the policies and commited all these metadata changes, reenabled my git policies and now that they are commited into main branch, branching out to a new workspace seems to autobind correctly.
Hi Jason-J ,
Thank you for reaching out to the Microsoft Fabric Community.
We were able to review the scenario you described, and your observation is correct. The Git binding setting for notebooks works based on metadata stored in the repository, and not solely on the workspace level configuration.
When the “Lakehouse in new workspace” option is enabled, Fabric updates the notebook metadata accordingly. However, this change must be committed to the main branch before it can take effect in any new workspace. If the metadata changes are not committed, subsequent workspace creations or branch syncs will continue to use the previous lakehouse binding.
Recommended approach:
Enable the Git binding setting (Lakehouse in new workspace)
Commit all resulting notebook metadata changes to the main branch
Proceed with branching or syncing into a new workspaceOnce these steps are followed, notebooks should bind correctly in the target workspace.
Please let us know if you continue to face any issues or need further clarification.Thank you.
2 Replies
Hi Jason-J ,
Thank you for reaching out to the Microsoft Fabric Community.
We were able to review the scenario you described, and your observation is correct. The Git binding setting for notebooks works based on metadata stored in the repository, and not solely on the workspace level configuration.
When the “Lakehouse in new workspace” option is enabled, Fabric updates the notebook metadata accordingly. However, this change must be committed to the main branch before it can take effect in any new workspace. If the metadata changes are not committed, subsequent workspace creations or branch syncs will continue to use the previous lakehouse binding.
Recommended approach:
Enable the Git binding setting (Lakehouse in new workspace)
Commit all resulting notebook metadata changes to the main branch
Proceed with branching or syncing into a new workspaceOnce these steps are followed, notebooks should bind correctly in the target workspace.
Please let us know if you continue to face any issues or need further clarification.Thank you.
The problem with it was once you turn on the target workspace option in a branch and commit, it doesn't actually commit metadata changes which enables this to work. That was what threw us off. It's a 2-step process.
1. Enable the option on each notebook, commit and merge into your main branch
2. In the workspace connected to main, sync down this change and the metadata will update. Commit back to main.,
This would be far simpler if when you enabled the option in the notebook, this triggers the metadata update for that notebook so it all gets commited in 1 shot back to main.
