MRs based on another MR don't update their commits once base MR is merged
Summary
If MR2 is based on MR1 and MR1 gets merged, MR2 still shows MR1's commits as being part of the MR.
What is the expected correct behavior?
I expect the newly published commits to disappear from MR2. I would argue that there should be a difference in visibility between commits from MR1 and MR2 from MR2's page, but that may be another issue.
Maybe this is a Gitlab issue and will be fixed by the current Gitlab 12.2 rebase?