Sync betaflight to Gitea

2026-08-03 16:37:10 +08:00
commit ad3163cf91
4712 changed files with 3301380 additions and 0 deletions
@@ -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
@@ -0,0 +1,36 @@
+name: Feature Request
+description: Suggest an idea for for a new feature for Betaflight.
+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.
@@ -0,0 +1,83 @@
+name: Firmware Bug Report
+description: Create a report to help us fix bugs in the Betaflight firmware.
+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: |
+        # Flight controller configuration
+
+  - type: textarea
+    attributes:
+      label: Support ID
+      description: |
+
+        If missing any drivers for GYRO, ACC, MAG, BARO, FLASH or OSD it's required to flash a `Core Only` build for your board.
+
+        Go to CLI tab and use the `Submit Support Data` button to get an `Support ID`. Please post the `Support ID` here.
+
+        Don't add three backticks or any other format symbol at the start or end of the block, they will be added automatically.
+
+      placeholder: |
+          # PASTE HERE THE OUTPUT OF `Support ID` IN THE CLI TAB
+      render: txt
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        # Setup / Versions
+
+  - type: input
+    attributes:
+      label: Flight controller
+      description: Specify your flight controller model (what type is it, where was it bought from, ...).
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Other components
+      description: Specify other components attached to the flight controller (RX, VTX, brand / model for all of them, firmware version where applicable...).
+
+  - type: textarea
+    attributes:
+      label: How are the different components wired up (including port information)
+      description: Details about how all is wired.
+
+  - type: markdown
+    attributes:
+      value: |
+        # Other information
+
+  - type: textarea
+    attributes:
+      label: Add any other context about the problem that you think might be relevant here