How to Upload Power BI Project to GitHub

Saving your Power BI report as "Sales_Dashboard_V4_Final_ForRealThisTime.pbix" might feel familiar, but it's a messy way to track your work. Applying version control with a tool like GitHub transforms your Power BI files from isolated documents into a managed, collaborative project. This guide walks you through exactly why and how to upload your Power BI projects to GitHub, step-by-step.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why Use GitHub for Power BI?

At first glance, GitHub might seem like a tool exclusively for software developers. However, the principles behind it - tracking changes, collaborating, and maintaining a history of your work - are incredibly valuable for analytics and reporting. A single .pbix file is a black box, you can't easily see what changed between versions. When you integrate Power BI with GitHub, you unlock several key benefits:

• Full Version History: GitHub tracks every single change you save. If a DAX measure breaks or a visual gets deleted, you can pinpoint the exact change that caused the issue and easily roll back to a previous, working version. No more frantically trying to remember what you adjusted.
• Meaningful Collaboration: Instead of emailing files back and forth and creating conflicting copies, your team can work from a single source of truth. Teammates can work on different parts of a report simultaneously (using branches) and merge their changes together in an organized way.
• Disaster Recovery: Your local hard drive is not a backup plan. Storing your project on GitHub means there's always a cloud-based copy of your work. If your computer fails, your hard work is safe and sound.
• A Professional Workflow: Adopting version control is a standard practice in technical fields for a reason. It adds a layer of discipline and transparency to your work, making your projects more robust and easier to manage, especially as they grow in complexity.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Key: Saving as a Power BI Project (.pbip)

The main reason version control has been tricky with Power BI is the file format. The standard .pbix file is a compressed, binary file - essentially a single, opaque package. Git can store this file, but it can't understand the contents. If you change one DAX measure, Git just sees that the entire file has changed, which isn't very helpful for tracking specific updates.

This is where the Power BI Project (.pbip) format changes the game. When you save your report as a .pbip file, Power BI unbundles that black box into a folder structure of individual, human-readable text files. Your report layout is saved in a Report.json file, and your data model definitions are stored in another folder. These are plain text files that Git excels at tracking.

Now, if you change a DAX measure or update a color on a chart, Git can see the specific line of JSON code that changed. This is what makes version control truly powerful for Power BI.

How to Enable the .pbip Save Option

The Power BI Project feature is still in preview, so you may need to enable it first:

1. In Power BI Desktop, go to File > Options and settings > Options.
2. In the "Global" section, select Preview features.
3. Check the box next to Power BI project (.pbip) save option.
4. Click OK and restart Power BI Desktop.

Getting Your Workspace Ready

Before we start, make sure you have three things ready to go:

• Power BI Desktop: The latest version, with the .pbip preview feature enabled.
• A GitHub Account: If you don't have one, you can sign up for free at github.com.
• Git Installed: Git is the command-line tool that powers GitHub. Download it for your operating system from git-scm.com and follow the installation instructions.

Step-by-Step Guide: From .pbix to GitHub Commit

Ready to get started? Let's walk through the process of creating a new GitHub repository, saving your project, and pushing it to the cloud.

Step 1: Create a New Repository on GitHub

First, we need a place on GitHub to store our project. This is called a repository (or "repo" for short).

1. Log in to your GitHub account.
2. Click the + icon in the top-right corner and select New repository.
3. Give your repository a short, descriptive name, like sales-dashboard-pbi.
4. Add a brief description (optional).
5. Choose whether the repository should be Public (visible to anyone) or Private (visible only to you and collaborators). For most business reports, you'll want Private.
6. Check the box to Add a README file. This is a file where you can describe your project.
7. Click the Add .gitignore dropdown and select the PowerBI template. This is a crucial step that tells Git to ignore unnecessary files. We'll fine-tune this later.
8. Click Create repository.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Step 2: Clone the Repository to Your Computer

Now we'll bring a copy of that new repository down to your local machine. This is where you'll do your work.

1. On your repository's main page in GitHub, click the green Code button.
2. Make sure you're on the HTTPS tab, and click the copy icon next to the URL.
3. Open your command-line interface (Terminal on Mac, Git Bash or Command Prompt on Windows).
4. Navigate to the folder where you want to store your project (e.g., cd Documents/Projects).
5. Type git clone and then paste the URL you copied. It should look like this:

git clone https://github.com/your-username/sales-dashboard-pbi.git

Press Enter. Git will create a new folder on your computer named sales-dashboard-pbi containing the files from your GitHub repo.

Step 3: Save Your Report as a Power BI Project

This is where we connect Power BI to our new Git workflow.

1. Open the sales-dashboard-pbi folder that was just created on your computer.
2. Now, open your report in Power BI Desktop.
3. Go to File > Save As.
4. Navigate inside your sales-dashboard-pbi Git folder.
5. In the "Save as type" dropdown, select Power BI project files (*.pbip).
6. Give your file a name (e.g., Sales Dashboard) and click Save.

If you look inside your folder now, you won't see a single .pbix file. Instead, you'll see a small .pbip file and a folder with the same name containing your data model and report layout files.

Step 4: Commit and Push Your Project to GitHub

Your project files now exist on your computer, but Git and GitHub don't know about them yet. We need to "commit" these new files as a new version and "push" them up to GitHub.

1. In your command-line interface, navigate into your project's directory:

cd sales-dashboard-pbi

1. First, we need to "stage" all the new files. This tells Git we want to include them in our next saved version. The . stands for all new and modified files in the current directory.

git add .

1. Next, we "commit" them. This creates a snapshot of your files at this point in time. It requires a message (the -m flag) describing the change. Good messages are essential for understanding your project's history.

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

1. Finally, we "push" the commit from our local machine up to the GitHub server. origin is the default name for your GitHub remote, and main is the name of the primary branch.

git push origin main

That's it! If you refresh your GitHub repository page in your browser, you'll see all your project files there.

Your New Workflow: How to Update Your Report

Now that you're set up, your day-to-day workflow becomes a simple rhythm.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Made a Change? Here’s What You Do:

1. Open the .pbip file in Power BI Desktop and make your changes (add a visual, update a DAX formula, etc.).
2. Save your report in Power BI as you normally would.
3. Go back to your command-line terminal, which should still be in the project directory.
4. You can check what files have changed by typing git status. You'll likely see that Report.json has been modified.
5. Stage the changes for your next commit:

git add .

1. Commit the changes with a clear, descriptive message:

git commit -m "Updated YoY sales calculation and added regions chart"

1. Push your changes back up to GitHub to keep your project in sync:

git push origin main

By following this simple "edit, save, add, commit, push" cycle, you create a perfect history of every iteration of your report, all safely stored and ready for collaboration.

Final Thoughts

Bringing developer tools like Git and GitHub into your Power BI workflow is a massive upgrade. Your reports are no longer just files on a drive, they are managed projects with a full history, better collaboration capabilities, and a safety net against accidental errors. It's a more deliberate and professional way to handle your most important business data.

While mastering new tools and workflows is empowering, it also highlights the overhead that comes with traditional business intelligence. Instead of spending your time configuring repositories or learning complex reporting tools, you could be getting answers. With Graphed, we remove all that friction. You simply connect your data sources across marketing and sales, then use simple, natural language to create the dashboards you need. We automate the entire process, providing live, interactive reports in seconds so you can focus on insights, not setup.