Merge pull request #2767 from McGiverGim/move_issues_form

Move issues to Github forms

.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,27 +0,0 @@
----
-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/bug-report.yml

@@ -0,0 +1,62 @@
+name: Bug Report
+description: Create a report to help us fix bugs in Betaflight Configurator.
+labels: [Template: Bug]
+body:
+
+  - type: markdown
+    attributes:
+      value: |
+        # Please fill all the fields with the required information
+
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: To Reproduce
+      description: Steps to reproduce the behavior.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        # Setup
+
+  - type: input
+    attributes:
+      label: Configurator version
+      description: Specify the version of the configurator (as displayed in the app).
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Flight controller configuration
+      description: |
+        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/).
+      value: |
+        ```
+          # REPLACE THIS LINE BY THE OUTPUT OF YOUR `diff`
+        ```
+
+  - type: markdown
+    attributes:
+      value: |
+        # Other information
+
+  - type: textarea
+    attributes:
+      label: Add any other context about the problem that you think might be relevant here

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,21 +0,0 @@
----
-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/feature-request.yml

@@ -0,0 +1,36 @@
+name: Feature Request
+description: Suggest a new feature idea for Betaflight Configurator.
+labels: [Template: Feature Request]
+body:
+
+  - type: markdown
+    attributes:
+      value: |
+        **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.
+
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem? Please describe
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...].
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Other information
+      description: Add any other context or screenshots about the feature request that you think might be relevant here.