PerfSheriff: update link for triage backlog
The current link is a go link, which only works on @google account whereas most perf sheriffs will be working from @chromium accounts, so using a direct link is better. Change-Id: I3a277a67733b6af06aa19c42e61a22e502cce936 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422188 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#830567}
This commit is contained in:

committed by
Commit Bot

parent
81304b8571
commit
7d19683be5
@ -62,9 +62,10 @@ issues:
|
||||
## Follow up on Performance Regressions
|
||||
|
||||
Please spend any spare time driving down bugs from the [regression
|
||||
backlog](http://go/triage-backlog). Treat these bugs as you would your own --
|
||||
investigate the regressions, find out what the next step should be, and then
|
||||
move the bug along. Some possible next steps and questions to answer are:
|
||||
backlog](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Performance%3DSheriff+Type%3ABug+modified-before%3Atoday-6&sort=-modified).
|
||||
Treat these bugs as you would your own -- investigate the regressions, find out
|
||||
what the next step should be, and then move the bug along. Some possible next steps
|
||||
and questions to answer are:
|
||||
|
||||
* Should the bug be closed?
|
||||
* Are there questions that need to be answered?
|
||||
|
Reference in New Issue
Block a user