On 2026-08-17 09:15, David Kastrup wrote:
But that is the point. A review works by going through the changes, and a stacked merge request only displays the differential changes. That makes the stacked requests separately reviewable. The branch constituents in terms of commits are the same regardless of what branch the MR is based off , but the reference point for the reviewable changes is a different one. For reviewing single commits, you can just constrain yourself to the commits of interest. For doing a review on the actually relevant changes, the difference is quite helpful.
Although chaotic experiences with GitHub's stacked PRs are fresh in my memory, I'm willing to try using GitLab's stacked MRs; however, there is an issue standing in the way, in my opinion.
We need to run the regression-test difference detector. A merge request should not be labeled Patch::review until someone has recorded the test differences in the comments.
-- Dan
