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? #81548
Labels
Comments
Yes |
Yes, would like to keep it if possible. I hope to get back to contributing to clang-tidy again, in the future. |
Yes, planning to get more active in LLVM eventually. |
No, not at the moment anyways. Please feel free to remove my commit access. Thanks! 👍 |
No. Please remove my commit access.
…On Mon, Feb 12, 2024, 19:51 Tom Stellard ***@***.***> wrote:
TLDR: If you want to retain your commit access, please comment on this
issue. Otherwise, you can unsubscribe from this issue and ignore it.
@mprobst <https://github.com/mprobst>, @vmiklos
<https://github.com/vmiklos>, @gislan <https://github.com/gislan>,
@tschwinge <https://github.com/tschwinge>, @Theodor
<https://github.com/Theodor>, @tinti <https://github.com/tinti>, @agners
<https://github.com/agners>, @ianlevesque <https://github.com/ianlevesque>,
@steveire <https://github.com/steveire>, @MadCoder
<https://github.com/MadCoder>
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.
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 priviledged 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
<#81548>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAHXDVWWZLD64SVVCLC66TYTKMIJAVCNFSM6AAAAABDFQN3T2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTCMJSHE3TEMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, I'd like to keep it if possible. |
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.
@mprobst, @vmiklos, @gislan, @tschwinge, @Theodor, @tinti, @agners, @ianlevesque, @steveire, @MadCoder
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.
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 priviledged role and will allow you to do the following:
The text was updated successfully, but these errors were encountered: