diff options
Diffstat (limited to 'doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md')
| -rw-r--r-- | doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md b/doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md index b8976ffae7f..44e63d46901 100644 --- a/doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md +++ b/doc/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md @@ -86,12 +86,15 @@ In case, you have a high-priority merge request (e.g. critical patch) to be merg you can use **Merge Immediately** option for bypassing the merge train. This is the fastest option to get the change merged into the target branch. - + However, every time you merge a merge request immediately, it could affect the existing merge train to be reconstructed, specifically, it regenerates expected merge commits and pipelines. This means, merging immediately essentially wastes -CI resources. +CI resources. Because of these downsides, you will be asked to confirm before +the merge is initiated: + + ## Troubleshooting |