-
Notifications
You must be signed in to change notification settings - Fork 10.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
Do you still need commit access? #91351
Labels
Comments
Comment as requested for retaining commit access. |
Yes, I still need commit access.
Qfrost
***@***.***
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2024年5月7日(星期二) 晚上11:59
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [llvm/llvm-project] Do you still need commit access? (Issue #91351)
Comment as requested for retaining commit access.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Yes, please retain commit access. |
Yes, I do need commit access. Thanks |
Yes. I need commit access. Thanks!
From: Tom Stellard ***@***.***>
Sent: Tuesday, May 7, 2024 8:55 AM
To: llvm/llvm-project ***@***.***>
Cc: Huihui Zhang ***@***.***>; Mention ***@***.***>
Subject: [llvm/llvm-project] Do you still need commit access? (Issue #91351)
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
TLDR: If you want to retain your commit access, please comment on this issue. Otherwise, you can unsubscribe from this issue and ignore it. Commit access is not required to contribute to the project. You can still create Pull Requests without commit access.
@davidbolvansky<https://github.com/davidbolvansky> @eleviant<https://github.com/eleviant> @Weverything<https://github.com/Weverything> @orlov-alex<https://github.com/orlov-alex> @v-kutuzov<https://github.com/v-kutuzov> @qshanz373<https://github.com/qshanz373> @Pretty-box<https://github.com/Pretty-box> @XiaodongLoong<https://github.com/XiaodongLoong> @dfki-mako<https://github.com/dfki-mako> @shabalind<https://github.com/shabalind> @mmalcomson<https://github.com/mmalcomson> @fghanim<https://github.com/fghanim> @dfki-jugr<https://github.com/dfki-jugr> @sajjadm-google<https://github.com/sajjadm-google> @hkmatsumoto<https://github.com/hkmatsumoto> @ebrevnov<https://github.com/ebrevnov> @Qfrost911<https://github.com/Qfrost911> @johnson-troy<https://github.com/johnson-troy> @huihzhang<https://github.com/huihzhang> @luke957<https://github.com/luke957>
LLVM has a policy of downgrading write access to its repositories for accounts with long term inactivity. This is done because inactive accounts with high levels of access tend to be at increased risk of compromise and this is one tactic that the project employs to guard itself from malicious actors. Note that write access is not required to contribute to the project. You can still submit pull requests and have someone else merge them.
Our project policy is to ping anyone with less than five 'interactions' with the repositories over a 12 month period to see if they still need commit access. An 'interaction' and be any one of:
* Pushing a commit.
* Merging a pull request (either their own or someone else’s).
* Commenting on a PR.
If you want to retain your commit access, please post a comment on this issue. If you do not want to keep your commit access, you can just ignore this issue. If you have not responded in 6 weeks, then you will move moved from the 'write' role within the project to the 'triage' role. The 'triage' role is still a privileged role and will allow you to do the following:
* Review Pull Requests.
* Comment on issues.
* Apply/dismiss labels.
* Close, reopen, and assign all issues and pull requests.
* Apply milestones.
* Mark duplicate issues and pull requests.
* Request pull request reviews.
* Hide anyone’s comments.
—
Reply to this email directly, view it on GitHub<#91351>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN64HAE7242SWD2QNP5BDBLZBD2NXAVCNFSM6AAAAABHLJDHTOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DGNZQHAYDGNY>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Yes, I do still need commit access |
Yes, please retain commit access. |
Yes. I need commit access. Thanks! |
Yes, please retain.
Thanks
Evgeniy
ср, 8 мая 2024 г., 14:41 Viktor Kutuzov ***@***.***>:
… Yes. I need commit access. Thanks!
—
Reply to this email directly, view it on GitHub
<#91351 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN2ACGWSK65LCZ3YSSEPVHLZBHJLJAVCNFSM6AAAAABHLJDHTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZHE2DQOJZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, retain please. |
Yes, I do need commit access. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TLDR: If you want to retain your commit access, please comment on this issue. Otherwise, you can unsubscribe from this issue and ignore it. Commit access is not required to contribute to the project. You can still create Pull Requests without commit access.
@davidbolvansky @eleviant @Weverything @orlov-alex @v-kutuzov @qshanz373 @Pretty-box @XiaodongLoong @dfki-mako @shabalind @mmalcomson @fghanim @dfki-jugr @sajjadm-google @hkmatsumoto @ebrevnov @Qfrost911 @johnson-troy @huihzhang @luke957
LLVM has a policy of downgrading write access to its repositories for accounts with long term inactivity. This is done because inactive accounts with high levels of access tend to be at increased risk of compromise and this is one tactic that the project employs to guard itself from malicious actors. Note that write access is not required to contribute to the project. You can still submit pull requests and have someone else merge them.
Our project policy is to ping anyone with less than five 'interactions' with the repositories over a 12 month period to see if they still need commit access. An 'interaction' and be any one of:
If you want to retain your commit access, please post a comment on this issue. If you do not want to keep your commit access, you can just ignore this issue. If you have not responded in 6 weeks, then you will move moved from the 'write' role within the project to the 'triage' role. The 'triage' role is still a privileged role and will allow you to do the following:
The text was updated successfully, but these errors were encountered: