Forum Discussion
Best practice for Git integration for multiple workspaces
Which is the best architecture from ADO repository for a Fabric scenario with multiple workspaces? We have one workspace por lakehouses, one for dataflows, one for notebooks and one for reports. And both duplicated for each environment (DEV and PRO), that is, we have 8 workspaces.
I've seen in the documentation how to manage Git integration for one workspace, having one main branch for the workspace and creating new branches to apply the updates, to finally pull the changes into main.
In our case is like each workspace should be a different main branch, because we hace the artifacts in separated workspaces. How can this be managed?
Hello amaaiia ,
Note that when connecting a workspace, you not only specify the branch, but also a folder. I suggest to simply create a folder for each workspace. then, within each branch you'll have the 4 folders connected to it, without no need to manage multiple 'main' branches.
5 Replies
Hi amaaiia ,
Thanks for using Fabric Community.
I hope this document might help you - Working with Microsoft Fabric Git integration and multiple workspaces - Kevin Chant (kevinrchant.com)Yes, I already had in mind this post before posting my question. But here is refering multiple workspaces to creating one workspace to perform changes and then merging both workspaces (the new tmp one and then main one).
My situation is different, I have multiple workspaces with different information. All of it is about the same project, it's just that due to permission managing I'm separating each artifact type into different workspaces.
Hello amaaiia ,
Note that when connecting a workspace, you not only specify the branch, but also a folder. I suggest to simply create a folder for each workspace. then, within each branch you'll have the 4 folders connected to it, without no need to manage multiple 'main' branches.
