Skip to content

Commit 1cfd5a5

Browse files
committed
BrentOzarULTD#1234 documentation on how to contribute to Power BI
Since it’s not a diff-able file. Closes BrentOzarULTD#1234.
1 parent d3142b6 commit 1cfd5a5

File tree

2 files changed

+21
-1
lines changed

2 files changed

+21
-1
lines changed

CONTRIBUTING.md

+11-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,17 @@ After your Github issue has gotten good responses from a couple of volunteers wh
3838

3939
Note that if you're not ready to get started coding in the next week, or if you think you can't finish the feature in the next 30 days, you probably don't want to bother opening an issue. You're only going to feel guilty over not making progress, because we'll keep checking in with you to see how it's going. We don't want to have stale "someday I'll build that" issues in the list - we want to keep the open issues list easy to scan for folks who are trying to troubleshoot bugs and feature requests.
4040

41-
### Git Flow for pull requests
41+
### Contributing Changes to Power BI
42+
43+
Power BI files are binary files that don't work well with Git source control. Rather than sending someone your changed Power BI files, here's what you need to do:
44+
45+
1. Make the changes on your side, test them, and make sure they work.
46+
2. In the Github issue you created above (in the How to Build Features section), add step-by-step instructions for someone else to make the same change to the master Power BI files.
47+
3. The First Responder Kit maintainers will review your changes and try to reproduce your results with the same steps. If they produce the right results, congratulations! They'll be saved permanently.
48+
49+
Why not just email your file to the maintainers? Well, lots of folks may be working on slightly different changes at the same time, and we need to be able to fold everyone's changes together at different points in time.
50+
51+
### Contributing T-SQL Code: Git Flow for Pull Requests
4252
<a name="git-flow"></a>
4353

4454
1. [Fork] the project, clone your fork, and configure the remotes:

README.md

+10
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Navigation
2222
- [sp_AllNightLog: Back Up Faster to Lose Less Data](#sp_allnightlog-back-up-faster-to-lose-less-data)
2323
- [sp_DatabaseRestore: Easier Multi-File Restores](#sp_databaserestore-easier-multi-file-restores)
2424
- [Parameters Common to Many of the Stored Procedures](#parameters-common-to-many-of-the-stored-procedures)
25+
- [Power BI Dashboard for DBAs](#power-bi-dashboard-for-dbas)
2526
- [License MIT](#license)
2627

2728
You're a DBA, sysadmin, or developer who manages Microsoft SQL Servers. It's your fault if they're down or slow. These tools help you understand what's going on in your server.
@@ -351,6 +352,15 @@ For information about how this works, see [Tara Kizer's white paper on Log Shipp
351352

352353
[*Back to top*](#header1)
353354

355+
## Power BI Dashboard for DBAs
356+
357+
[Documentation for this part of the project is currently at BrentOzar.com.](https://www.brentozar.com/first-aid/first-responder-kit-power-bi-dashboard/)
358+
359+
To contribute changes, read the [contributing guide](CONTRIBUTING.md) - there's a special section for the Power BI Dashboard since it has to be changed differently than scripts.
360+
361+
[*Back to top*](#header1)
362+
363+
354364

355365
## License
356366

0 commit comments

Comments
 (0)