Native Git Integration in Power BI Desktop using PowerShell (Developer Mode for PBIP projects)
With the introduction of the PBIP (Power BI Project) format, Power BI has taken a huge step toward modern development workflows, including proper version control and CI/CD practices.
However, today the Power BI Desktop experience still lacks native support for source control operations, forcing developers to rely on external tools such as VS Code, GitHub Desktop, or command-line Git. While functional, this breaks the development flow and raises the barrier for adoption of version control among Power BI users.
Proposed idea: Developer Mode with native Git actions
When a report is opened in PBIP format, Power BI Desktop could expose a new “Developer” tab in the ribbon, focused on version control and automation.
This tab could offer simple, guided actions such as:
View repository status (current branch, modified files)
Stage changes (equivalent to git add .)
Commit changes, with a popup to enter the commit message
Push changes to the remote repository
All actions could be implemented internally via PowerShell, which is already a first-class Microsoft technology and a natural fit for Windows-based enterprise environments.
Why PowerShell?
PowerShell is native to Windows and widely adopted by IT, data, and DevOps professionals
It allows controlled, secure execution of Git commands
It avoids the need to embed a full terminal UI, keeping the experience simple and safe
Optionally, Power BI Desktop could also expose a sandboxed PowerShell console scoped to the PBIP project folder, for advanced users who want deeper automation without leaving the tool.
Benefits
Dramatically improves developer productivity
Encourages Git adoption among Power BI users
Reduces context switching between tools
Aligns Power BI Desktop with modern development IDEs
Complements existing Git integration in the Power BI Service / Fabric
This approach keeps Power BI approachable for non-technical users while unlocking a first-class development experience for advanced and enterprise teams.
Thank you for considering this suggestion.
1 Comment
- peterg0417
Helper III
Hell yes to this!! This is the biggest barrier to my workflow right now. I'd love to pop open a report, make some edits, and right in PBI Desktop create a new branch with those edits that's ready to be merged with main. Branch folders could even be organized based on File name, so all you have to add is "/general-updates" or something to that effect.
Recent ideas
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI depl...akonda7 hours agoNew MemberNew5Views0likes0CommentsIncrease or Make Configurable the Power BI Browser Tab Limit (Currently 20 Items)
Power BI users frequently work across multiple reports, dashboards, semantic models, notebooks, and Fabric artifacts simultaneously. The current browser limitation of 20 open Power BI/Fabric items re...sharadmahajan10 hours agoRegular VisitorNew339Views21likes3CommentsAdd "NO SELECTION" default selected option to slicers
Scenario Currently, slicers have two states: No value selected (bogs report down) BI dev preselects one or more data values (problematic when reports are consumed by other clients/users) Option...arpost12 hours agoPost ProdigyNew8Views0likes0Comments