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.

Sign up for GitHub

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

Jump to bottom

access: Requesting Try-Bots Access and Self-Assign Github Issues #65936

Closed
raghvenders opened this issue Feb 25, 2024 · 2 comments
Closed

access: Requesting Try-Bots Access and Self-Assign Github Issues #65936

raghvenders opened this issue Feb 25, 2024 · 2 comments
Assignees
@dmitshur
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Unreleased

Comments

@raghvenders
Copy link
Contributor

raghvenders commented Feb 25, 2024 •
edited

Hello,

Per https://github.com/golang/go/wiki/GithubAccess I'd like to request Try-Bots Access and self-Assign Github issues. I have already raised a request on this (#64523) and have been advised on wait time. I am re-requesting the access.

gerrit account: raghvenders@gmail.com
github account: raghvenders

Thank you!
@mauri870 mauri870 added the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label Feb 26, 2024
@mauri870
Copy link
Member

cc @golang/release

@mauri870 mauri870 added this to the Unreleased milestone Feb 26, 2024
@dmitshur dmitshur self-assigned this Apr 5, 2024
@dmitshur
Copy link
Contributor

Hi @raghvenders, thanks for your contributions to Go so far.

We discussed this request. We generally look for contributors to have a more established track record of contributions before considering granting trybot access, and it doesn't seem enough time has passed for that to happen yet. You should feel free to request someone else on the CL to run trybots when needed in the meantime. Thanks again.

I have sent you an invite to the go-assignees group (https://go.dev/wiki/GithubAccess#assignees).

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. labels Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmitshur dmitshur

Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
Access
Status: Done
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@dmitshur @raghvenders @mauri870