From a72b2cb58d000d30e6f0f2c1c3aa6b7ca1562bd4 Mon Sep 17 00:00:00 2001 From: Sean Carroll Date: Thu, 5 Sep 2019 21:00:35 +0000 Subject: Apply suggestion to doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md --- doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md b/doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md index fbc95a5ede3..d68fba82f4b 100644 --- a/doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md +++ b/doc/ci/merge_request_pipelines/pipelines_for_merged_results/index.md @@ -65,7 +65,8 @@ otherwise pipelines for merged results won't run and your merge requests will be > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/12996) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.3. -GitLab CI can detect the presence of redundant pipelines, and will cancel them automatically in order to conserve CI resources. +GitLab CI can detect the presence of redundant pipelines, +and will cancel them automatically in order to conserve CI resources. When a user merges a merge request immediately within an ongoing merge train, the train will be reconstructed, as it will recreate the expected -- cgit v1.2.1