Forum Discussion

AntoineW's avatar
AntoineW
Super User
3 months ago
Solved

Git Branch Feature Question

When branching to a new workspace in Fabric, I understand that I need to be admin of that target workspace, and that developers need to be contributors in their feature branch workspace.

However, I’m trying to clarify the following point:
👉 Can developers merge into the main branch without having permissions on the main workspace?

I don't need them to modify the main workspace.

  • Hi AntoineW ,

     

    Merging branches can take places only in Azure Devops or GitHub. We cannot merge branches in Fabric Workspace. 

    However possibilities are there if your developers has access to main branch and have access to create workspace.

     

    Best practice is,

    Developers should have access to feature branch only.

    Developers should not have access to create workspace.

    Via Approved PR only code should be merged to main branch. PR approval access should be restricted to authorized users.

     

    Regards,

    Srisakthi

  • Hello AntoineW,

    Yes, they can.

    Merging doesn’t happen in Microsoft Fabric. It happens in your Git repo.

    So even if a developer has zero access to the main workspace, they can still merge into main if they have the right Git permissions.

    What matters:

    • Permission to create and complete pull requests in the repo
    • Branch policies (if you’ve set them)

    What doesn’t matter:

    • Access to the main Fabric workspace

    In most setups I’ve seen, teams actually keep devs out of the production workspace and rely fully on PRs + branch policies for control.

    Docs:

    Key point: Fabric controls the workspace. Git controls the merge.

2 Replies

  • Hi AntoineW ,

     

    Merging branches can take places only in Azure Devops or GitHub. We cannot merge branches in Fabric Workspace. 

    However possibilities are there if your developers has access to main branch and have access to create workspace.

     

    Best practice is,

    Developers should have access to feature branch only.

    Developers should not have access to create workspace.

    Via Approved PR only code should be merged to main branch. PR approval access should be restricted to authorized users.

     

    Regards,

    Srisakthi

  • Hello AntoineW,

    Yes, they can.

    Merging doesn’t happen in Microsoft Fabric. It happens in your Git repo.

    So even if a developer has zero access to the main workspace, they can still merge into main if they have the right Git permissions.

    What matters:

    • Permission to create and complete pull requests in the repo
    • Branch policies (if you’ve set them)

    What doesn’t matter:

    • Access to the main Fabric workspace

    In most setups I’ve seen, teams actually keep devs out of the production workspace and rely fully on PRs + branch policies for control.

    Docs:

    Key point: Fabric controls the workspace. Git controls the merge.