From 465df128a2bbd1e61a562bf7ce1856907083d449 Mon Sep 17 00:00:00 2001
From: Rhys Arkins <rhys@arkins.net>
Date: Sat, 2 Jul 2022 09:24:58 +0200
Subject: [PATCH] docs: priority labels rename
---
docs/development/issue-labeling.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/development/issue-labeling.md b/docs/development/issue-labeling.md
index 089eda4142..99322066f2 100644
--- a/docs/development/issue-labeling.md
+++ b/docs/development/issue-labeling.md
@@ -73,8 +73,8 @@ Add the `breaking` label for Issues or PRs which have changes that are not backw
<summary>Priority</summary>
priority-1-critical
- priority-2-important
- priority-3-normal
+ priority-2-high
+ priority-3-medium
priority-4-low
priority-5-triage
@@ -86,7 +86,7 @@ Try to select the proper priority.
Nothing bad will happen if you select a "wrong" priority.
At a high level: critical = needs immediate fix, important = to be prioritized ahead of others, normal = default priority, low = trivial issue, or impacts a very small % of the user base.
-Use [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Apriority-1-critical+-label%3Apriority-2-important+-label%3Apriority-3-normal+-label%3Apriority-4-low++-label%3Apriority-5-triage) to find any issues which are missing a priority label.
+Use [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Apriority-1-critical+-label%3Apriority-2-high+-label%3Apriority-3-medium+-label%3Apriority-4-low++-label%3Apriority-5-triage) to find any issues which are missing a priority label.
### Platform
--
GitLab