Update issue templates

2 files changed, 80 insertions, 0 deletions

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..19dfc26b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,60 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+### Describe the bug
+A clear and concise description of what the bug is.
+
+### To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behavior
+A clear and concise description of what you expected to happen.
+
+### Screenshots
+If applicable, add screenshots to help explain your problem.
+
+### System:
+
+- Nheko version: <!-- Get the version from the settings menu (bottom left corner)  -->
+- Installation method: <!-- AppImage, some repository, local build etc -->
+- Operating System:
+- Qt version: <!-- If you compiled it yourself -->
+- C++ compiler: <!-- if you compiled it yourself -->
+- Desktop Environment: <!-- for Linux -->
+
+### Logs
+<!-- If applicable -->
+
+<!-- The log file is located in
+    Linux: ~/.cache/nheko/
+    macOS: ~/Library/Caches/nheko or /Library/Caches/nheko
+    Windows: C:/Users/<USER>/AppData/Local/nheko/cache
+-->
+
+### Debugger backtrace
+<!-- 
+If the program crashed send a backtrace:
+
+You can retrieve a backtrace by building nheko with -DCMAKE_BUILD_TYPE=Debug
+and running it through gdb or lldb.
+
+gdb ./build/nheko
+
+>> run
+
+... Make the program crash
+
+>> bt
+
+... Paste a link of the output below (Use a pastebin, don't paste directly in the github issue).
+-->
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 00000000..11fc491e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.