From 83d8f96fe56a4e0936ea68af21e4ffaab52514c9 Mon Sep 17 00:00:00 2001 From: Rhys Arkins <rhys@arkins.net> Date: Sun, 7 Feb 2021 19:10:49 +0100 Subject: [PATCH] docs: add links to issues missing labels (#8574) --- docs/development/issue-labeling.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/development/issue-labeling.md b/docs/development/issue-labeling.md index 644804f4f0..1aa47332a4 100644 --- a/docs/development/issue-labeling.md +++ b/docs/development/issue-labeling.md @@ -30,7 +30,7 @@ Most issues should have a label relating to either a platform, manager, datasour Use these to label the status of an issue. For example, use `status:requirements` to mean that an issue is not yet ready for development to begin. -All open issues should have some `status:*` label applied. +All open issues should have some `status:*` label applied, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Astatus%3Arequirements+-label%3Astatus%3Aready+-label%3Astatus%3Ain-progress+-label%3Astatus%3Ablocked) can identify any which are missing a status label. ### Type of issue @@ -50,6 +50,8 @@ For example, use `type:bug` to label a bug type issue, and use `type:feature` fo Only use `type:refactor` for code changes, don't use `type:refactor` for documentation type changes. Use the `type:help` label for issues which should be converted to a discussion post. +Any issue which has the label `status:ready` should also have a `type:*` label, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Atype%3Abug+label%3Astatus%3Aready+-label%3Atype%3Afeature+-label%3Atype%3Adocs+-label%3Atype%3Arefactor+) can identify any which are missing one. + Add the `breaking` label for Issues or PRs which contain changes that are not backwards compatible and require a major version bump. ### Priority -- GitLab