Forum Discussion
Notebook Git Binding Not Autobinding
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.
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 workspace
Once 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.