Hello everyone,
- The following MR was added to a merge train (via an internal bot).
- This merge train pipeline then started.
- A thread was opened after the pipeline started.
- But the MR was nonetheless merged.
I was expecting to have it removed from the merge train as explained by the documentation.
Is there a bug or is the expected behaviour?
Steps to reproduce
I reproduced the problem in a test repo in two MRs:
- in the first one, I’ve added the MR to a merge train manually: Happy case (!4761) · Merge requests · Nomadic Labs / bruno-tezos · GitLab
- in the second one, I’ve used (a slightly different version of) the internal bot: Happy case (!4758) · Merge requests · Nomadic Labs / bruno-tezos · GitLab
In both cases, I’ve opened a thread after the merge train pipeline started and the MR was merged.
Note that if I tried to make the MR unmergeable by revoking an approval, then the MR would be dropped from the merge train, as it supposed to be. Cf this MR.
Relevant doc: Merge trains | GitLab
Versions
- Self-managed
-
GitLab.comSaaS - Dedicated
- Self-hosted Runners
Versions
- GitLab Runner: 17.4.0