Skip to content

Commit b69de69

Browse files
committed
docs: update issue template
1 parent 934572c commit b69de69

File tree

1 file changed

+4
-11
lines changed

1 file changed

+4
-11
lines changed

.github/ISSUE_TEMPLATE/feature_request.yml

+4-11
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name: 🚀 New feature proposal
22
description: Propose a new feature
33
labels: [enhancement]
4-
title: '`rule-name`: describe the feature here'
4+
title: 'Feature proposal:'
55
body:
66
- type: markdown
77
attributes:
@@ -18,7 +18,7 @@ body:
1818
id: suggested-solution
1919
attributes:
2020
label: Suggested solution
21-
description: 'In rule [xy] we could provide following implementation...'
21+
description: 'In xxx, we could provide following implementation...'
2222
validations:
2323
required: true
2424
- type: textarea
@@ -37,16 +37,9 @@ body:
3737
label: Validations
3838
description: Before submitting the issue, please make sure you do the following
3939
options:
40-
- label: Follow our [Code of Conduct](https://github.com/eslint-stylistic/eslint-stylistic/blob/main/CODE_OF_CONDUCT.md)
40+
- label: Follow our [Code of Conduct](https://github.com/shikijs/shiki/blob/main/CODE_OF_CONDUCT.md)
4141
required: true
42-
- label: Read the [Contributing Guide](https://eslint.style/contribute/guide).
42+
- label: Read the [Contributing Guide](https://github.com/shikijs/shiki/blob/main/CONTRIBUTING.md).
4343
required: true
4444
- label: Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
4545
required: true
46-
- type: checkboxes
47-
id: contributes
48-
attributes:
49-
label: Contributes
50-
description: As stylistic rules can be sometime subjective or niche, we may not have enough to maintainability to fix or improve every aspect. In general, **we encourage the original reporter (or anyone wants to work on it) to submit a PR to fix issue**. Check the following if you are willing to
51-
options:
52-
- label: If this feature request is accepted, I am willing to submit a PR to fix this issue

0 commit comments

Comments
 (0)