From 452f50700f7b5d2cf273297f218e4c37967040db Mon Sep 17 00:00:00 2001 From: Serge Latyntsev Date: Wed, 27 Jan 2021 10:20:49 +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 4305607c4..c40df2891 100644 --- a/docs/en/05_Contributing/16_Maintainer_Guidelines.md +++ b/docs/en/05_Contributing/16_Maintainer_Guidelines.md @@ -113,7 +113,7 @@ Applying [labels](./code/#labels) is the main mechanism used to escalate critica How to do it - - Regularly check the repository for new issues + - Regularly check the repository for new issues or use the ["Untriaged" filter](https://silverstripe-github-issues.now.sh/?mode=untriaged) in our cross-repository issue tracker. - Ideally subscribe to the repository via [GitHub Watch](https://docs.github.com/en/free-pro-team@latest/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) functionality - Read the docs about [how we use labels](./code/#labels) - If unsure about anything, it’s usually good to ask other maintainers for their opinions (on Slack or via mentioning them directly on GitHub)