From 697046c2b2edb902103f9ce2ef42208832627e56 Mon Sep 17 00:00:00 2001
From: George Kalpakas <kalpakas.g@gmail.com>
Date: Sat, 18 May 2019 00:20:47 +0300
Subject: [PATCH] docs: document the `PR action: rerun CI at HEAD` label in
 `TRIAGE_AND_LABELS.md` (#30171)

Related to #29098.

PR Close #30171
---
 docs/TRIAGE_AND_LABELS.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/TRIAGE_AND_LABELS.md b/docs/TRIAGE_AND_LABELS.md
index beea97c569..4622f788eb 100644
--- a/docs/TRIAGE_AND_LABELS.md
+++ b/docs/TRIAGE_AND_LABELS.md
@@ -202,3 +202,9 @@ There should always be a comment added to the PR to explain why the caretaker's
 The comment should be formatted like this: `merge-assistance: <explain what kind of assistance you need, and if not obvious why>`
 
 For example, the PR owner might not be a Googler and needs help to run g3sync; or one of the checks is failing due to external causes and the PR should still be merged.
+
+### `PR action: rerun CI at HEAD`
+* _**Who adds it:** Any team member._
+* _**Who removes it:** The Angular Bot, once it triggers the CI rerun._
+
+This label can be added to instruct the Angular Bot to rerun the CI jobs for the PR at latest HEAD of the branch it targets.