-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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? #117279
Comments
Commenting with a comment |
I would like to keep the commit access. |
Yes please |
I would also like to keep my commit access |
I would like to retain my commit access |
Feel free to remove me, unfortunately I haven't had time to contribute since 2020. Thanks. |
I would like to retain my comment access. Thanks. |
I would like to retain my commit access. Thanks. |
I would also like to retain commit access |
retain, please. |
yup |
I would also like to retain my commit access. Thanks. |
Would like to retain. |
I'd like to retain commit access. |
Ceci est un comment. |
Please retain my commit access thank you! |
Please keep it! |
Yes, please. |
Please maintain my access. Thanks! |
Please keep my access, thanks. |
Please retain access |
I'ld like to retain my access, please! |
I would like to retain access. |
Closing due to a bug in the script that caused people to be notified twice within a one year period. I'm going to fix the bug and rerun the script. Sorry for the inconvenience. |
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.
@pmatos @vmiklos @gislan @ashay @tschwinge @Theodor @ianlevesque @steveire @nvoorhies @comex @whitequark @filcab @powderluv @aadsm @splhack @simonpcook @tJener @vedantk @vchuravy @rudkx @Lekensteyn @luismarques @waywardmonkeys @vmurali @werat @petar-jovanovic @luqmana @last5bits @pepsiman @DanAlbert @chisophugis @kaladron @awatry @stephenneuendorffer @yuanfang-chen @zatrazz @gottesmm @jackoalan @shawnl @aperez @chfast @vext01 @cchen15 @sheredom @sivachandra @DiamondLovesYou @bryant @bhamiltoncx @mantognini @chandlerc
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 4 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: