45 lines
1.5 KiB
YAML
45 lines
1.5 KiB
YAML
name: "\U0001F680 Feature Request"
|
|
description: "Suggest an idea for this project \U0001F63B!"
|
|
title: 'feat: [DESCRIPTION]'
|
|
labels: 'type: feature request'
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: "Thanks for taking the time to fill out this form!"
|
|
|
|
- type: checkboxes
|
|
attributes:
|
|
label: "#"
|
|
description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the feature you are requesting"
|
|
options:
|
|
- label: "I have searched the existing issues"
|
|
required: false
|
|
|
|
- type: textarea
|
|
validations:
|
|
required: true
|
|
attributes:
|
|
label: "Is your feature request related to a problem? Please describe it"
|
|
description: "A clear and concise description of what the problem is"
|
|
placeholder: |
|
|
I'm always frustrated when ...
|
|
|
|
- type: textarea
|
|
validations:
|
|
required: true
|
|
attributes:
|
|
label: "Describe the solution"
|
|
description: "Description of what you want to happen. Add any considered drawbacks"
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: "Teachability, documentation, adoption, migration strategy"
|
|
description: "Explain how users will be able to use this and possibly write out something for the docs. Maybe a screenshot or design?"
|
|
|
|
- type: textarea
|
|
validations:
|
|
required: true
|
|
attributes:
|
|
label: "What is the motivation / use case for changing the behavior?"
|
|
description: "Describe the motivation or the concrete use case"
|