Steps to reproduce:
- Create MRs for a stack of two patches
- Amend the second patch, and push that
- While the CI for the now-updated second patch is running, merge the first patch
- Now the second patch gets stuck with a message saying "You should run a new pipeline, because the target branch has changed for this merge request."
Could Gerritlab automatically trigger the new pipeline for the second patch when merging the first patch?