tools/perf/docs/perf_regression_sheriffing.md - Issue 1770383005: Reduce indentation levels for sheriff docs.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: tools/perf/docs/perf_regression_sheriffing.md

Issue 1770383005: Reduce indentation levels for sheriff docs. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 4 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: tools/perf/docs/perf_regression_sheriffing.md

diff --git a/tools/perf/docs/perf_regression_sheriffing.md b/tools/perf/docs/perf_regression_sheriffing.md

index 8f45b6828abbeb3d24aaa3e000d05864de0f2853..a7cc703c14e28b303adf3ba7c5a438d3ae017e58 100644

--- a/tools/perf/docs/perf_regression_sheriffing.md

+++ b/tools/perf/docs/perf_regression_sheriffing.md

@@ -12,7 +12,7 @@ regression sheriff role is now entirely focused on performance.

* [Follow up on Performance Regressions](#followup)

* [Give Feedback on our Infrastructure](#feedback)

-###<a name="triage"></a> Triage Regressions on the Perf Dashboard

+##<a name="triage"></a> Triage Regressions on the Perf Dashboard

Open the perf dashboard [alerts page](https://chromeperf.appspot.com/alerts).

@@ -73,7 +73,7 @@ below it the dashboard shows graphs of all the alerts checked in that table.

bisects as you feel are necessary to investigate; [give feedback](#feedback)

below if you feel that is not the case.

-###<a name="datastoppage"></a> Triaging data stoppage alerts

+##<a name="datastoppage"></a> Triaging data stoppage alerts

Data stoppage alerts are listed on the

[perf dashboard alerts page](https://chromeperf.appspot.com/alerts). Whenever

@@ -108,7 +108,7 @@ some diagnosis:

sent to the perf dashboard. Are there null values? Sometimes it lists a

reason as well. Please put your finding in the bug.

-###<a name="followup"></a> Follow up on Performance Regressions

+##<a name="followup"></a> Follow up on Performance Regressions

During your shift, you should try to follow up on each of the bugs you filed.

Once you've triaged all the alerts, check to see if the bisects have come back,

@@ -129,7 +129,7 @@ culprit follow up to ensure the CL author addresses the problem. If you are

certain that a specific CL caused a performance regression, and the author does

not have an immediate plan to address the problem, please revert the CL.

-###<a name="feedback"></a> Give Feedback on our Infrastructure

+##<a name="feedback"></a> Give Feedback on our Infrastructure

Perf regression sheriffs have their eyes on the perf dashboard and bisects

more than anyone else, and their feedback is invaluable for making sure these