-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeveloperPolicy: Update commit access requirements #127006
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -539,11 +539,21 @@ What are the expectations around a revert? | |
Obtaining Commit Access | ||
----------------------- | ||
|
||
We grant commit access to contributors that can provide a valid justification. | ||
If you would like commit access, please use this `link <https://github.com/llvm/llvm-project/issues/new?title=Request%20Commit%20Access%20For%20%3Cuser%3E&body=%23%23%23%20Why%20Are%20you%20requesting%20commit%20access%20?>`_ to file | ||
Once you have 3 or more merged pull requests, you may use this | ||
link <https://github.com/llvm/llvm-project/issues/new?title=Request%20Commit%20Access%20For%20%3Cuser%3E&body=%23%23%23%20Why%20Are%20you%20requesting%20commit%20access%20?>`_ to file | ||
an 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 | ||
the issue description. If approved, a GitHub invitation will be sent to your | ||
the issue description. Once the issue is created, you will need to get two | ||
current contributors to support your request before commit access will be granted. | ||
|
||
Reviewers of your committed patches will automatically be CCed upon creating the issue. | ||
Most commonly these reviewers will provide the necessary approval, but approvals | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As a reviewer, how am I supposed to provide approval? One of these issues has been assigned to me and I don't know what I'm supposed to do with it, even after reading this documentation and skimming the very long discourse thread. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jayfoad You can just leave a comment say " I support this request" or something similar. |
||
from other LLVM committers are also acceptable. Those reviewing the application are | ||
confirming that you have indeed had three patches committed, and that based on interactions | ||
on those reviews and elsewhere in the LLVM community they have no concern about you | ||
adhering to our Developer Policy and Code of Conduct. | ||
|
||
If approved, a GitHub invitation will be sent to your | ||
GitHub account. In case you don't get notification from GitHub, go to | ||
`Invitation Link <https://github.com/orgs/llvm/invitation>`_ directly. Once | ||
you accept the invitation, you'll get commit access. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can't comment on the lines below directly, but the following paragraph should probably be updated too:
In fact, I think it can be removed entirely, but we may want to keep the bit of information about a valid author name and email address if we don't discuss it anywhere else. |
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit late to the party, but I would suggest something like the following introductory sentence:
This clarifies that one can actually go a long way without requiring commit access.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ldionne I've submitted this as a follow up change here: #128244