summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Lenny <jlenny@gitlab.com>2019-02-08 07:57:09 +0000
committerJason Lenny <jlenny@gitlab.com>2019-02-08 07:57:09 +0000
commit985694883d8addcdcf71d4e69b274d5889c4e4f1 (patch)
tree245252f2546ff348ab5f0713e2098846af37d147
parent42c9e39785ab625fef16f2e8b8a897599754d3d8 (diff)
downloadgitlab-ce-985694883d8addcdcf71d4e69b274d5889c4e4f1.tar.gz
Apply suggestion to doc/ci/merge_request_pipelines/index.md
-rw-r--r--doc/ci/merge_request_pipelines/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/merge_request_pipelines/index.md b/doc/ci/merge_request_pipelines/index.md
index 8da357fc242..be739b6690d 100644
--- a/doc/ci/merge_request_pipelines/index.md
+++ b/doc/ci/merge_request_pipelines/index.md
@@ -61,7 +61,7 @@ The same tag is shown on the pipeline's details:
The behavior of the `only: merge_requests` rule is such that _only_ jobs with
that rule are run in the context of a merge request; no other jobs will be run.
-This behavior may not be intuitive when you want all of your jobs to run _except_
+However, you may what to reverse this behaviour, having all of your jobs to run _except_
for one or two. Consider the following pipeline, with jobs A B and C. If you want
all pipelines to always run `A` and `B`, but only want `C` to run for a merge request,
you can configure your `.gitlab-ci.yml` file as follows: