brintos

brintos / llvm-project-archived public Read only

0
0
Text · 2.3 KiB · 6258a43 Raw
49 lines · plain
1================2LLVM Admin Tasks3================4 5Commit Access Review6--------------------7 8* Frequency: Monthly9* Permissions: Triage10* Description: The `Commit Access Review <https://github.com/llvm/llvm-project/actions/workflows/commit-access-review.yml>`_11  github actions job runs once per month and generates an artifact called 'triagers' which is a list of GitHub users who12  no longer qualify for commit access due to limited activity over the last 12 months.13 14When the job completes, an admin should download the triagers artifact and create an issue asking everyone on15the list if they still need commit access.  Here is an `example issue <https://github.com/llvm/llvm-project/issues/131262>`_.16The issue should have the 'infra:commit-access' label and should use the same description as the example issue.17 18Removing Users from LLVM Committers team19----------------------------------------20 21* Frequencey: Monthly22* Permissions: Admin23* Description: Each month an admin should review any open issues with the infra:commit-access label.24  For any issue that has been open for more than 4 weeks, any user who has not responded on the ticket25  should be moved from the LLVM Committers team to the LLVM Triagers team.26 27Action Secret Rotation28----------------------29 30* Frequency: Monthly31* Permissions: Admin32* Description: Each month an admin should rotate the secrets that are used for GitHub Actions workflows33  in the llvm-project repository.34 35The secrets are personal access tokens that are associated with the llvmbot GitHub account.  An admin36should log in to the llvmbot account, re-generate the personal access tokens and then copy the37new values into the corresponding secret in the llvm-project repo's settings.38 39Grant Commit Access40--------------------41 42* Frequency: Ongoing43* Permissions: Admin44* Description: An admin should periodically review the list of commit access requests.  This can be45  done by searching for issues in the llvm-project repository which have the infra:commit-access-request46  label.  Any user that meets the `commit access requirements <https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access>`_47  should be added to the 'LLVM Committers' team.  The admin should add a comment to the issue when48  an invite to join the team has been sent and then close the issue when the invite has been accepted.49