4 ms·

I guess what I'm saying is: for very large complex features, I don't want one big commit. I want to review a series of commits and then I want to have that seri

I guess what I'm saying is: for very large complex features, I don't want one big commit. I want to review a series of commits and then I want to have that series of commits persist in the history. This is how Gerrit operates "natively" - the commit message and everything is part of the artifact under review exactly like the diff. If the model is to squash an MR into a single commit before merging it, I'd then want to be able to have MRs that depend on each other.

seabrookmx 8mo ago
You can "chain" them and there's some native support for this in Gitlab, but I can't say I've ever tried using it. If I really need a feature branch, I just create a separate branch and target my MR's to that until the whole thing is ready to land in main. Again, it seems less natural to me than how Gerrit does it.