microsoft / microsoft/finops-toolkit
Investigate PBIX versioning options
Open
Nobody has claimed this yet.
Help wanted ✨
Tool: Power BI
Type: Cleanup
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
⚠️ Problem
PBIX files are ZIP files, which contain text files. As binary files, there's no transparency into what changed in each version.
🛠️ Solution
Investigate options that can version control PBIX (or possibly generic ZIP) files. Some options:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the listed options—zippey, powerbi-source-control, xlsx-git, and pbi-tools—for versioning PBIX or generic ZIP files. Document which options provide useful change transparency and identify a viable approach; the issue does not name project files, tests, or an entry point.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100