-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Request Commit Access For quic-garvgupt #140512
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
Comments
@quic-garvgupt thank you for applying for commit access. Please review the project's code review policy. |
@llvm/issue-subscribers-infra-commit-access-request Author: Garvit Gupta (quic-garvgupt)
### Why Are you requesting commit access ?
I had commit access until today I got to know that I have been removed from committers list to triage list. I didn't have any period of inactivity as can also seen below on my github dashboard. I have currently a stack of 7PRs in flight and I am regularly engaging with reviewers through these patches especially for the last couple of months. Not sure how I got removed from the list.
Github Profile - https://github.com/quic-garvgupt Also, I have 3 patches committed to llvm project |
Activity Summary:
|
I'm supportive of this request. |
Hi @tstellar , can you sent me an invite for commit access. Currently I have stack of PR on the branch off the main llvm repo, and until I have write access I cannot push to the branch. I will really appreciate if I can get commit access at the earliest. Thanks |
Why Are you requesting commit access ?
I had commit access until today I got to know that I have been removed from committers list to triage list. I didn't have any period of inactivity as can also seen below on my github dashboard. I have currently a stack of 7PRs in flight and I am regularly engaging with reviewers through these patches especially for the last couple of months. Not sure how I got removed from the list.
Github Profile - https://github.com/quic-garvgupt
Also, I have 3 patches committed to llvm project
The text was updated successfully, but these errors were encountered: