I'm not sure that Developer is the right section for this but since it spans both desktop, service and the issue with collaborating with other developers on Power BI i thought it was the best fit.
We're a small developer team working on a Power BI Pro project. We're saving our reports as pbip and use git for version handling of code. It works really well, we can work on the same report and merge code in decent way without to much extra work. A big step forward compared with Power BI out of the box in terms of collaborating with other report makers in Power BI Desktop.
However, now we're also constructing a pipeline in Azure Devops so that the reports are autmatically published when a new commit is made and now we run into a problem. For the pipeline to work the Power BI files need to be in the pbix format and for efficient version handling we want to save them as pbip.
I know the common answer to this problem is to enable git integration in the Power BI Service, which would require a Premium license. I'd like to know what other Pro license developers working in teams do to solve this problem?
The best solution I can think of is that a developer making a change to a Power BI report both have to save it as a pbip file, for version handling, and a pbix file, for auto deploy to workspace. But should this really be necessary?
