[llvm] [Workflows] Enable commit access requests via GitHub issues (PR #100458)

Tom Stellard via llvm-commits llvm-commits at lists.llvm.org
Thu Jul 25 12:12:52 PDT 2024


================
@@ -476,11 +476,12 @@ Obtaining Commit Access
 -----------------------
 
 We grant commit access to contributors with a track record of submitting high
-quality patches.  If you would like commit access, please send an email to
-`Chris <mailto:clattner at llvm.org>`_ with your GitHub username.  This is true
-for former contributors with SVN access as well as new contributors. If
-approved, a GitHub invitation will be sent to your GitHub account. In case you
-don't get notification from GitHub, go to
+quality patches.  If you would like commit access, please use this `link
+<https://github.com/llvm/llvm-project/issues/new?title=Request%20Commit%20Access%20For%20<user>&body=%23%23%23%20Why%20Are%20you%20requesting%20commit%20access%20?>`_ to file
+and issue and request commit access.  Replace the <user> string in the title
+with your github username, and explain why you are requesting commit access in
----------------
tstellar wrote:

I don't disagree that the explanation may be awkward, but according to @lattner's [description](https://discourse.llvm.org/t/rfc-new-criteria-for-commit-access/76290/81) of how the current process works, users are asked for a justification.

I may be overly cautious here, but I've [proposed](https://discourse.llvm.org/t/rfc-new-criteria-for-commit-access/76290) changing the commit access requirements in the past, and since this proposal was rejected,
I'm trying really hard to not change or even give the impression of changing anything about the current process, because I don't want people to think I'm trying to backdoor changes into the process when that's not my intention.

https://github.com/llvm/llvm-project/pull/100458


More information about the llvm-commits mailing list