Better validation of Merge Requests
Problem to solve
When creating a merge request (for example from a feature branch to master), current behavior is to run a pipeline against the source branch only.
Further details
It would be nice to create a temporary branch based on the target branch and merge automatically with source branch to run a pipeline against this temporary branch.
This way, we can make sure that possible changes made on the target branch that not necessarily generates a conflict gets tested by the pipeline before a merge. It will minimize the chance of not testing something that reached the target branch before the source branch.
If any changes are made on both source or target branch, this temporary branch should be recreated and another pipeline should be triggered.
Proposal
What does success look like, and how can we measure that?
Changes from both target and source branches are included in a pipeline run.