GIT Integration | Allow Multiple Users to select different branches in same workspace
When using Git Integration, only one workspace is allowed to use one branch at a time. If Developer A switches branch in a workspace than it changes for Developer B as well. So, if a development team is working on what can be considered a 'Devl' workspace, they need to use the feature to 'Branch out to new workspace' option in order to not interfere or override changes that others may be doing. (A huge use case for collaborative coding in Git, it would be nice if each team member can work on their own feature branches in the same workspace...). It would be nice if the Git Integration for a given Workspace allowed for 2 different members to change to two seperate feature branches within the same workspace at the same time. Ideally, the workspace can be tied to a single branch, such as 'main', but allow multiple team members branch off of main to development on seperate feature branches at the same time. The Git Commit and Pull Request process would still allow for versioning and change management, this would eliminate the need for multiple workspace creations, deletions, access management, and in the case of Power BI Semantic Model Data Source URLS it would not 'break' the lineage for power bi reports as the current Branch out to new workspace feature does.
3 Comments
- LKDataRegular VisitorPerhaps different GIT branches could each be tied to a Fabric Workspace folder?
- Mauro89
Super User
I guess this is currently supposed to be as designed. Imagine you would like to „connect“ to a workspace for outside of Fabric e.g. via API. How would you distinguish between any number of branches connected to the workspace? We solved the challenge with branching out and getting a mess of workspaces that every developer has one feature workspace where every new branch is connected to. - yaronprigal
Microsoft Employee
Hi, we recently released a new ability to commit to another branch, will be interesting to see if it somehow ease your way of work. https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAzure%2Ccommit-to-git#commit-changes-to-git
Recent ideas
Feature Request: Add a Warning Prompt Before Deleting Tables That Contain Measures
Problem Statement: In Power BI, measures are linked to specific tables. When a developer deletes a table from the model view or report view, Power BI automatically deletes all measures assigned to ...Murtaza_Ghafoor1 hour agoSuper UserNew4Views0likes0CommentsCustom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON2 hours agoNew MemberNew7Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi4 hours agoMicrosoft EmployeeNew21Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull225 hours agoAdvocate INew31Views1like1Comment