Metadata-Version: 2.4
Name: gitpowerdash
Version: 0.1.0
Summary: Git analytics specifically for Power BI projects
Requires-Python: >=3.12
Requires-Dist: pandas>=2.3.3
Requires-Dist: typer>=0.21.0
Description-Content-Type: text/markdown

1. get_git_commits.sh  
2. get_git_files.sh

Run these in that order. However, there is a small detail to keep in mind regarding **where** you run them.

Since your scripts are currently sitting in `~/dev/gitpowerdash`, running them there will only give you the history of your *dashboard project itself*. If you want to analyze a different, larger project (the one the C-Suite actually cares about), you should copy these scripts into that project's root folder first.

### The Execution Steps

1. **Make them executable:**
Before running, you need to give your system permission to treat them as programs:
```bash
chmod +x get_git_commits.sh get_git_files.sh

```


2. **Run the Commits Script:**
This creates the "Header" or "Fact" table.
```bash
./get_git_commits.sh

```


3. **Run the File Changes Script:**
This creates the "Line Item" or "Granular" table. This one might take a few seconds longer because it’s doing a deep dive into every file change.
```bash
./get_git_files.sh

```



---

### Understanding the Data Connection

Once those run, you will see `commits_fact.csv` and `file_changes_fact.csv` in your folder.

In Power BI, you are going to link them using the **SHA** column. In Git terms, the SHA is the "Unique Transaction ID."

### Pro-Tip for your README

Since you are documenting this, you might want to update your `README.md` to explain the **Relationship Model** so anyone else using your template knows how to hook up the data.

**Would you like me to show you the specific Power Query (M) "Join" logic to merge these, or are you comfortable handling the relationship in the Power BI Model View?**
