@@ -28,7 +28,6 @@ Responsibilities include
8000
:
28
28
* PR/issue management
29
29
- Renaming PRs
30
30
- Reviewing PRs
31
- - Closing PRs and issues
32
31
- Assisting contributors
33
32
- Notifying appropriate core developers
34
33
* Applying appropriate labels to PRs/Issues
@@ -37,6 +36,16 @@ Responsibilities include:
37
36
- Good first issue
38
37
- Other categorizations
39
38
39
+ As triagers gain experience, they may have some intuition of when a PR should
40
+ be closed. Triagers can recommend closing a PR, but the final decision must be
41
+ made by a core developer. By having triagers and core developers work together,
42
+ the author receives a careful consideration of their PR. This encourages future
43
+ contributions, regardless of whether their PR is accepted or closed.
44
+
45
+ Triagers can make use of the ``invalid `` and ``stale `` labels to suggest that a
46
+ PR may be suitable for closure. For more information, see the
47
+ :ref: `GitHub PR labels <github-pr-labels >` section.
48
+
40
49
It is also of paramount importance to treat every contributor to the Python
41
50
project kindly and with respect. Regardless of whether they're entirely new
42
51
or a veteran core developer, they're actively ch
8000
oosing to voluntarily donate their
@@ -72,6 +81,7 @@ For every new triager, it would be great to announce them in the python-committe
72
81
mailing list and core-workflow category in Discourse. `Example announcement
73
82
<https://discuss.python.org/t/abhilash-raj-has-been-granted-triage-role-on-github/2089> `_.
74
83
84
+ .. _github-pr-labels :
75
85
76
86
GitHub Labels for PRs
77
87
'''''''''''''''''''''
@@ -93,8 +103,9 @@ expert-asyncio
93
103
invalid
94
104
Used manually for PRs that do not meet basic requirements and
95
105
automatically added by bedevere when PR authors attempt to merge maintenace
96
- branches into the master branch. During competitions, this label causes the
97
- PR to not count towards the author's contributions.
106
+ branches into the master branch. During events such as the October
107
+ Hacktoberfest, this label will prevent the PR from counting toward the
108
+ author's contributions.
98
109
99
110
needs backport to X.Y
100
111
Used for PRs which are appropriate to backport to
0 commit comments