-
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? #90765
Comments
I'd like to retain commit access. |
I don't. |
I’d like to retain my commit access. Thanks
Best Regards,
Shimin Cui
IBM Toronto Software Lab
8200 Warden Ave, Markham, ON, L6G 1C7
***@***.******@***.***>
From: Tom Stellard ***@***.***>
Date: Wednesday, May 1, 2024 at 3:31 PM
To: llvm/llvm-project ***@***.***>
Cc: Shimin Cui ***@***.***>, Mention ***@***.***>
Subject: [EXTERNAL] [llvm/llvm-project] Do you still need commit access? (Issue #90765)
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
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!9JFQ-d758eTwfT7aJuzLendWveyOyOZAJ2LaooNwVIDeGqiWDC_XIyx45gi-SAysJhrhTEQ-kgwKUsHhROXHiA$>
Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!9JFQ-d758eTwfT7aJuzLendWveyOyOZAJ2LaooNwVIDeGqiWDC_XIyx45gi-SAysJhrhTEQ-kgwKUsHhROXHiA$>
ZjQcmQRYFpfptBannerEnd
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.
@nigelp-xmos<https://github.com/nigelp-xmos> @adibiagio<https://github.com/adibiagio> @reidtatge<https://github.com/reidtatge> @bixia1<https://github.com/bixia1> @asteinha<https://github.com/asteinha> @rdhindsa14<https://github.com/rdhindsa14> @tarinduj<https://github.com/tarinduj> @riccibruno<https://github.com/riccibruno> @Marcythm<https://github.com/Marcythm> @zukatsinadze<https://github.com/zukatsinadze> @luxufan<https://github.com/luxufan> @StuartDBrady<https://github.com/StuartDBrady> @AnastasiaStulova<https://github.com/AnastasiaStulova> @scui-ibm<https://github.com/scui-ibm> @jedilyn<https://github.com/jedilyn> @psoni2628<https://github.com/psoni2628> @tmsri<https://github.com/tmsri> @diseraluca<https://github.com/diseraluca> @thomasjoerg<https://github.com/thomasjoerg> @ekieri<https://github.com/ekieri>
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<#90765>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJFRIAADIEQ7N2IMHU4VDFTZAE7INAVCNFSM6AAAAABHCOJG62VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TIMBWGU2DCMQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I need commit access and I am working on some important features related to Propeller. Thanks! |
I'd like to retain commit access. Thanks! |
Yes please I would ideally like to keep commit access. Still active on XCore even though upstream backend not very active. Before I had commit access, my reviewers were very willing to commit for me, but it was hard to find a reviewer in the first place. Is there guidance or policy on who to contact to commit PRs to our own area of code, if we don't have commit access? Thanks. |
I would like to keep my commit access, thanks! |
I would like to keep my commit access. |
I would like to keep my commit access. Thanks!
…On Thu, May 2, 2024 at 5:26 AM Prabhdeep Soni ***@***.***> wrote:
I would like to keep my commit access.
—
Reply to this email directly, view it on GitHub
<#90765 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AITKY2FQHT5G5FZMWMVOGQ3ZAIWH5AVCNFSM6AAAAABHCOJG62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQGM3TGMRSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
@nigelp-xmos @adibiagio @reidtatge @bixia1 @asteinha @rdhindsa14 @tarinduj @riccibruno @Marcythm @zukatsinadze @luxufan @StuartDBrady @AnastasiaStulova @scui-ibm @jedilyn @psoni2628 @tmsri @diseraluca @thomasjoerg @ekieri
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: