Forum Discussion
PBI Git Best Practices
Hello, I’ve run into a problem with Power BI’s Git integration, or maybe with Git overall.
In our team, we use Git while working with Power BI development. We work on Power BI Desktop, commit our changes, and merge them to a Git branch called “test” that’s connected to a workspace named “Test.” If everything works fine in Test, I want to merge it to the production branch.
The problem is that if we’re working on, let’s say, two datasets in one workspace, we only want to merge the files related to that specific Datset to production. Is there a way to manage this? Or is it even possible? I looked into cherry-picking, but from what I understand, it’s for specific commits rather than specific files.
Thank you in advance, and I’m looking forward to learning how you use Git with Power BI!
2 Replies
- sangameshks
Helper I
Ensure you add only the relevant dataset files when committing changes.
- AnonymousNot applicable
The problem is not the files that are committed; the problem is that I can’t choose which files to merge into Production. This means that if two colleagues are working on different datasets in one workspace, I have to merge both changes into Production, even if I only want to merge one of them.