... | ... | @@ -57,6 +57,6 @@ Other branches might be force pushed at convenience of the people that work on t |
|
|
|
|
|
Yes, we do. With non-squashed merges, it doesn't add any (historical) value to keep the branches around, and gitlab can automatically delete the branch after the merge.
|
|
|
|
|
|
### How to backport merge request?
|
|
|
### How to backport a Merge Request?
|
|
|
|
|
|
After the merge request is merged there's an option to use the same commits to create new merge request on different branch. Generally, this approach should be used. |
|
|
See the [relevant article](backporting-a-merge-request). |