From 53a1577f0860f336bff0d9df9950cdb525b60c3d Mon Sep 17 00:00:00 2001 From: Serge Latyntsev Date: Wed, 27 Jan 2021 10:18:47 +1300 Subject: [PATCH] Update docs/en/05_Contributing/16_Maintainer_Guidelines.md Co-authored-by: Ingo Schommer --- docs/en/05_Contributing/16_Maintainer_Guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/05_Contributing/16_Maintainer_Guidelines.md b/docs/en/05_Contributing/16_Maintainer_Guidelines.md index e7b9d349e..2bee6d029 100644 --- a/docs/en/05_Contributing/16_Maintainer_Guidelines.md +++ b/docs/en/05_Contributing/16_Maintainer_Guidelines.md @@ -109,7 +109,7 @@ Some of the Supported Modules have their own house rules (usually explained in t Triaging GitHub issues and pull requests imply responding to issue/pr creators with following closing or labelling. Labelling allows the other maintainers to pick up proper issues/prs accordingly to their dedication or available resources. -It is also the main way to escalate critical and high impact issues, give feedback to the community, or peer review a PR and let other maintainers know it is “good to be merged on green CI tests”. +Applying [labels](./code/#labels) is the main mechanism used to escalate critical and high impact issues, give feedback to the community, or peer review a PR and let other maintainers know it is “good to be merged on green CI tests”. How to do it