管理问题
¥Managing issues
为了我们自己和用户的利益,我们始终如一地管理问题。
¥We manage issues consistently for the benefit of ourselves and our users.
标签和问题类型
¥Labels and issue types
使用 labels 和问题类型。
¥Use labels and issue types.
当你第一次对问题进行分类时,你应该:
¥When you first triage an issue, you should:
-
添加
status: needs *
标签之一,例如status: needs discussion
¥add one of the
status: needs *
labels, e.g.status: needs discussion
-
不要添加任何其他标签或问题类型
¥don't add any other label or an issue type
分类后,你应该添加:
¥After triage, you should add:
-
问题类型之一,例如
bug
¥one of the issue types, e.g.
bug
-
不需要
status: *
标签之一,例如status: ready to implement
¥one of the non-need
status: *
labels, e.g.status: ready to implement
-
零个或一个
subtype: *
标签,例如subtype: new rule
¥zero or one of the
subtype: *
labels, e.g.subtype: new rule
-
零个、一个或多个
syntax: *
标签,例如syntax: scss
¥zero, one or more of the
syntax: *
labels, e.g.syntax: scss
-
零个或一个
priority: *
标签,例如priority: high
¥zero or one of the
priority: *
labels, e.g.priority: high
-
可选,
good first issue
、help wanted
和upstream
标签¥optionally, the
good first issue
,help wanted
andupstream
labels
里程碑
¥Milestones
使用 milestones。
¥Use milestones.
你应该:
¥You should:
-
使用
future-major
里程碑来解决引入重大更改的问题¥use the
future-major
milestone for issues that introduce breaking changes -
(可选)创建版本里程碑(例如
8.x
)来管理即将发布的版本¥optionally, create version milestones (e.g.
8.x
) to manage upcoming releases
标题
¥Titles
将标题重命名为一致的格式。
¥Rename the title into a consistent format.
你应该:
¥You should:
-
以 变更日志组名称 开头,但用现在时:
¥lead with the CHANGELOG group names, but in the present tense:
-
"删除 y",例如 “删除
unit-disallowed-list
Ӵ"Remove y", e.g. "Remove
unit-disallowed-list
" -
"弃用 y 中的 x",例如 “在
selector-class-pattern
中弃用resolvedNested
选项”¥"Deprecate x in y", e.g. "Deprecate
resolvedNested
option inselector-class-pattern
" -
"添加 y",例如 “添加
unit-disallowed-list
Ӵ"Add y", e.g. "Add
unit-disallowed-list
" -
"将 x 添加到 y",例如 “将
ignoreProperties: []
添加到property-disallowed-list
Ӵ"Add x to y", e.g. "Add
ignoreProperties: []
toproperty-disallowed-list
" -
"修复 y 的 x 误报/漏报",例如 “修复 Less mixin 的
color-no-hex
误报”¥"Fix x false positives/negatives for y", e.g. "Fix
color-no-hex
false positives for Less mixins"
-
-
如果问题适用于一组规则,则使用
*
,例如 “修复 SCSS 变量的selector-*-pattern
漏报”¥use
*
if the issue applies to a group of rules, e.g. "Fixselector-*-pattern
false negatives for SCSS variables"
受让人
¥Assignees
你可以:
¥You can:
-
将自己分配给某个问题,但未经他人许可不得分配给其他人
¥assign yourself to an issue, but not other people without their permission
-
在询问其他人是否仍在处理某个问题后取消分配
¥unassign others after asking if they are still working on an issue
已保存的响应
¥Saved replies
你应该使用 已保存的响应。
¥You should use saved replies.
关闭问题
¥Close an issue
这不使用模板:
¥That doesn't use a template:
Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
Please help us help you by [recreating the issue](https://github.com/stylelint/stylelint/issues/new/choose) using one of our templates.
最适合作为插件:
¥That is best suited as a plugin:
Thank you for your suggestion. I think this is best-suited as a [plugin](https://stylelint.nodejs.cn/developer-guide/plugins).
标记为准备实现
¥Label as ready to implement
这修复了规则中的错误:
¥That fixes a bug in a rule:
I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.nodejs.cn/contributing) if you have time.
There are [steps on how to fix a bug in a rule](https://stylelint.nodejs.cn/developer-guide/rules#fix-a-bug-in-a-rule) in the Developer guide.
这为规则添加了一个新选项:
¥That adds a new option to a rule:
I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.nodejs.cn/contributing) if you have time.
There are [steps on how to add a new option](https://stylelint.nodejs.cn/developer-guide/rules#add-an-option-to-a-rule) in the Developer guide.
这增加了一条新规则:
¥That adds a new rule:
I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.nodejs.cn/contributing) if you have time.
There are [steps on how to add a new rule](https://stylelint.nodejs.cn/developer-guide/rules#add-a-rule) in the Developer guide.
这是另一种改进:
¥That is another type of improvement:
I've labeled the issue as ready to implement. Please consider [contributing](https://stylelint.nodejs.cn/contributing) if you have time.