docs(template): fix comment (#5634)

This commit is contained in:
Kitzunu
2021-05-04 15:32:45 +02:00
committed by GitHub
parent 44ecd5a4cb
commit 367f3f53af
2 changed files with 20 additions and 20 deletions

View File

@@ -7,40 +7,40 @@ assignees: ''
--- ---
[//]: # (IF YOU DO NOT FILL THIS TEMPLATE OUT, WE WILL CLOSE YOUR ISSUE) <!-- IF YOU DO NOT FILL THIS TEMPLATE OUT, WE WILL CLOSE YOUR ISSUE
[//]: # (You should always read how to properly fill out the bug report before continuing. https://www.azerothcore.org/wiki/issue-tracker-standards) You should always read how to properly fill out the bug report before continuing. https://www.azerothcore.org/wiki/issue-tracker-standards
[//]: # (For issues containing a fix, please create a Pull Request following this tutorial: https://www.azerothcore.org/wiki/How-to-create-a-PR) For issues containing a fix, please create a Pull Request following this tutorial: https://www.azerothcore.org/wiki/How-to-create-a-PR -->
**CURRENT BEHAVIOUR:** **CURRENT BEHAVIOUR:**
[//]: # (If this is a crash report you should post the crashlog. Upload it to https://gist.github.com/) <!-- If this is a crash report you should post the crashlog. Upload it to https://gist.github.com/ -->
**EXPECTED BLIZZLIKE BEHAVIOUR:** **EXPECTED BLIZZLIKE BEHAVIOUR:**
[//]: # (What should happen instead) <!-- What should happen instead -->
**SOURCE:** **SOURCE:**
[//]: # (If you can, include a source that can strengthen your claim) <!-- If you can, include a source that can strengthen your claim -->
**STEPS TO REPRODUCE THE PROBLEM:** **STEPS TO REPRODUCE THE PROBLEM:**
[//]: # (Describe in a detailed step-by-step order how to reproduce the issue) <!-- Describe in a detailed step-by-step order how to reproduce the issue -->
1. 1.
2. 2.
3. 3.
**EXTRA NOTES:** **EXTRA NOTES:**
[//]: # (Any extra notes that can help solve the issue) <!-- Any extra notes that can help solve the issue -->
**AC HASH/COMMIT:** **AC HASH/COMMIT:**
[//]: # (Always include the exact hash/commit you are using. Never write "latest"!) <!-- Always include the exact hash/commit you are using. Never write "latest"! -->
**OPERATING SYSTEM:** **OPERATING SYSTEM:**
[//]: # (Which OS are you running) <!-- Which OS are you running -->
**MODULES:** **MODULES:**
[//]: # (Are you using any modules? List them here) <!-- Are you using any modules? List them here -->
**CUSTOMIZATIONS:** **CUSTOMIZATIONS:**
[//]: # (Do you have any other customizations? List them here) <!-- Do you have any other customizations? List them here -->
<!-- ------------------------- THE END ------------------------------ <!-- ------------------------- THE END ------------------------------
Thank you for your contribution. Thank you for your contribution.

View File

@@ -1,37 +1,37 @@
[//]: # (First of all, THANK YOU for your contribution.) <!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed: ## Changes Proposed:
- -
- -
## Issues Addressed: ## Issues Addressed:
[//]: # (If your fix has a relating issue, link it below) <!-- If your fix has a relating issue, link it below -->
- Closes - Closes
## SOURCE: ## SOURCE:
[//]: # (If you can, include a source that can strengthen your claim) <!-- If you can, include a source that can strengthen your claim -->
## Tests Performed: ## Tests Performed:
[//]: # (Does it build without errors? Did you test in-game? What did you test? On which OS did you test? Describe any other tests performed) <!-- Does it build without errors? Did you test in-game? What did you test? On which OS did you test? Describe any other tests performed -->
- -
- -
## How to Test the Changes: ## How to Test the Changes:
[//]: # (Describe in a detailed step-by-step order how to test the changes) <!-- Describe in a detailed step-by-step order how to test the changes -->
1. 1.
2. 2.
3. 3.
## Known Issues and TODO List: ## Known Issues and TODO List:
[//]: # (Is there anything else left to do after this PR?) <!-- Is there anything else left to do after this PR? -->
- [ ] - [ ]
- [ ] - [ ]
[//]: # (If you intend to contribute repeatedly to our project, it is a good idea to join our discord channel. We set ranks for our contributors and give them access to special resources or knowledge: https://discord.com/invite/DasJqPba) <!-- If you intend to contribute repeatedly to our project, it is a good idea to join our discord channel. We set ranks for our contributors and give them access to special resources or knowledge: https://discord.com/invite/DasJqPba)
[//]: # (Do not remove the instructions below about testing, they will help users to test your PR) Do not remove the instructions below about testing, they will help users to test your PR -->
## How to Test AzerothCore PRs ## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE TESTED]**. When a PR is ready to be tested, it will be marked as **[WAITING TO BE TESTED]**.