From cddc732c710e9251a060a9021ab22cb48e34a530 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dan=20No=C3=A9?= <dpn@google.com>
Date: Tue, 4 Sep 2018 13:12:28 -0400
Subject: [PATCH] CONTRIBUTING: Document 'kick-ci' trick. (#4335)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Risk Level: doc-only
Testing: n/a doc-only change
Docs Changes: CONTRIBUTING.md change.
Release Notes: n/a

Signed-off-by: Dan Noé <dpn@google.com>
---
 CONTRIBUTING.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 41ee9af1e740..70c5c666ab8c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -214,3 +214,17 @@ git push origin -f
 
 Note, that in general rewriting history in this way is a hinderance to the review process and this
 should only be done to correct a DCO mistake.
+
+## Triggering CI re-run without making changes
+
+Sometimes CI test runs fail due to obvious resource problems or other issues
+which are not related to your PR. It may be desirable to re-trigger CI without
+making any code changes. Consider adding an alias into your `.gitconfig` file:
+
+```
+[alias]
+    kick-ci = !"git commit -s --allow-empty -m 'Kick CI' && git push"
+```
+
+Once you add this alias you can issue the command `git kick-ci` and the PR
+will be sent back for a retest.