tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 12:05:37 +00:00
Code Issues Projects Releases Wiki Activity

Update docs/en/05_Contributing/16_Maintainer_Guidelines.md

Browse Source 
Co-authored-by: Ingo Schommer <ingo@silverstripe.com>
This commit is contained in:
Serge Latyntsev 2021-01-27 10:18:47 +13:00 committed by GitHub
parent d5eb3216b3
commit 53a1577f08
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/05_Contributing/16_Maintainer_Guidelines.md
View File

@ -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