1 | # Managing issues
|
2 |
|
3 | We manage issues consistently for the benefit of ourselves and our users.
|
4 |
|
5 | ## Labels
|
6 |
|
7 | Use [labels](https://github.com/stylelint/stylelint/labels).
|
8 |
|
9 | When you first triage an issue, you should:
|
10 |
|
11 | - add one of the `status: needs *` labels, e.g. `status: need discussion`
|
12 | - don't add any other label
|
13 |
|
14 | After triage, you should add:
|
15 |
|
16 | - _one_ of the non-need `status: *` labels, e.g. `status: ready to implement`
|
17 | - _zero or one_ of the `type: *` labels, e.g. `status: new rule`
|
18 | - _zero, one or more_ of the `syntax: *` labels, e.g. `syntax: scss`
|
19 | - optionally, the `good first issue`, `help wanted`, `priority: high` and `upstream` labels
|
20 |
|
21 | ## Milestones
|
22 |
|
23 | Use [milestones](https://github.com/stylelint/stylelint/milestones).
|
24 |
|
25 | You should:
|
26 |
|
27 | - use the `future-major` milestone for issues that introduce breaking changes
|
28 | - optionally, create version milestones (e.g. `8.x`) to manage upcoming releases
|
29 |
|
30 | ## Titles
|
31 |
|
32 | Rename the title into a consistent format.
|
33 |
|
34 | You should:
|
35 |
|
36 | - lead with the [CHANGELOG group names](pull-requests.md), but in the present tense:
|
37 | - "Remove y", e.g. "Remove unit-blacklist"
|
38 | - "Deprecate x in y", e.g. "Deprecate resolvedNested option in selector-class-pattern"
|
39 | - "Add y", e.g. "Add unit-blacklist"
|
40 | - "Add x to y", e.g. "Add ignoreProperties: [] to property-blacklist"
|
41 | - "Fix false positives/negatives for x in y", e.g. "Fix false positives for Less mixins in color-no-hex"
|
42 | - use `*` if the issue applies to a group of rules, e.g. "Fix false negatives for SCSS variables in selector-\*-pattern"
|
43 |
|
44 | ## Saved replies
|
45 |
|
46 | You should use [saved replies](https://help.github.com/en/github/writing-on-github/working-with-saved-replies).
|
47 |
|
48 | ### Close an issue
|
49 |
|
50 | That doesn't use a template:
|
51 |
|
52 | ```md
|
53 | Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
|
54 |
|
55 | Please help us help you by [recreating the issue](https://github.com/stylelint/stylelint/issues/new/choose) using one of our templates.
|
56 | ```
|
57 |
|
58 | That is best-suited as a plugin:
|
59 |
|
60 | ```md
|
61 | Thank you for your suggestion. I think this is best-suited as a [plugin](https://stylelint.io/developer-guide/plugins).
|
62 | ```
|
63 |
|
64 | ### Label as ready to implement
|
65 |
|
66 | That fixes a bug in a rule:
|
67 |
|
68 | ```md
|
69 | I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.io/contributing) if you have time.
|
70 |
|
71 | There are [steps on how to fix a bug in a rule](https://stylelint.io/developer-guide/rules#fix-a-bug-in-a-rule) in the Developer guide.
|
72 | ```
|
73 |
|
74 | That adds a new option to a rule:
|
75 |
|
76 | ```md
|
77 | I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.io/contributing) if you have time.
|
78 |
|
79 | There are [steps on how to add a new option](https://stylelint.io/developer-guide/rules#add-an-option-to-a-rule) in the Developer guide.
|
80 | ```
|
81 |
|
82 | That adds a new rule:
|
83 |
|
84 | ```md
|
85 | I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.io/contributing) if you have time.
|
86 |
|
87 | There are [steps on how to add a new rule](https://stylelint.io/developer-guide/rules#add-a-rule) in the Developer guide.
|
88 | ```
|
89 |
|
90 | That is another type of improvement:
|
91 |
|
92 | ```md
|
93 | I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.io/contributing) if you have time.
|
94 | ```
|