Sorting the repository files

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,92 @@
+name: Bug report
+description: Create a bug report to help us improve.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to fill out a bug report. Remember to fill out all fields including the title above. 
+        An issue that is not properly filled out will be closed. 
+        You can read more about the standards for a bug report [here](https://www.azerothcore.org/wiki/issue-tracker-standards).
+  - type: textarea
+    id: current
+    attributes:
+      label: Current Behaviour
+      description: |
+        Description of the problem or issue here.
+        Include entries of affected creatures / items / quests / spells etc.
+        If this is a crash, post the crashlog (upload to https://gist.github.com/) and include the link here.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Blizzlike Behaviour
+      description: |
+        Tell us what should happen instead.
+    validations:
+      required: true
+  - type: textarea
+    id: source
+    attributes:
+      label: Source
+      description: |
+        If you have a source that proves how it is supposed to work, please add that to make it easier for devs to fix the issue.
+    validations:
+      required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce the problem
+      description: |
+        What does someone else need to do to encounter the same bug?
+      placeholder: |
+        1. Step 1
+        2. Step 2
+        3. Step 3
+    validations:
+      required: true
+  - type: textarea
+    id: extra
+    attributes:
+      label: Extra Notes
+      description: |
+        Do you have any extra notes that can help solve the issue that does not fit any other field?
+      placeholder: |
+        None
+    validations:
+      required: false
+  - type: textarea
+    id: commit
+    attributes:
+      label: AC rev. hash/commit
+      description: |
+        Copy the result of the `.server debug` command (if you need to run it from the client get a prat addon)
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      description: |
+        Operating System, i.e. Windows 10 x64, Debian 10 x64, etc
+    validations:
+      required: true
+  - type: textarea
+    id: custom
+    attributes:
+      label: Custom changes or Modules
+      description: |
+        List which custom changes or modules you have applied, i.e. Eluna module, etc.
+      placeholder: |
+        None
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for your contribution.
+        If you use AzerothCore regularly, we really NEED your help to:
+        - Test our fixes: https://www.azerothcore.org/wiki/How-to-test-a-PR
+        - Report issues or suggestions: https://github.com/azerothcore/azerothcore-wotlk/issues/new/choose
+        - Improve the documentation/wiki: https://www.azerothcore.org/wiki/home
+        With your help, the project can evolve much quicker!

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,20 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Website
+    url: https://www.azerothcore.org
+    about: On the AC website you can find a lot of things, such as existing modules.
+  - name: Wiki
+    url: https://www.azerothcore.org/wiki
+    about: You can find plenty of information on our Wiki.
+  - name: How to ask for help
+    url: https://www.azerothcore.org/wiki/How-to-ask-for-help
+    about: Before submitting an issue we'd love if you take a minute to read this.
+  - name: FAQ
+    url: https://www.azerothcore.org/wiki/faq
+    about: Frequently asked questions.
+  - name: Common Errors
+    url: https://www.azerothcore.org/wiki/common-errors
+    about: You can find common errors and their solutions here.
+  - name: Discord
+    url: https://discord.gg/gkt4y2x
+    about: Join the discussions over at our Discord Server.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,42 @@
+name: Feature request
+description: Suggest an idea for this project
+title: "Feature: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking your time to fill out a feature request. Remember to fill out all fields including the title above. 
+        An issue that is not properly filled out will be closed. 
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe your feature request or suggestion in detail
+      description: |
+        A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe a possible solution to your feature or suggestion in detail
+      description: |
+        A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: |
+        Add any other context or screenshots about the feature request here.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for your contribution.
+        If you use AzerothCore regularly, we really NEED your help to:
+        - Test our fixes: https://www.azerothcore.org/wiki/How-to-test-a-PR
+        - Report issues or suggestions: https://github.com/azerothcore/azerothcore-wotlk/issues/new/choose
+        - Improve the documentation/wiki: https://www.azerothcore.org/wiki/home
+        With your help, the project can evolve much quicker!

.github/README.md

@@ -26,7 +26,7 @@ or you can manually [download the module](https://github.com/azerothcore/mod-ant
 
 ### 2) Re-run cmake and launch a clean build of AzerothCore
 
-### 3) Execute the included "\sql\characters\base\charactersdb_anticheat.sql" file on your characters database and excute  "\sql\world\Acore_strings.sql" on your world datase. This creates the necessary tables for this module.
+### 3) Execute the included `\sql\characters\base\charactersdb_anticheat.sql` file on your characters database and excute  `\sql\world\Acore_strings.sql` on your world datase. This creates the necessary tables for this module.
 
 **That's it.**
 
@@ -37,7 +37,7 @@ If you need to change the module configuration, go to your server configuration
 # Known issues and TODO list:
 
 - [ ] Identify any class\spells that gives false positives, so far only blink and killingspree has been reported
-- [ ] Currently no dedicated collumn for ignore control or teleport hack reporting, but the numbers are added to total report. Custom Messages are adjusted in Acore_string for those two anticheats. The reason being is for some damn reason we are getting unrealistic high numbers being reported in the sql if i add in another collumn or two. I have no idea why that happens.
+- [ ] Currently no dedicated collumn for ignore control or teleport hack reporting, but the numbers are added to total report. Custom Messages are adjusted in `acore_string` for those two anticheats. The reason being is for some damn reason we are getting unrealistic high numbers being reported in the sql if i add in another collumn or two. I have no idea why that happens.
 
 # Localize Acore_Strings
 - [x] LOCALE_enUS = 0

.github/README_ES.md

@@ -26,7 +26,7 @@ o puede [descargar manualmente el módulo](https://github.com/azerothcore/mod-an
 
 ### 2) Vuelva a ejecutar cmake e inicie una compilación limpia de AzerothCore
 
-### 3) Ejecute el archivo "\sql\characters\base\charactersdb_anticheat.sql" incluido en su base de datos de personajes y ejecute "\sql\world\Acore_strings.sql" en su base de datos world. Esto crea las tablas necesarias para este módulo.
+### 3) Ejecute el archivo `\sql\characters\base\charactersdb_anticheat.sql` incluido en su base de datos de personajes y ejecute `\sql\world\Acore_strings.sql` en su base de datos world. Esto crea las tablas necesarias para este módulo.
 
 **Eso es todo.**
 
@@ -37,7 +37,7 @@ Si necesita cambiar la configuración del módulo, vaya a la carpeta de configur
 # Problemas conocidos y lista de TODO:
 
 - [ ] Identifique cualquier clase/hechizo que dé falsos positivos, hasta ahora solo se ha informado blink y killingspree.
-- [ ] CActualmente no hay una columna dedicada para ignorar el control o el informe de hack de teletransporte, pero los números se agregan al informe total. Los mensajes personalizados se ajustan en Acore_string para esos dos anticheats. La razón es que, por alguna maldita razón, estamos obteniendo números altos poco realistas que se informan en el sql si agrego otra columna o dos. No tengo idea de por qué sucede eso.
+- [ ] CActualmente no hay una columna dedicada para ignorar el control o el informe de hack de teletransporte, pero los números se agregan al informe total. Los mensajes personalizados se ajustan en `acore_string` para esos dos anticheats. La razón es que, por alguna maldita razón, estamos obteniendo números altos poco realistas que se informan en el sql si agrego otra columna o dos. No tengo idea de por qué sucede eso.
 
 # Localizar Acore_Strings
 - [x] LOCALE_enUS = 0

pull_request_template.md

@@ -0,0 +1,44 @@
+<!-- First of all, THANK YOU for your contribution. -->
+
+## Changes Proposed:
+-  
+-  
+
+## Issues Addressed:
+<!-- If your fix has a relating issue, link it below -->
+- Closes 
+
+## SOURCE:
+<!-- 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 -->
+- 
+- 
+
+## 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? -->
+
+- [ ]
+- [ ]
+
+<!-- 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]**.
+
+You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
+
+http://www.azerothcore.org/wiki/How-to-test-a-PR
+
+**REMEMBER**: when testing a PR that changes something **generic** (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but **especially** check that the PR does not cause any regression (i.e. introducing new bugs).
+
+**For example**: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but **we should test Y and Z as well**.