goreviews.dev

[Ian Lance Taylor]

When I was still at Google I worked on a CL review dashboard based on
the golang.org/x/oscar framework. The dashboard code was all committed
to the repo. The dashboard was designed to be somewhat flexible and to
support any open source project, but it was only actually implemented
for the Go project.

There were some difficulties getting it running on Google Cloud that I
don't fully recall. It had something to do with the amount of memory
it needed at times. It wasn't a good fit for Cloud Run Functions, or
something like that. I'm probably misremembering.

Still, it's an easy program to run on a standalone server. And (full
disclosure) I am currently working at a company, exe.dev, that makes
it very easy to set up a standalone server. So I started it up.

It's visible at https://goreviews.dev.

It lists all CLs against the Go project that are available for review
(it ignores CL marked wait-release or DO NOT REVIEW, and so forth).
There are a lot of open CLs; you can filter them as described in the
search box at the top of the page.

The CLs are grouped. The groups are things like "ready to submit",
"ready to submit when comments are resolved", "ready to submit but
there is a merge conflict", "not ready but written by a maintainer",
and so forth. Concepts like "maintainer" are derived from the repo
history, there isn't an official list or anything.

You can adjust the grouping if you like by editing the box at the
bottom of the page. I hope it's clear but I'm not going to explain it
as I'm not sure anybody wants to adjust the grouping anyhow.

I wrote this dashboard primarily to make my own job (at Google)
easier. Part of that job as I perceived it was to support external
contributors to Go.

That's not my job any more but I hope that people will find the
dashboard useful. Please feel free to open bug reports at
https://go.dev/issue, though I don't promise that I or anybody else
will fix them.

Happy Hacking!

Ian

[Sean Liao]

That looks interesting, I'll have to try it out.
Personally I also try to focus reviews on external contributors.
Right now, I'm just using a Gerrit filter for any non-approvers
(I think it only works if you're an approver):
https://go-review.googlesource.com/q/is:open+-ownerin:cria/project-golang-approvers+-is:wip+-age:14d

- sean

> --
> You received this message because you are subscribed to the Google Groups "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/golang-dev/CAOyqgcXtGuAYe-a84EkD5wwn7w8VhVDKrvMLBOeLmHBbwq3rHQ%40mail.gmail.com.

[David Chase]

That was useful, I found some ready-to-submit CLs that had dropped off the radar, plus some older ones that needed to be abandoned.  

Thanks!

[Jorropo]

That is a useful tool thanks.

There looks to be a bug with:
>  727780 cmd/compile: improve Ctz's limits modeling and add bruteforce tests

the CL is merged but it is still on the list.

To view this discussion visit https://groups.google.com/d/msgid/golang-dev/CAHOpXeX4M44NhjseApmZ2pYWAQzi4VDYwwMR0aP-PsnQJuNONA%40mail.gmail.com.

[Ian Lance Taylor]

On Sun, Mar 1, 2026 at 5:47 PM Jorropo <jorro...@gmail.com> wrote:
>
> There looks to be a bug with:
> > 727780 cmd/compile: improve Ctz's limits modeling and add bruteforce tests
>
> the CL is merged but it is still on the list.

Thanks. Not sure what happened there, but it's fixed now.

Ian