Klectr/.github
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source
This commit is contained in:
Jesse Squires 2021-11-07 10:10:46 -08:00 committed by GitHub
parent d64b330344
commit 8e1d0732a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.md
View File

@ -20,11 +20,11 @@
## :book: Code of Conduct
Please review our [Code of Conduct](https://github.com/jessesquires/.github/blob/master/CODE_OF_CONDUCT.md). It is in effect at all times. We expect it to be honored by everyone who contributes to this project. Acting like an asshole will not be tolerated.
Please review our [Code of Conduct](https://github.com/jessesquires/.github/blob/main/CODE_OF_CONDUCT.md). It is in effect at all times. We expect it to be honored by everyone who contributes to this project. Acting like an asshole will not be tolerated.
## :bulb: Asking Questions
See our [Support Guide](https://github.com/jessesquires/.github/blob/master/SUPPORT.md). In short, GitHub issues are not the appropriate place to debug your specific project, but should be reserved for filing bugs and feature requests.
See our [Support Guide](https://github.com/jessesquires/.github/blob/main/SUPPORT.md). In short, GitHub issues are not the appropriate place to debug your specific project, but should be reserved for filing bugs and feature requests.
## :inbox_tray: Opening an Issue
@ -32,7 +32,7 @@ Before [creating an issue](https://help.github.com/en/github/managing-your-work-
### :lock: Reporting Security Issues
Review our [Security Policy](https://github.com/jessesquires/.github/blob/master/SECURITY.md). **Do not** file a public issue for security vulnerabilities.
Review our [Security Policy](https://github.com/jessesquires/.github/blob/main/SECURITY.md). **Do not** file a public issue for security vulnerabilities.
### :beetle: Bug Reports and Other Issues
@ -40,7 +40,7 @@ A great way to contribute to the project is to send a detailed issue when you en
In short, since you are most likely a developer, **provide a ticket that you would like to receive**.
- **Review the documentation and [Support Guide](https://github.com/jessesquires/.github/blob/master/SUPPORT.md)** before opening a new issue.
- **Review the documentation and [Support Guide](https://github.com/jessesquires/.github/blob/main/SUPPORT.md)** before opening a new issue.
- **Do not open a duplicate issue!** Search through existing issues to see if your issue has previously been reported. If your issue exists, comment with any additional information you have. You may simply note "I have this problem too", which helps prioritize the most common problems and requests.