summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Lenny <jlenny@gitlab.com>2019-02-11 08:08:00 +0000
committerJason Lenny <jlenny@gitlab.com>2019-02-11 08:08:00 +0000
commitba1b2ab9d9dd15eb8d04c1bdeed9a68989551a3e (patch)
treedc28bc89fc6692eb7855adaeaa36fa3713368152
parent985694883d8addcdcf71d4e69b274d5889c4e4f1 (diff)
downloadgitlab-ce-ba1b2ab9d9dd15eb8d04c1bdeed9a68989551a3e.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 be739b6690d..f24c5ad40a9 100644
--- a/doc/ci/merge_request_pipelines/index.md
+++ b/doc/ci/merge_request_pipelines/index.md
@@ -62,7 +62,7 @@ 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.
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
+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: