Post

spent some time looking at this last week and was very unimpressed. stacked diffs/patch series don't make nearly as much sense with a new commit + merge workflow as they do with an amend + rebase workflow. jj compat is alao dubious. going to stick with spr

GitHub@github.com

Stacked PRs, now on GitHub. Go forth and stack 🥞

if you were designing a stacked workflow from first principles, you would focus on atomic/bisectable commits as the unit of work, with interdiffs between versions to guide you. Basically what Gerrit, Phab and numerous other tools do. The lack of engagement with prior art continues to be frustrating

Every time I see these threads I’m amazed how many people can’t imagine how a code review system could be better than GitHub. You don’t know what you’re missing out on, I guess.

0 reposts13 likes

I've mostly just given up at this point. You can do it the right way (amend + rebase) on GitHub but so painful to use that way that it doesn't feel worth it. Not to mention that the communication problems that come from the lack of imagination/experience with good review systems.