[llvm] 03b9039 - [docs] Update the commit review admin task with process details (#210420)

via llvm-commits llvm-commits at lists.llvm.org
Fri Jul 17 17:00:07 PDT 2026


Author: Reid Kleckner
Date: 2026-07-18T00:00:02Z
New Revision: 03b9039147cca65e2b4fa3adcbbbf40f73e3a3c9

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

LOG: [docs] Update the commit review admin task with process details (#210420)

As discussed in the infra area team meeting. Mostly this serves as a
place to stash helpful links.

I picked an arbitrary two week timeout for requests. We can re-evaluate at any time.
It seems less than ideal that one needs issue tracker labelling
privileges to reopen the issue, but I think that's accurate.

Added: 
    

Modified: 
    llvm/docs/AdminTasks.md

Removed: 
    


################################################################################
diff  --git a/llvm/docs/AdminTasks.md b/llvm/docs/AdminTasks.md
index 3888942e64846..3e97b3fa5e0dd 100644
--- a/llvm/docs/AdminTasks.md
+++ b/llvm/docs/AdminTasks.md
@@ -1,5 +1,22 @@
 # LLVM Admin Tasks
 
+## Grant Commit Access
+
+- Frequency: Ongoing
+- Permissions: Admin
+- Description: An admin should periodically review the list of commit access requests.
+
+This can be done by searching for issues in the llvm-project repository which have the [`infra:commit-access-request` label].
+Any user that meets the [commit access requirements] should be added to the ['LLVM Committers' team].
+The admin should add a comment to the issue when an invite to join the team has been sent and then close the issue when the invite has been accepted.
+Admins should close issues after sending the invite and invite the requestor to reopen if there are issues.
+If there are insufficient votes and it has been over two weeks since the last update, admins may remove the `infra:commit-access-request` label to take the request off the queue.
+To reopen the request, someone with repository triage or write access must reapply the label to get it back on the dashboard.
+
+[`infra:commit-access-request` label]: https://github.com/llvm/llvm-project/issues/?q=is%3Aissue%20state%3Aopen%20label%3Ainfra%3Acommit-access-request
+[commit access requirements]: https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access
+['LLVM Committers' team]: https://github.com/orgs/llvm/teams/llvm-committers
+
 ## Commit Access Review
 
 - Frequency: Monthly
@@ -30,13 +47,3 @@ The issue should have the 'infra:commit-access' label and should use the same de
 The secrets are personal access tokens that are associated with the llvmbot GitHub account. An admin
 should log in to the llvmbot account, re-generate the personal access tokens and then copy the
 new values into the corresponding secret in the llvm-project repo's settings.
-
-## Grant Commit Access
-
-- Frequency: Ongoing
-- Permissions: Admin
-- Description: An admin should periodically review the list of commit access requests. This can be
-  done by searching for issues in the llvm-project repository which have the infra:commit-access-request
-  label. Any user that meets the [commit access requirements](https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access)
-  should be added to the 'LLVM Committers' team. The admin should add a comment to the issue when
-  an invite to join the team has been sent and then close the issue when the invite has been accepted.


        


More information about the llvm-commits mailing list