diff options
| -rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 24 | ||||
| -rw-r--r-- | pull_request_template.md | 16 |
2 files changed, 20 insertions, 20 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 0424dab5ec..11bd83499c 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -7,40 +7,40 @@ assignees: '' --- -[//]: # (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) -[//]: # (For issues containing a fix, please create a Pull Request following this tutorial: https://www.azerothcore.org/wiki/How-to-create-a-PR) +<!-- 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 + 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:** -[//]: # (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:** -[//]: # (What should happen instead) +<!-- What should happen instead --> **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:** -[//]: # (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. 2. 3. **EXTRA NOTES:** -[//]: # (Any extra notes that can help solve the issue) +<!-- Any extra notes that can help solve the issue --> **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:** -[//]: # (Which OS are you running) +<!-- Which OS are you running --> **MODULES:** -[//]: # (Are you using any modules? List them here) +<!-- Are you using any modules? List them here --> **CUSTOMIZATIONS:** -[//]: # (Do you have any other customizations? List them here) +<!-- Do you have any other customizations? List them here --> <!-- ------------------------- THE END ------------------------------ Thank you for your contribution. diff --git a/pull_request_template.md b/pull_request_template.md index cc5c8ee024..3b677b0d2b 100644 --- a/pull_request_template.md +++ b/pull_request_template.md @@ -1,37 +1,37 @@ -[//]: # (First of all, THANK YOU for your contribution.) +<!-- First of all, THANK YOU for your contribution. --> ## Changes Proposed: - - ## Issues Addressed: -[//]: # (If your fix has a relating issue, link it below) +<!-- If your fix has a relating issue, link it below --> - Closes ## 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: -[//]: # (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: -[//]: # (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. 2. 3. ## 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) -[//]: # (Do not remove the instructions below about testing, they will help users to test your 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) + Do not remove the instructions below about testing, they will help users to test your PR --> ## How to Test AzerothCore PRs When a PR is ready to be tested, it will be marked as **[WAITING TO BE TESTED]**. |