[llvm] cd60247 - [llvm][docs] Document how to ask for things other than commit access (#146340)

[via llvm-commits]

Author: David Spickett
Date: 2025-07-01T10:59:59+01:00
New Revision: cd60247a0fca43964103775a4c18a01e0ae1bf0e

URL: https://github.com/llvm/llvm-project/commit/cd60247a0fca43964103775a4c18a01e0ae1bf0e
DIFF: https://github.com/llvm/llvm-project/commit/cd60247a0fca43964103775a4c18a01e0ae1bf0e.diff

LOG: [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

Added: 
    

Modified: 
    llvm/docs/DeveloperPolicy.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst
index 6b60812df83bd..0c500b9bc826b 100644
--- a/llvm/docs/DeveloperPolicy.rst
+++ b/llvm/docs/DeveloperPolicy.rst
@@ -550,6 +550,17 @@ after they are committed, depending on the nature of the change).  You are
 encouraged to review other peoples' patches as well, but you aren't required
 to do so.
 
+Obtaining Other Access or Permissions
+-------------------------------------
+
+To obtain access other than commit access, you can raise an issue like the one
+for obtaining commit access. However, instead of including PRs you have authored,
+include evidence of your need for the type of access you want.
+
+For example, if you are helping to triage issues and want the ability to add
+labels, include links to issues you have triaged previously and explain how
+having this ability would help that work.
+
 .. _discuss the change/gather consensus:
 
 Making a Major Change