Skip to content

Commit cd60247

Browse files
[llvm][docs] Document how to ask for things other than commit access (#146340)
This is the implicit process but useful to spell it out I think. To give folks more confidence in asking. Inspired by https://discourse.llvm.org/t/request-github-issue-triage-permission-for-labeling-clang-issues/87126/1
1 parent 5c08aea commit cd60247

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

llvm/docs/DeveloperPolicy.rst

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -550,6 +550,17 @@ after they are committed, depending on the nature of the change). You are
550550
encouraged to review other peoples' patches as well, but you aren't required
551551
to do so.
552552

553+
Obtaining Other Access or Permissions
554+
-------------------------------------
555+
556+
To obtain access other than commit access, you can raise an issue like the one
557+
for obtaining commit access. However, instead of including PRs you have authored,
558+
include evidence of your need for the type of access you want.
559+
560+
For example, if you are helping to triage issues and want the ability to add
561+
labels, include links to issues you have triaged previously and explain how
562+
having this ability would help that work.
563+
553564
.. _discuss the change/gather consensus:
554565

555566
Making a Major Change

0 commit comments

Comments
 (0)