diff options
| author |  rmistry <rmistry@google.com> | 2015-11-18 06:47:11 -0800 |
|---|---|---|
| committer |  Commit bot <commit-bot@chromium.org> | 2015-11-18 06:47:11 -0800 |
| commit | 7224ae9d519f35a1fcfa0493b1bb77233d92009b (patch) | |
| tree | a05ebfe90fc7385728c0b70286de47ce0aa80543 /site/dev/sheriffing | |
| parent | f970ad6ee1161bc99bcdeed511498d6d4e9531b0 (diff) | |
Update all code site issue tracker links to point to bug.skia.org
BUG=skia:
NOTRY=true
DOCS_PREVIEW= https://skia.org/?cl=1461613002
Review URL: https://codereview.chromium.org/1461613002
Diffstat (limited to 'site/dev/sheriffing')
| -rw-r--r-- | site/dev/sheriffing/index.md | 4 | ||||
| -rw-r--r-- | site/dev/sheriffing/trooper.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/site/dev/sheriffing/index.md b/site/dev/sheriffing/index.md index 052388c11a..dd602f13a1 100644 --- a/site/dev/sheriffing/index.md +++ b/site/dev/sheriffing/index.md @@ -34,7 +34,7 @@ Below is a brief summary of what the sheriff does for each task: * Track down people responsible for breakages and revert broken changes if there is no easy fix. * Close and open the [tree](http://skia-tree-status.appspot.com). * Keep the builder comments on the [status page](https://status.skia.org) up to date. -* File or follow up with [BreakingTheBuildbots bugs](https://code.google.com/p/skia/issues/list?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs). +* File or follow up with [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs). <a name="deps_rolls"></a> ### DEPS rolls @@ -75,7 +75,7 @@ Tips for sheriffs ### When to file bugs Pay close attention to the "Failures" view in the [status page](https://status.skia.org). -Look at all existing [BreakingTheBuildbots bugs](https://code.google.com/p/skia/issues/list?q=label:BreakingTheBuildbots). If the list is kept up to date then it should accurately represent everything that is causing failures. If it does not, then please file/update bugs accordingly. +Look at all existing [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). If the list is kept up to date then it should accurately represent everything that is causing failures. If it does not, then please file/update bugs accordingly. <a name="how_close_tree"></a> diff --git a/site/dev/sheriffing/trooper.md b/site/dev/sheriffing/trooper.md index a73aaf100f..040239a62a 100644 --- a/site/dev/sheriffing/trooper.md +++ b/site/dev/sheriffing/trooper.md @@ -48,7 +48,7 @@ Tips for troopers - Monitoring alerts, including prober, collectd, and others - Disconnected build slaves -- These alerts generally do not auto-dismiss ([issue here](https://code.google.com/p/skia/issues/detail?id=4292)): +- These alerts generally do not auto-dismiss ([issue here](https://bug.skia.org/4292)): - Build slaves that failed a step - Disconnected devices (these are detected as the "wait for device" step failing) |