diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-17 12:10:30 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-17 12:10:30 +0300 |
| commit | 5dc25b7a85dbda5e3ad67c8a01d7f6487fc4142c (patch) | |
| tree | 453f9f1826abeb6f0ec977e4101e045534d4115b /doc/development/pipelines | |
| parent | 82dd7e4df10da0e033359a0bc1fd490502081bde (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/pipelines')
| -rw-r--r-- | doc/development/pipelines/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/pipelines/index.md b/doc/development/pipelines/index.md index fff64eef639..316ae3c83cd 100644 --- a/doc/development/pipelines/index.md +++ b/doc/development/pipelines/index.md @@ -214,7 +214,7 @@ graph LR ## Merge Trains -### Why do we need to have a “stable” master branch to enable merge trains? +### Why do we need to have a "stable" master branch to enable merge trains? If the master branch is unstable (i.e. CI/CD pipelines for the master branch are failing frequently), all of the merge requests pipelines that were added AFTER a faulty merge request pipeline would have to be **cancelled** and **added back to the train**, which would create a lot of delays if the merge train is long. |