Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even if you have linear history on main (squash commits from PRs). You still have this problem if you have multiple out-standing PRs and one of them is dependent on another.


In Gerrit, the review unit is commonly one commit. IMO the Github pattern of bundling several changes in one review is a mistake.


Even the email based flow presents a series of changes as a thread of email messages, so the association between changes that are related or depend on each other is maintained.

Once a patch set looks good to the maintainer, it's merged. Email clients do enforce looking at the changes as a series of diffs on a per commit basis.


There are 2 possibilities: 1) Gerrit doesn't support stacked PRs 2) You have this rebase problem.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: