Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
When using the Fabric CICD python library to deploy across environments, the best practice is to disconnect your higher environment workspaces from git. However, this makes branching out to new workspaces difficult, especially if you have a multi-workspace strategy and those workspaces are in one repository. I'm noting that I could programtically create a workspace connected to git and scoped to the correct folder using the REST APIs. That being said it would be nice if we can do this from the UI.
I'd like to propose that, when using the branch out workspace menu, that you can specifcy a Git Folder to properly scope the newly created / existing workspace to the correct subfolder. This way, if you're trigger the refresh of your feature workspace on a new branch but are doing development for a different workspace than you were previously, you can easily refresh your workspace to the correct git folder that aligns to that workspace.
Note in the screenshot below, I'm initiating this from the featue workspace.
Benefits:
- Multi-Workspace strategy where you logically group resources together becomes singiciantly easier. Folks would be less inclined to put everything into a single workspace (which has the 1000 item limit). Smaller, more modular workspaces (just like with everything else in software development) is best practice. This alligns with that mentality / approach. This involves less code for folks less comfortable with DevOps / APIs / CLIs to still leverage git and deploy functionality through environments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.