diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-19 15:57:54 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-19 15:57:54 +0300 |
| commit | 419c53ec62de6e97a517abd5fdd4cbde3a942a34 (patch) | |
| tree | 1f43a548b46bca8a5fb8fe0c31cef1883d49c5b6 /doc/ci/pipelines/merged_results_pipelines.md | |
| parent | 1da20d9135b3ad9e75e65b028bffc921aaf8deb7 (diff) | |
Add latest changes from gitlab-org/gitlab@16-5-stable-eev16.5.0-rc42
Diffstat (limited to 'doc/ci/pipelines/merged_results_pipelines.md')
| -rw-r--r-- | doc/ci/pipelines/merged_results_pipelines.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/ci/pipelines/merged_results_pipelines.md b/doc/ci/pipelines/merged_results_pipelines.md index 1a21a2a9a00..e4f739e8242 100644 --- a/doc/ci/pipelines/merged_results_pipelines.md +++ b/doc/ci/pipelines/merged_results_pipelines.md @@ -21,7 +21,6 @@ Over time, while you're working in the source branch, the target branch might ch Any time you want to be sure the merged results are accurate, you should re-run the pipeline. Merged results pipelines can't run when the target branch has changes that conflict with the changes in the source branch. - In these cases, the pipeline runs as a [merge request pipeline](merge_request_pipelines.md) and [is labeled as `merge request`](merge_request_pipelines.md#types-of-merge-request-pipelines). |