aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/dev/sheriffing
diff options
context:
space:
mode:
authorGravatar kjlubick <kjlubick@google.com>2016-02-08 05:23:37 -0800
committerGravatar Commit bot <commit-bot@chromium.org>2016-02-08 05:23:37 -0800
commita58ec2162c0a1e0c934d4ce485019303c51349a4 (patch)
tree479e2349ee86371060589eff92e150afde9673ae /site/dev/sheriffing
parent8dbe00293f5ce05ac99b72e33bf70373bb63e293 (diff)
Fix autoroll link
Diffstat (limited to 'site/dev/sheriffing')
-rw-r--r--site/dev/sheriffing/index.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/site/dev/sheriffing/index.md b/site/dev/sheriffing/index.md
index dd602f13a1..47b5c85b83 100644
--- a/site/dev/sheriffing/index.md
+++ b/site/dev/sheriffing/index.md
@@ -38,13 +38,13 @@ Below is a brief summary of what the sheriff does for each task:
<a name="deps_rolls"></a>
### DEPS rolls
-* Ensure that [AutoRoll Bot](https://skia-tree-status.appspot.com/set_arb_action)'s DEPS rolls land successfully.
+* Ensure that [AutoRoll Bot](https://autoroll.skia.org)'s DEPS rolls land successfully.
<a name="gold_and_perf"></a>
### Gold and Perf
* Pay attention for new [Perf](https://perf.skia.org/) and [Gold](https://gold.skia.org/) alerts (by clicking on the bell at the top right of the [status page](https://status.skia.org)).
* The sheriff's duty here is to make sure that when developers introduce new images or new perf regressions, that they are aware of what happened, and they use these tools to take appropriate action.
-
+
<a name="sheriff_doc"></a>
### Documentation
* Improve/update this documentation page for future sheriffs, especially the [Tips section](#tips).
@@ -149,7 +149,7 @@ If a Skia CL changes layout tests, but the new images look good, the tests need
* Retry the DEPS roll (for the 1st/dispreferred option this usually means just retrying the layout bots)
* Make a Blink patch by editing LayoutTests/TestExpectations
- * Add # comment about what has changed
+ * Add # comment about what has changed
* Add line(s) like the following after the comment:
* crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsRebaseline ]
* (if you took the second option above you can just edit the existing line(s))