rusefi
/
atbetaflight
mirror of https://github.com/rusefi/atbetaflight.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Move GitHub issues to forms

This commit is contained in:
Miguel Angel Mulero Martinez 2022-01-20 09:48:09 +01:00
parent 9c3562a10b
commit c62afa2e12
5 changed files with 113 additions and 80 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
.github/ISSUE_TEMPLATE/feature-request.md vendored
View File

@ -1,21 +0,0 @@
---
name: Feature Request
about: Suggest an idea for for a new feature for Betaflight
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. -->

36
.github/ISSUE_TEMPLATE/feature-request.yml vendored Normal file
View File

@ -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.

37
.github/ISSUE_TEMPLATE/firmware-bug-report.md vendored
View File

@ -1,37 +0,0 @@
---
name: Firmware Bug Report
about: Create a report to help us fix bugs in the Betaflight firmware
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. -->
### Flight controller configuration
<!-- 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/)
Use resource show all to create a resource allocation list and post it here in a code block. Put (three backticks) at the start and end of the output block. -->
```
PASTE THE OUTPUT OF 'diff' HERE
```
```
PASTE THE OUTPUT OF 'resource show all' HERE
```
### Setup / Versions
<!-- Specify your flight controller model (what type is it, where was it bought from, ...) -->
- Flight controller:
<!-- Specify other components attached to the flight controller (RX, VTX, brand / model for all of them, firmware version where applicable...) -->
- Other components:
<!-- Details about how all is wired -->
- How are the different components wired up:
<!-- Add any other context about the problem that you think might be relevant here. -->

77
.github/ISSUE_TEMPLATE/firmware-bug-report.yml vendored Normal file
View File

@ -0,0 +1,77 @@
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: textarea
attributes:
label: Flight controller configuration
description: |
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/).
Use `resource show all` to create a resource allocation list and post it here in a code block. Put (three backticks) at the start and end of the output block.
value: |
```
# REPLACE THIS LINE BY THE OUTPUT OF YOUR `diff`
```
```
# REPLACE THIS LINE BY THE OUTPUT OF YOUR `resource show all`
```
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
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

22
.github/workflows/issues.yml vendored
View File

@ -1,22 +0,0 @@
name: Issues
on:
issues:
types: [opened, edited]
jobs:
auto_close_issues:
name: Check if issues follow the templates
runs-on: ubuntu-latest
steps:
- name: Checkout templates
uses: actions/checkout@v2.3.4
- name: Automatically close issues that don't follow the templates
uses: ergo720/auto-close-issues@v1.0.4
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
issue-close-message: >
@${issue.user.login}: This issue is being automatically closed because it does not follow the template.\n\n
**When you open an issue or feature request you are presented with a template. Follow the guidelines**.\n\n
You can edit your message to fix this and the issue will be automatically reopened.
closed-issues-label: Not following template