How to switch the branches when multiple people work in same GIT Integrated Fabric workspace

[pavannarani]

Hello Everyone,

I enabled the git integration in one of our Fabric POC workspace and it synced and committed all the fabric items to azure repos as expected. 

Approach 1

Generally i thinking one approach lets assume if multiple people work on same Power BI report then our Fabric POC workspace is integrated with fabric_dev branch created in Azure Devops. So am thinking both people can create two new seperate branches (fabric_dev_1 & fabric_dev_2) by considering fabric_dev as main branch. So once they are done with their changes they can raise a pull request and merge their changes back to fabric_dev branch one by one so that we have both of their changes in fabric_dev branch later it is published to Fabric POC workspace once we click on source control and pull the latest changes so that it sync all the changes to its respective items.

As per my understanding approach 1 will work for multiple users for any fabric items.

Approach 2

I observed one thing today any way when we sync the changes from Fabric POC workspace the item changes are automatically committing to the git enabled branch in azure repos right. Till here its going good but my doubt is why do we need to push items through GIT why cant we directly do it workpsace itself as it is committing back to GIT anyway for version control -

To follow up on, 

Lets say if multiple people want to do the changes and they created their own branches in azure repos just like Approach 1 but they wont be having admin access to change/override the branch in workspace settings. Even if someone does it for them before they start doing changes, still it can be pointed to either First person branch(fabric_dev_1) or Second person branch (fabric_dev_2) right. And that too if they are done with their changes both of their changes will go into same branch only and that will become a problem and may result into conflicts if they worked on same fabric items (reports or etc.).

Here similar to Approach 1 can each user push or sync the changes to his own child branch directly from fabric workspace instead of GIT. Is this really possible using Fabric workspaces to switch their own branches for each user seperately when they are working (they will not have admin access to switch or override because admin access cannot given to all people in the team).

Can anyone suggest me i want to know how it can be done through Fabric workspaces or if it is not possible then is there any other way in workspace. At last if there is no way shall we go a head with GIT changes Approach 1 only. please share your thoughts here .

Thanks in Advance.

Regards

Pavan kumar

[v-zhouwen-msft]

Hi @pavannarani ,

I have no experience with this. But the documentation says that the best practice for Git is to have developers work independently outside of a shared workspace. By having each developer work in their own branch, you minimize the risk of conflicts and ensure that changes can be reviewed before merging back into the branch.

Git integration branches - Microsoft Fabric | Microsoft Learn

[pavannarani]

@v-zhouwen-msft 

we are using Fabric POC as shared workspace for development environment so are you saying to create seperate branch for each user and work in different workspace. Later after done with the changes shall we merge back the changes to main branch which is connected to POC workspace again.

To do that i went through the solution given in documentation branching out to workspace but am not sure how to use it. So does it mean it creates new branch with new workspace for each user seperately

Git integration branches - Microsoft Fabric | Microsoft Learn