summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <marcia@gitlab.com>2019-04-18 09:04:59 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-04-18 09:04:59 +0000
commit935de589000789191e451ee76cbaddebcf9a2c28 (patch)
tree94b073c2b611207988637ad64af00b6387a1e820
parentc50b9be4af3908662a4b6ae683371d3f00a0ec26 (diff)
downloadgitlab-ce-935de589000789191e451ee76cbaddebcf9a2c28.tar.gz
Doc fixes for the release post 11.10
-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 2de751c9e62..6a03ab910fc 100644
--- a/doc/ci/merge_request_pipelines/index.md
+++ b/doc/ci/merge_request_pipelines/index.md
@@ -69,7 +69,7 @@ when a merge request was created or updated. For example:
## Combined ref pipelines **[PREMIUM]**
-> [GitLab Premium](https://about.gitlab.com/pricing/) 11.10.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/7380) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.10.
It's possible for your source and target branches to diverge, which can result
in the scenario that source branch's pipeline was green, the target's pipeline was green,