From 9ae3498f826ed1af95c1cc2111d72826b7db719e Mon Sep 17 00:00:00 2001 From: Tomoko Uchida Date: Sat, 20 Aug 2022 13:22:42 +0900 Subject: [PATCH] add notes about labels' color code --- dev-docs/github-issues-howto.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/dev-docs/github-issues-howto.md b/dev-docs/github-issues-howto.md index 03c12d91ad1..faacf3c0c77 100644 --- a/dev-docs/github-issues-howto.md +++ b/dev-docs/github-issues-howto.md @@ -23,21 +23,21 @@ under the License. There are a few pre-defined label families to organize/search issues. -- `type` : issue type +- `type` (color code `#ffbb00`) : issue type - `type:bug` is attached to bug reports - `type:enhancement` is attached to enhancement requests or suggestions - `type:test` is attached to test improvements or failure reports - `type:task` is attached to general tasks - `type:documentation` is attached to tasks relate to documentation -- `fix-version` : the versions in which a bug or enhancement is planned to be released +- `fix-version` (color code `#7ebea5`) : the versions in which a bug or enhancement is planned to be released - this may be used for release planning - (example) `fix-version:10.0.0` -- `affects-version` : the versions in which a bug was found +- `affects-version` (color code `#f19072`) : the versions in which a bug was found - this may be used with `type:bug` - (example) `affects-version:9.1.0` -- `module` : Lucene module +- `module` (color code `#a0d8ef`) : Lucene module - (example) `module:core/index`, `module:analysis` -- `tool` : tooling +- `tool` (color code `#a0d8ef`) : tooling - (example) `tool:build`, `tool:release-wizard` A `type` label is automatically attached to an issue by the issue template that the reporter selected. Other labels such as `fix-version` may be manually added by committers.