Stacked pull requests break large changes into small, reviewable pull requests. They’re an ordered series of pull requests that each represent focused layers of your change. With stacks, you can…
I’ve recently picked up jujutsu, and it plus gitlab’s stacked PR have made splitting up MRs a breeze. Typo in a commit at the top of the chain? “jj edit revision”, fix the typo, then “jj git push”.
Ah yeah looks like the latest 19.1 release from June.
But it also seems to suggest it’s only a UI change. Is is possible to do stacked MRs across forks? Does it not still suffer from the flaw GitHub has (or had, hopefully) - you create one MR, myfork:feature_0 -> upstream:master. That’s fine, but then you want to create the second MR targeting the first MR, myfork:feature_1 -> ???:feature_0, only you can’t. feature_0 doesn’t exist in the upstream and there’s no point creating an MR targeting your own fork.
I’ve recently picked up jujutsu, and it plus gitlab’s stacked PR have made splitting up MRs a breeze. Typo in a commit at the top of the chain? “jj edit revision”, fix the typo, then “jj git push”.
Do you mean GitHub? Last I checked Gitlab doesn’t support stacked PRs.
No I meant gitlab. I have been using them for a week or two now, I guess it’s a recent addition
Ah yeah looks like the latest 19.1 release from June.
But it also seems to suggest it’s only a UI change. Is is possible to do stacked MRs across forks? Does it not still suffer from the flaw GitHub has (or had, hopefully) - you create one MR,
myfork:feature_0 -> upstream:master. That’s fine, but then you want to create the second MR targeting the first MR,myfork:feature_1 -> ???:feature_0, only you can’t.feature_0doesn’t exist in the upstream and there’s no point creating an MR targeting your own fork.