patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 7 Packages Projects Releases Wiki Activity

doc: fix note for forcing a CI recheck

Browse source 
Doc incorrectly said to use the word "retest" in a comment when the
correct word is "recheck".

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2018-04-10 12:02:04 -07:00 committed by Anas Nashif
parent 9bde3c06e1
commit a02e78d3fd
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
CONTRIBUTING.rst
View file

@ -224,9 +224,14 @@ CI is run on the ``shippable`` cloud service and it uses the same tools
described in the `Contribution Tools`_ section. described in the `Contribution Tools`_ section.
The CI results must be green indicating "All checks have passed" before 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 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 again every time the PR is modified with a commit.
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). .. 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 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 GitHub PR page, below the review status. Depending on the success or failure