5 Commits

Author SHA1 Message Date
Tom Stellard
2359635457
workflows/commit-access-review: Exclude users who have recently requested access (#119102)
Now that we are accepting commit access requests via GitHub issues, we
can keep track of who has recently requested access.
2025-01-07 15:01:49 -08:00
Tom Stellard
0d5ae3632d
workflows/commit-access-review: Use Python APIs for graphql queries (#108903) 2024-12-06 18:34:03 -08:00
Tom Stellard
c49d809f2f
workflows/commit-access-review: Update label name (#118903)
We switched to using a new label name for tracking commit access
requests.
2024-12-06 18:16:30 -08:00
Tom Stellard
f14fd32602
workflows/commit-access-review: Use get_collaborators() function (#108313)
This gets us the full list of users with commit access to
llvm/llvm-project rather than the list of people in the llvm-committers
team. This will ensure we are able everyone to track everyone with
commit access in case they receive access some other way.
2024-09-16 13:37:49 -07:00
Tom Stellard
84efc8ed46
[workflows] Add a new workflow for checking commit access qualifications (#93301)
This workflow produces a list of users that should be moved to the LLVM
Triagers team. An admin will review the list and then manually move
people to the LLVM Triagers Team.

I've also added some documentation to the Developer Policy about the
Triage Role.

See
https://discourse.llvm.org/t/rfc2-new-criteria-for-commit-access/77110
for more details.
2024-08-15 17:08:24 -07:00