August 2019
Beginner
608 pages
16h 7m
English
For an individual project, you can define merge request behavior. For example, you can define how GitLab will execute merges on the server. For every executed merge request, there is a Git session on the server running the same Git binary that you have on your workstation. For instance, you can specify that the server side never does a merge commit:

In version 12.0 of GitLab, the concept of merge trains was added. If you enable this, all the merges must pass in sequence, and your merge will be a part of this train. The merges only succeed as a whole, and this use case is common in Enterprise environments where different teams ...
Read now
Unlock full access