Forum Discussion
Git Workflow
Hi everyone,
Version control is essential for collaborative analytics projects.
For teams using Git with Microsoft Fabric:
How do you organize repositories?
How do you manage branching strategies?
Have you integrated Fabric with CI/CD pipelines?
What challenges did you face when multiple developers worked on the same project?
I'd appreciate hearing how your development workflow has evolved over time.
Looking forward to your recommendations.
Hi binitafulpagare,
A good approach is to keep a single Git repository as the source of truth for your Fabric solution and use workspace-level Git integration to version supported items while keeping the workspace structure intact. For reviews before merging into the main branch, use feature branches and pull requests. For deployments, pair Git integration with Deployment Pipelines to move validated changes through Development, Test, and Production. Using short-lived feature branches, descriptive commits, and a dedicated test workspace can help reduce merge conflicts and improve collaboration when multiple developers are working on the same project.
We'll keep this thread open so other community members can share their production experiences and proof-of-concept (POC) workflows that may help you evaluate different approaches.
Plan CI/CD for Microsoft Fabric Solutions - Microsoft Fabric | Microsoft Learn
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn
Source Control, CI/CD, and ALM for Fabric Data Agent - Microsoft Fabric | Microsoft Learn
Thank you.
2 Replies
Hi binitafulpagare,
A good approach is to keep a single Git repository as the source of truth for your Fabric solution and use workspace-level Git integration to version supported items while keeping the workspace structure intact. For reviews before merging into the main branch, use feature branches and pull requests. For deployments, pair Git integration with Deployment Pipelines to move validated changes through Development, Test, and Production. Using short-lived feature branches, descriptive commits, and a dedicated test workspace can help reduce merge conflicts and improve collaboration when multiple developers are working on the same project.
We'll keep this thread open so other community members can share their production experiences and proof-of-concept (POC) workflows that may help you evaluate different approaches.
Plan CI/CD for Microsoft Fabric Solutions - Microsoft Fabric | Microsoft Learn
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn
Source Control, CI/CD, and ALM for Fabric Data Agent - Microsoft Fabric | Microsoft Learn
Thank you.
Hi v-saisrao-msft,
Thank you for the detailed explanation and for sharing the Microsoft Learn resources.
Your recommendation of using a single Git repository, feature branches, pull requests, and Deployment Pipelines provides a clear and practical approach for managing Microsoft Fabric projects in a collaborative environment. I also appreciate the emphasis on using a dedicated test workspace to reduce merge conflicts before promoting changes to production.
I have one follow-up question based on enterprise-scale implementations. As the number of developers and Fabric workspaces grows, how do organizations typically organize repositories? Do they prefer a single repository for the entire Fabric platform, or separate repositories for each business domain or project to improve maintainability and reduce complexity?
I'd also be interested in hearing from other community members about their Git and CI/CD strategies for large Microsoft Fabric deployments and any lessons they've learned along the way.
Thank you again for your guidance and for encouraging further discussion.
