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
Add "Collapse all / Expand all" to the Queries pane in Power Query Editor
Hi Fabric Community, I suggest adding a "..." menu beside Queries(n])with Collapse all and Expand all. Current state: With many queries, every group and Helper Queries folder is expanded. My 8...DataVitalizer1 hour agoSuper UserNew6Views0likes0CommentsAdd Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit2 hours agoNew MemberNew3Views0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit2 hours agoNew MemberNew2Views0likes0CommentsAdd Centralized Health, Freshness Monitoring, and Alerts for OneLake Shortcuts
Microsoft Fabric should provide a centralized health-monitoring experience for OneLake Shortcuts across workspaces and data sources. As organizations adopt OneLake Shortcuts at enterprise scale, hun...mourakshit2 hours agoNew MemberNew3Views0likes0CommentsAdd Schema Compatibility Policies and Breaking-Change Detection to Fabric Event Schema Registry
Fabric Event Schema Registry should support configurable schema compatibility policies so teams can safely evolve event contracts without breaking downstream Eventstreams, Eventhouse ingestion, appli...mourakshit2 hours agoNew MemberNew2Views0likes0Comments