From 890014e2611fa006162197ffde4ebdf6f4cde714 Mon Sep 17 00:00:00 2001
From: Dragonisser <dragonisser@googlemail.com>
Date: Tue, 8 Aug 2023 11:25:53 +0200
Subject: [PATCH] feat: add issue templates

---
 .github/ISSUE_TEMPLATE/Bug_report.md      | 62 +++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/Feature_request.md | 16 ++++++
 2 files changed, 78 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/Bug_report.md
 create mode 100644 .github/ISSUE_TEMPLATE/Feature_request.md

diff --git a/.github/ISSUE_TEMPLATE/Bug_report.md b/.github/ISSUE_TEMPLATE/Bug_report.md
new file mode 100644
index 0000000..4ceb3d3
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/Bug_report.md
@@ -0,0 +1,62 @@
+---
+name: Bug report
+about: Create a report to help us improve TF2 Tower Defense
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Version of TF2 Tower Defense and dependencies
+
+<!--
+Keep in mind that it barely makes sense to report bugs on older version and the issue might be fixed already in the latest available version of TF2 Tower Defense. 
+-->
+
+*For example:*
+
+Tower Defense:          2.1.0
+
+TF2Items:               1.6.4-279
+
+Steamtools:             0.10.0-54fdc51
+
+TF2Attributes:          v1.7.3
+
+MySQL/MariaDB server:   10.3.39-MariaDB-0+deb10u1
+
+## Description
+
+A clear and concise description of what the bug is.
+
+
+## Steps to reproduce
+
+How to reproduce this issue. Be as specific as possible and try to only include instructions you believe are necessary to reproduce said issue, E.g.
+
+1. Join a server
+2. Join a team
+3. Start the wave
+4. Bots dont spawn
+
+## Reproduction rate
+
+Please check just _one_ of the following reproduction rates:
+
+- [ ] Consistent: I can reproduce this bug by following the steps to reproduce 100% of the time (*every time*)
+- [ ] Occasional: I can reproduce this bug by following the steps to reproduce around 50% of the time
+- [ ] Rare: I can reproduce this bug by following the steps to reproduce around 10% or less of the time
+
+<!---
+Friendly Tip: most bugs are in fact 100% reproducible - it's nailing down the precise reproduction steps that is the hard part! Bugs that are 80-100% reproducible will save the developers a lot of time and energy and they tend to get more attention too. If you have the time, try and figure out the exact reproduction steps and everybody will benefit. This text will not appear in the actual bug report but is visible to people creating new issues - feel free to remove it if you like.
+-->
+
+## Expected result
+
+Describe your expected result i.e. answer the question "What did you expect would happen?"
+
+## Evidence (optional)
+
+Show us what happened or provide any kind of logs
+
+<!--- Please browsed through the other issues and confirmed that this issue has not been reported already. -->
diff --git a/.github/ISSUE_TEMPLATE/Feature_request.md b/.github/ISSUE_TEMPLATE/Feature_request.md
new file mode 100644
index 0000000..04e2fa1
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/Feature_request.md
@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: Feature
+assignees: ''
+
+---
+
+## Description
+
+A short description about your feature request.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.