From a02e78d3fddedc57a1833327cf2a1e1da0573ac6 Mon Sep 17 00:00:00 2001 From: "David B. Kinder" Date: Tue, 10 Apr 2018 12:02:04 -0700 Subject: [PATCH] doc: fix note for forcing a CI recheck Doc incorrectly said to use the word "retest" in a comment when the correct word is "recheck". Signed-off-by: David B. Kinder --- CONTRIBUTING.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index b34ef449647..e151b030e0b 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -224,9 +224,14 @@ CI is run on the ``shippable`` cloud service and it uses the same tools described in the `Contribution Tools`_ section. The CI results must be green indicating "All checks have passed" before the Pull Request can be merged. CI is run when the PR is created, and -again every time the PR is modified with a commit. You can also force -the CI system to recheck a PR by adding a comment to the PR saying -simply ``retest`` in the message (helpful if the CI system fails unexpectedly). +again every time the PR is modified with a commit. + +.. note:: + + You can also force + the CI system to recheck a PR by adding a comment to the PR saying + simply ``recheck`` in the message (helpful if the CI system fails + unexpectedly). The current status of the CI run can always be found at the bottom of the GitHub PR page, below the review status. Depending on the success or failure