-
Notifications
You must be signed in to change notification settings - Fork 18k
access: may-start-trybots #66558
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
Hi abner chenc, Thanks for your contributions and helping maintain the linux/loong64 port. We've added you to the As noted at https://go.dev/wiki/GerritAccess#running-trybots-may-start-trybots, please be sure to at least skim CLs for anything malicious before starting a trybot run. Please let us know if you have any questions or issues. Thanks again. |
I can't select tryjobs, do I need additional permissions? @dmitshur |
The gerrit account |
Yes, |
To confirm, you are able to leave a Commit-Queue+1 vote using your account, is that right? I see here that is so. In that case, the may-start-trybots access is successfully granted to your Gerrit account, but this appears to be something else going wrong when using the Gerrit UI. Please file a new issue with a prefix "gerrit: " so we can continue the investigation there. (Edit: Issue #67468 is filed now.) |
Hi,
I'd like to request the "may-start-trybots" access (https://go-review.googlesource.com/#/admin/groups/1030,members) for myself .
I'm already part of the @golang/loong64 team for a while, and I'll be helping gardening this port in the UTC+8 timezone for the foreseeable future. It's increasingly inconvenient to have to ping other people for TryBot runs as the number of outstanding loong64 CLs keeps growing.
See https://go.dev/wiki/GerritAccess
Thanks.
The text was updated successfully, but these errors were encountered: