From a49b0ea078ad2eadd5caf9d79d82b462014f39c9 Mon Sep 17 00:00:00 2001 From: Monty Taylor Date: Thu, 5 Oct 2017 16:16:19 -0500 Subject: [PATCH] Fix doc typo that missed important words The docs say that job.post-review is set to True if the job is defined in an untrusted-project. However, that's only true if the job uses secrets. Change-Id: Iae85b59848144504fbcb47d4fa95a6c3cb3c0207 --- doc/source/user/config.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/source/user/config.rst b/doc/source/user/config.rst index f55fb4fc4b..c4014e2bb0 100644 --- a/doc/source/user/config.rst +++ b/doc/source/user/config.rst @@ -952,12 +952,12 @@ Here is an example of two job definitions: A boolean value which indicates whether this job may only be used in pipelines where :attr:`pipeline.post-review` is - ``true``. This is automatically set to ``true`` if this job is - defined in a :term:`untrusted-project`. It may be explicitly - set to obtain the same behavior for jobs defined in - :term:`config projects `. Once this is set to - ``true`` anywhere in the inheritance hierarchy for a job, it - will remain set for all child jobs and variants (it can not be + ``true``. This is automatically set to ``true`` if this job + uses a :ref:`secret` and is defined in a :term:`untrusted-project`. + It may be explicitly set to obtain the same behavior for jobs + defined in :term:`config projects `. Once this + is set to ``true`` anywhere in the inheritance hierarchy for a job, + it will remain set for all child jobs and variants (it can not be set to ``false``). .. _project: