I've been sending various compiler optimizations (and likely soon, x/tools CLs) where it'd be nice to be able to start my own test runs. It's made more frustrating when sending of stacked CLs where my lack of trybot perms means that nobody (not even people with perms) can run my later CLs, i.e. #65140.

At the Go contributor summit, a few people said I should just file this issue, so here it is 😅

I'm not sure what qualifications are being looked for, but I've landed a few CLs for 1.25/1.26 and plan to land more. I've been working in Go / following the project for a pretty long time, though now more publicly/directly this year as my work finally overlaps.

Could I have perms to start the trybots/LUCI?

See https://go.dev/wiki/GerritAccess

Comment From: gabyhelp

Related Issues

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Comment From: prattmic

Hi Jake,

Thank you for your contributions, and for requesting trybot access! I've added you to the may-start-trybots group, so you should be able to do so now.

As you've probably seen at https://golang.org/wiki/GerritAccess#trybot-access-may-start-trybots, please be sure to skim CLs before starting a trybot run.

Let us know if you have any questions or issues with it, and thanks again!