Add the ability to configure triggering pipelines on target branch change
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
In this issue: #36995 (closed) the behavior of the triggering pipeline was changed. Now when you change the target branch in the merge request the pipeline is triggered. There is no way to configure that and to force the "old" behavior, as confirmed here: #36995 (comment 1335491918).
In our team, we are usually opening a few small merge requests to speed up and simplify the code review. The merge request are targeting each other, for example: "A -> develop", "B -> A", "C -> B". So there is some kind of tree. When we start merging, the first merge request to merge is a merge request "A" which targets develop. After the merge, the target of merge request "B" is automatically changed from "A" to develop. Now with the new version of GitLab, it triggers the merge requests pipelines. In the case of a few merge requests, it slows us down a lot.
Add the ability to control that behavior, to enable the option to not trigger the pipelines on every target branch change.