Update the feature request template to the new yml format
This commit is contained in:
parent
688e74aad8
commit
ea6dfb172c
27
.github/ISSUE_TEMPLATE/feature_request.md
vendored
27
.github/ISSUE_TEMPLATE/feature_request.md
vendored
@ -1,27 +0,0 @@
|
|||||||
---
|
|
||||||
name: Feature request
|
|
||||||
about: Suggest a new idea for this project
|
|
||||||
title: ''
|
|
||||||
labels: Feature request
|
|
||||||
assignees: ''
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
# Instructions
|
|
||||||
*This is a template to help you report good issues. You may use [Github Markdown](https://help.github.com/articles/getting-started-with-writing-and-formatting-on-github/) syntax to format your issue report.*
|
|
||||||
*Please:*
|
|
||||||
- *replace the bracket enclosed texts with meaningful information*
|
|
||||||
- *remove any unused sub-section*
|
|
||||||
|
|
||||||
|
|
||||||
# Feature Request
|
|
||||||
[*Short description*]
|
|
||||||
|
|
||||||
## Use case
|
|
||||||
[*Verbose description*]
|
|
||||||
|
|
||||||
## Suggested implementation
|
|
||||||
[*Verbose description*]
|
|
||||||
|
|
||||||
## Suggested steps
|
|
||||||
[*List of tasks to achieve goal*]
|
|
||||||
44
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
44
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
@ -0,0 +1,44 @@
|
|||||||
|
name: Feature request
|
||||||
|
description: Suggest a new idea for this project
|
||||||
|
labels: ["Feature request"]
|
||||||
|
|
||||||
|
body:
|
||||||
|
- type: markdown
|
||||||
|
attributes:
|
||||||
|
value: |
|
||||||
|
This is a template to help you report good issues. You may use [Github Markdown](https://help.github.com/articles/getting-started-with-writing-and-formatting-on-github/) syntax to format your issue report.
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: feature-request
|
||||||
|
attributes:
|
||||||
|
label: Feature Request
|
||||||
|
description: Short description
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: use-case
|
||||||
|
attributes:
|
||||||
|
label: Use case
|
||||||
|
description: Verbose description
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: suggested-implementation
|
||||||
|
attributes:
|
||||||
|
label: Suggested implementation
|
||||||
|
description: Verbose description
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: suggested-steps
|
||||||
|
attributes:
|
||||||
|
label: Suggested steps
|
||||||
|
description: List of tasks to achieve goal
|
||||||
|
|
||||||
|
- type: checkboxes
|
||||||
|
id: terms
|
||||||
|
attributes:
|
||||||
|
label: Code of Conduct
|
||||||
|
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Dolibarr/dolibarr/blob/develop/.github/CODE_OF_CONDUCT.md)
|
||||||
|
options:
|
||||||
|
- label: I agree to follow this project's Code of Conduct
|
||||||
|
required: true
|
||||||
Loading…
Reference in New Issue
Block a user