-
Notifications
You must be signed in to change notification settings - Fork 18.1k
access: give zx2c4 access to gomote and github groups #44579
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
/cc @golang/release |
We've put new gomote accounts on hold while we get new infrastructure in place. |
Hi Jason, The gomote accounts are still on hold as work on the new infrastructure continues, but you also requested GitHub access in this issue, so I wanted to help here by moving that along. Since you've already been granted Gerrit Code-Review+2 access, that implies GitHub access as well. I've sent an invite to your GitHub account just now. As a reminder, please be sure to review https://go.dev/wiki/Gardening and https://go.dev/wiki/HandlingIssues as part of helping garden issues. If uncertain about something, don't hesitate to ask. Thank you for your continued contributions to the Go project! |
@zx2c4 do you still need/want gomote access? We're ready to give it out if you want it. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to fix the race detector on windows/amd64 so that it works with recent mingw (on both gcc and clang). It looks like part of that entails rebuilding using
x/build/cmd/racebuild
:It seems like I need gomote permissions for this to work.
And then while I'm knocking on the permission door, I figure I should use the opportunity to mention the Github groups too:
https://github.com/orgs/golang/teams/go-assignees
https://github.com/orgs/golang/teams/go-approvers
per https://github.com/golang/go/wiki/GithubAccess
CC @golang/release @dmitshur
The text was updated successfully, but these errors were encountered: