Auto merged - #2665 at Wed, 08 Dec 2021 10:17:12 GMT

Update github issues templates

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,27 @@
+---
+name: Bug Report
+about: Create a report to help us fix bugs in Betaflight Configurator
+labels: "Template: Bug"
+---
+<!-- This is a template that you must fill. If not, the message will be closed. So don't erase any subtitle in this template (they start with ###)
+and complete all of them -->
+
+### Describe the bug
+<!-- A clear and concise description of what the bug is. -->
+
+### To Reproduce
+<!-- Steps to reproduce the behavior -->
+
+### Expected behavior
+<!-- A clear and concise description of what you expected to happen. -->
+
+### Setup
+<!-- Specify the version of the configurator (as displayed in the app) -->
+- Configurator version:
+
+<!-- If this bug is related to a specific flight controller and/or configuration please specify it here. Create a diff and post it here in a code block. Put (three backticks) at the start and end of the diff block (instructions  on how to do a diff: https://oscarliang.com/use-diff-not-dump-betaflight/) -->
+```
+PASTE THE OUTPUT OF 'diff' HERE
+```
+
+<!-- Add any other context about the problem that you think might be relevant here. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Configuration and other support questions
+    url: https://github.com/betaflight/betaflight#support-and-developers-channel
+    about: Official Slack chat channel and Facebook group about Betaflight
+  - name: Hardware Issues
+    url: https://github.com/betaflight/betaflight#hardware-issues
+    about: What to do in the case of hardware issues

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: Suggest an idea for for a new feature for Betaflight Configurator
+labels: "Template: Feature Request"
+---
+<!-- This is a template that you must fill. If not, the message will be closed. So don't erase any subtitle in this template (they start with ###)
+and complete all of them -->
+
+<!-- Please note that feature requests are not 'fire and forget'. It is a lot more likely that the feature you would like to have will be implemented if you keep watching your feature request, and provide more details to developers looking into implementing your feature, and help them with testing. -->
+
+### 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. -->
+
+
+<!-- Add any other context or screenshots about the feature request that you think might be relevant here. -->

.github/issue_template.md

@@ -1,12 +0,0 @@
-# If your issue looks like a hardware fault or a configuration problem please don't raise an issue here.
-
-## Please consider using other user support options such as asking the manufacturer of the hardware you are using, RCGroups: https://rcgroups.com/forums/showthread.php?t=2464844, or Slack (registration at https://slack.betaflight.com/) or other user support forums & groups (e.g. Facebook).
-
-## If you believe there is an issue with the firmware itself please follow these steps:
-1. Describe your problem;
-2. Include ways to reproduce the problem;
-3. Provide as much information as possible about your hardware and software, including:
-- what hardware / software you are using;
-- the version of all the software used;
-- how things are connected / wired up.
-4. Remove this Text :).