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
Power BI, import report and semantic model: show change connection pop-up
When you need to import an existing Power BI report and semantic model in Tenant B that's created in Tenant A, you need to jump through a number of hoops to fix the original connection. It's doable, ...Reitse29 minutes agoMost Valuable ProfessionalNew2Views0likes0CommentsEnable per-user security for shared gateway connections using service accounts
When a shared gateway connection uses a highly privileged service account, all source queries run with that account’s permissions. Users cannot see the stored credentials, but report developers who c...AshishChougala48 minutes agoMicrosoft EmployeeNew5Views2likes0CommentsRequest to add a feature to extract gateway connection status and last time credentials used
Could you please add a feature in the admin UI on Microsoft Fabric/Power BI to extract the Gateway connections with details of the gateway connection status and last activity information along with t...Vinodkumar_Chak2 hours agoNew MemberNew20Views1like0CommentsPower BI - incorrect handling of empty string parameter in DAX query in paginated report
Blank string parameters in paginated reports are treated as empty strings in Power BI Report Builder but as null values in the Power BI Service, resulting in incorrect report output. -> Create a pag...roshinikumarkar5 hours agoMicrosoft EmployeeNew25Views5likes0CommentsAllow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara7 hours agoNew MemberNew20Views1like1Comment