You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,17 @@ After your Github issue has gotten good responses from a couple of volunteers wh
38
38
39
39
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.
40
40
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
42
52
<aname="git-flow"></a>
43
53
44
54
1.[Fork] the project, clone your fork, and configure the remotes:
Collapse file: Documentation/sp_Blitz Checks by Priority.md
0 commit comments