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
Tenant level Service Announcement option
The ability to activate a tenant wide banner which users will see when opening the Power BI service. Perhaps on the top of the screen in a blinking color to attract attention. The banner can be used...MarcoSchuiling3 hours agoRegular VisitorNew10Views1like0CommentsAdd Branch Compare Merge and Approval Workflows to Fabric Planning Scenarios
Fabric Planning supports scenarios, simulations, writeback, and collaborative planning. Enterprise planning teams also need a controlled process for developing multiple versions of a plan and promoti...mourakshit11 hours agoNew MemberNew4Views0likes0CommentsAdd Continuous Incremental Synchronization for Fabric ClickHouse Accelerated OneLake Tables
Fabric ClickHouse provides accelerated access to OneLake data for high-performance analytical workloads. For operational analytics and AI applications, a point-in-time accelerated copy can quickly be...mourakshit11 hours agoNew MemberNew6Views0likes0CommentsAdd Execution Preflight and Cost Guardrails to Fabric Data Engineering Agent
Fabric Data Engineering Agent can autonomously plan, execute, validate, and refine complex data engineering tasks. Before a long-running autonomous task starts executing against enterprise data, user...mourakshit11 hours agoNew MemberNew3Views0likes0Comments