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? #90765

Open
tstellar opened this issue May 1, 2024 · 9 comments
Open

Do you still need commit access? #90765

tstellar opened this issue May 1, 2024 · 9 comments

Comments

@tstellar
Copy link
Collaborator

tstellar commented May 1, 2024

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:

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

I'd like to retain commit access.

@asteinha
Copy link
Contributor

asteinha commented May 1, 2024

I don't.

@scui-ibm
Copy link
Contributor

scui-ibm commented May 1, 2024 via email

@tmsri
Copy link
Member

tmsri commented May 1, 2024

I need commit access and I am working on some important features related to Propeller. Thanks!

@luxufan
Copy link
Contributor

luxufan commented May 2, 2024

I'd like to retain commit access. Thanks!

@nigelp-xmos
Copy link
Contributor

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.

@AnastasiaStulova
Copy link
Contributor

I would like to keep my commit access, thanks!

@psoni2628
Copy link
Contributor

I would like to keep my commit access.

@rdhindsa14
Copy link
Contributor

rdhindsa14 commented May 3, 2024 via email

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

10 participants