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

access: request gomote access #67518

Closed
rhysh opened this issue May 19, 2024 · 4 comments
Closed

access: request gomote access #67518

rhysh opened this issue May 19, 2024 · 4 comments
Assignees
Labels
Access Access request. NeedsFix The path to resolution is known, but the work has not been done.

Comments

@rhysh
Copy link
Contributor

rhysh commented May 19, 2024

I'd like access to gomote, please. (I didn't quite get it set up after the 2022 permissions change, see #49151.) The Google account I use to log in to Gerrit is rhys.hiltner@gmail.com.

Thanks!

"See https://go.dev/wiki/Gomote#access."

@gopherbot gopherbot added the Access Access request. label May 19, 2024
@mauri870
Copy link
Member

cc @golang/release

@cagedmantis cagedmantis added the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label May 20, 2024
@cagedmantis cagedmantis self-assigned this May 20, 2024
@rhysh
Copy link
Contributor Author

rhysh commented May 21, 2024

Hi @cagedmantis @golang/release , I know you're on top of this already — thank you.

I've run into a problem with a recently merged change (https://go.dev/cl/585638) on a secondary port that I can't otherwise access. (Trybots would probably work, though slowly.) I'm nervous about lack of gomote making it hard for me to debug that before the team reverts that CL stack and the release freeze sets in.

Hopefully, there's no need to revert, and there's still time for me to submit the necessary fix. But if you'd be able to grant me this access, it would help me to meet the freeze deadline. Thanks.

@cagedmantis
Copy link
Contributor

Your account should have access now. Thank you for your contributions to Go!

@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 May 22, 2024
@rhysh
Copy link
Contributor Author

rhysh commented May 22, 2024

All set, yes. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Access Access request. NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: Reviewed
Development

No branches or pull requests

5 participants