Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
amaaiia
Helper IV
Helper IV

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?

1 ACCEPTED SOLUTION

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.

View solution in original post

5 REPLIES 5
v-gchenna-msft
Community Support
Community Support

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.

Hello @amaaiia ,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Hello @amaaiia ,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

March 2024  FBC Gallery Image

Fabric Monthly Update - March 2024

Check out the March 2024 Fabric update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Kudoed Authors