...
You’ll need to create an Azure project if you don’t already have one. After you’ve made a project, create an Azure Repo then clone it to your local machine. Add/save your .pbip files to the repo you just cloned. Make sure to move all the folders that came with the .pbip file as well, not just the .pbip report file by itself.
Proceed to setup dev/test/prod branches as you normally would using whatever Git interface you prefer. It may be a good idea to do At this point I would recommend doing an initial push of the .pbip file(s) to a branch and then Azure then use the GUI to initiate a pull request(s) to dev/test/prod. From there you can use your preferred Git interface as you normally would to pull/push branches from/to Azure. I have not run into any abnormalities here yet that make it any different from a normal Git workflow.
2 Connecting PBI Workspaces to Git
...
4 Paginated Reports
Unexplored.
5 GitHub Version Control
Released silently by Microsoft in August 2024. Currently a WIP in exploring.