Putting your Power BI reports under version control with GitHub is one of the best ways to level up your analytics workflow, especially when collaborating with a team. It moves your projects from fragile files sitting on a desktop to a robust, shareable, and trackable asset. This article will guide you through the process step-by-step, from setting up your project correctly in Power BI to pushing your first report to a GitHub repository.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Connect Power BI and GitHub?

Before we get into the "how," let's quickly cover the "why." If you've ever had a file named Sales_Dashboard_V5_FINAL_for_real.pbix, you already know the pain of manual versioning. GitHub solves this and more, turning your Power BI development into a professional, collaborative process.

True Version Control

Every change you commit to GitHub is tracked. Did a new DAX measure break three of your visuals? You can go back to the previous version with a single command. This creates a safety net, allowing you to experiment and build with confidence, knowing you can always revert to a stable state.

Better Team Collaboration

When multiple developers work on the same Power BI report, things get messy fast. "Who has the latest version?" becomes a constant question. With GitHub, your team has a single source of truth. Developers can work on different features in separate "branches" and then merge their changes back into the main project without overwriting each other's work.

Showcasing Your Work

For data analysts looking to build a portfolio, a well-maintained GitHub profile is the gold standard. It allows potential employers to see not just the final dashboard but your entire development process. They can review your code, your DAX measures, and your M queries, giving them a much deeper understanding of your skills than a simple screenshot ever could.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Getting Started: Prerequisites Checklist

To follow along, you'll need a few tools installed and ready to go. Make sure you have the following before you begin:

• Power BI Desktop: This one's a given. Ensure you have the latest version installed, as the feature we'll be using is relatively new.
• A GitHub Account: If you don’t have one, you can sign up for free at GitHub.com.
• Git Installed Locally: GitHub is the website, but Git is the version control software that runs on your computer. You need to install it from the official Git website. The installation is straightforward - just follow the default prompts.

Step-by-Step: Uploading Your Power BI Report to GitHub

With the setup out of the way, let's walk through the process of getting your report from Power BI Desktop into its own GitHub repository.

Step 1: Save Your Report as a Power BI Project (.PBIP)

This is the most critical step and the key that makes version control possible. Historically, Power BI reports were saved as .pbix files, which are monolithic, binary files that are not friendly to Git. Git can see that the file changed, but it can't see what changed inside.

Microsoft introduced Power BI Project files (.pbip) to fix this. When you save as a project, Power BI breaks the report into a folder structure containing human-readable files (mostly JSON), including a separate file for the report definition and another for the dataset definition. This is exactly what we need for effective version control.

To enable and use this feature:

1. In Power BI Desktop, go to File > Options and settings > Options.
2. Under Global > Preview features, check the box for "Power BI Project (.pbip) save option."
3. Restart Power BI Desktop.
4. Now, with your report open, go to File > Save As. In the "Save as type" dropdown, choose Power BI project file (*.pbip).

Save your project in a new folder on your computer. After saving, you'll see that Power BI has created a few files and subfolders. This is your project now, and this is what we'll be adding to GitHub.

Step 2: Create a Local Git Repository

Next, we need to tell Git to start tracking this new folder. This is done through the command line or terminal.

1. Open your terminal (on Windows, you can use Command Prompt, PowerShell, or Git Bash, which comes with Git).
2. Navigate into the folder where you saved your Power BI Project.
3. Once you are inside the project directory, initialize Git with this command:

You'll see a message like "Initialized empty Git repository." Behind the scenes, Git has created a hidden .git folder to store all its tracking information. Your folder is now a local Git repository.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 3: Create a .gitignore File (Extremely Important!)

Before you add any files, you need to tell Git what files to ignore. Power BI projects may contain user-specific layout files or cached data that you don't want to include in version control. The .gitignore file handles this.

Create a file in your project's root folder named .gitignore (exactly that name) and add the following content:

Power BI Files

*.pbix *.pbit *.auto.pbip

VS Code

.vscode/

Ignore layout files

*.pbil

Cache and other local files

.pbi/ *.Dataset/cache.abf

This simple file prevents clutter and keeps your repository clean, focusing only on the core components of your report definition and dataset.

Step 4: Create a Remote Repository on GitHub

Now, let's switch over to the GitHub website to create a home for your project where others can see it and where you can back it up.

1. Log in to your GitHub account.
2. In the top-right corner, click the '+' sign and select "New repository."
3. Give your repository a name (e.g., "power-bi-sales-report").
4. Add a brief description.
5. Choose whether to make it Public (visible to everyone) or Private (visible only to you and collaborators). For portfolios, public is best.
6. Important: Do not check the boxes to add a README, license, or .gitignore file. We have already created our own locally.
7. Click "Create repository."

GitHub will now give you a page with some command-line instructions. We're going to use these to connect our local repo to this newly created remote repo.

Step 5: Staging Files and Committing Your Changes

With everything configured, it's time to take a snapshot of your project and prepare it for upload. In Git terminology, this involves two steps: staging (adding files) and committing.

Back in your terminal (which should still be in your project's directory), run the following commands one at a time:

1. Stage all your project files:

git add .

The . tells Git to add all untracked files in the current directory (while respecting the .gitignore file you created).

2. Commit the staged files:

git commit -m "Initial commit of sales dashboard report"

A commit is a snapshot of your files at a specific point in time. The -m flag lets you provide a "commit message," which is a short description of the changes you made. Good commit messages are essential for understanding the project's history.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step 6: Pushing Your Report to GitHub

The final step is to "push" your local commits to the remote repository on GitHub.

1. First, tell your local Git repo where the remote one lives. Copy the command from the GitHub page that looks like this:

git remote add origin https://github.com/YourUsername/your-repo-name.git

Paste it into your terminal and press Enter. This links your local project to the one on GitHub, naming it "origin" by convention.

1. Finally, push your changes up:

git push -u origin main

This command sends your committed files to the "origin" remote, specifically to a branch named "main." After it finishes, you can refresh your repository page on GitHub, and you'll see all your Power BI project files there!

Ongoing Workflow

Now that your project lives on GitHub, your daily process becomes very simple:

1. Make changes to your report in Power BI Desktop and save them.
2. Go to your terminal.
3. Run git add . to stage the modified files.
4. Run git commit -m "Added new DAX measure for YoY sales" using a descriptive message.
5. Run git push to upload the changes.

Final Thoughts

Linking Power BI with GitHub transforms your analytics projects from simple desktop files into professional, collaborative assets with complete version history. By saving reports as .pbip files, you can use Git's full power to track changes, work with a team, and build a reliable portfolio of your work.

Integrating tools like Power BI and GitHub addresses a critical part of the data analysis lifecycle, especially for developers who need precise control. As analysis becomes more embedded within business operations, seeing your reports linking behind the tools that keep you organized and able to master your domain becomes essential. Consider using tools like Graphed for integration and management of your analytics processes.