Skip to content
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

Closed
tstellar opened this issue Feb 12, 2024 · 8 comments
Closed

Do you still need commit access? #81548

tstellar opened this issue Feb 12, 2024 · 8 comments

Comments

@tstellar
Copy link
Collaborator

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:

  • 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.
@ianlevesque
Copy link
Contributor

Yes

@vmiklos
Copy link
Collaborator

vmiklos commented Feb 13, 2024

If you want to retain your commit access, please post a comment on this issue.

Yes, would like to keep it if possible. I hope to get back to contributing to clang-tidy again, in the future.

@tschwinge
Copy link
Member

Yes, planning to get more active in LLVM eventually.

@agners
Copy link
Contributor

agners commented Feb 13, 2024

No, not at the moment anyways. Please feel free to remove my commit access. Thanks! 👍

@tinti
Copy link
Contributor

tinti commented Feb 13, 2024 via email

@gislan
Copy link
Contributor

gislan commented Feb 13, 2024

Yes, I'd like to keep it if possible.

@tstellar
Copy link
Collaborator Author

@mprobst @Theodor @steveire @MadCoder Reminder, if you want to retain your commit access, please comment on this ticket in the next week.

@tstellar
Copy link
Collaborator Author

@tinti @agners @mprobst @Theodor @steveire @MadCoder added to the LLVM Triagers team. If you need write access again, please follow these instructions: https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants