You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our commit message formatting rules instruct people to omit subrepo prefix (like "x/crypto/") from CL subjects, since those are used only in the issue tracker.
On the current Go Release Dashboard, there's a Pending CLs section. It groups CLs based on the path prefix in the CL subject:
Our commit message formatting rules instruct people to omit subrepo prefix (like "x/crypto/") from CL subjects, since those are used only in the issue tracker.
However, the current release dashboard doesn't display the subrepo, making it hard to find (correctly formatted) CLs for a given subrepo package. For example, see https://groups.google.com/d/msg/golang-dev/j7w5535aLjA/BuE0P-wkFwAJ for a recent occurrence (/cc @bcmills).
I'd like to make a change to better visualize the subrepo that a given CL affects. Here's the proposed fix:
It was easy to implement by reusing the logic for doing the subject parsing from gochanges.org.
It also brings a benefit that improperly formatted CL subjects (that don't omit "x/subrepo/" prefix) are easier to spot (and fix):
/cc @bradfitz @andybons @bcmills
The text was updated successfully, but these errors were encountered: