summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-02-12 09:21:12 +1000
committerEvan Read <eread@gitlab.com>2019-02-12 09:21:12 +1000
commit4a2a959180016fd06387f51edd4fda710f160526 (patch)
tree581575914babbea4e82835175098cd5f26d1cf7a
parent71597f9baa4ad409d361677df51a5372589dbf97 (diff)
downloadgitlab-ce-4a2a959180016fd06387f51edd4fda710f160526.tar.gz
Small grammar fix
-rw-r--r--doc/ci/merge_request_pipelines/index.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/merge_request_pipelines/index.md b/doc/ci/merge_request_pipelines/index.md
index 465ecedff32..b7b5c660586 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.
-However, you may what to reverse this behaviour, having all of your jobs to run _except_
+However, you may want 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:
@@ -77,7 +77,7 @@ A:
<<: *only-default
script:
- ...
-
+
B:
<<: *only-default
script: