Merge Request targeting a topic
There's nothing that prevents the target GitLab branch of a Merge Request to be a topic. Many people would probably consider bad practice to target a topic, but I wouldn't go as far as calling them illegitimate.
The outcome would be surprising for most users: accepting the Merge Request will publish its final changeset, hence in particular the target topic.
I think a full consistent behaviour for MRs creating non-linear history would be:
- not publish, that's the important part.
- generate the final merge in the target topic
It's less clear in linear cases:
- with the default merge method, we should be able to generate an empty merge changeset, but that's to be checked
- what should it mean with the 'fast-forward' method? Nothing? Adoption of the source changesets in the target topic?
The risk of unwanted publication has been on my mind for a while, but I don't think it's been reported before.
It's too late for %Heptapod 0.13.0 to offer full support for these (especially in the linear case), but I'd want to include at least a basic protection, so that users don't get bad surprises.