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
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Wanna do something else, or have a question not answered here? Hop into Slack an
14
14
15
15
## How to Report Bugs or Request Enhancements
16
16
17
-
[Check out the Github issues list.](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues) Search for what you're interested in - there may already be an issue for it. Make sure to search through closed issues, too, because we often decline things that aren't a good fit for these tools.
17
+
Check out the [Github issues list]. Search for what you're interested in - there may already be an issue for it. Make sure to search through closed issues, too, because we often decline things that aren't a good fit for these tools.
18
18
19
19
If you can't find a similar issue, go ahead and open your own. Include as much detail as you can - what you're seeing now, and what you'd like to see.
20
20
@@ -24,11 +24,11 @@ When requesting new checks, keep in mind that we want to focus on:
24
24
* Performance issues or reliability risks - if it's just a setting we don't agree with, let's set that aside
25
25
* Things that end users or managers will notice - if we're going to have someone change a setting on their system, we want it to be worth their time
26
26
27
-
Now [head on over to the Github issues list](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues) and get started.
27
+
Now head on over to the [Github issues list] and get started.
28
28
29
29
## How to Write New T-SQL Checks
30
30
31
-
Before you code, check the [Github issues list](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues) for what you're trying to do - there may already be an issue for it. Make sure to search through closed issues, too, because we often decline things that aren't a good fit for these tools.
31
+
Before you code, check the [Github issues list] for what you're trying to do - there may already be an issue for it. Make sure to search through closed issues, too, because we often decline things that aren't a good fit for these tools.
32
32
33
33
If you've got a new idea that isn't covered in an existing issue, open a Github issue for it. Outline what you'd like to do, and how you'd like to code it. This just helps make sure other users agree that it's a good idea to add to these tools.
34
34
@@ -101,4 +101,5 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi
101
101
available at [http://contributor-covenant.org/version/1/4][version]
0 commit comments