On: Launch HN: Axolo (YC W21) – Faster pull requests a...

[cosydney]

We've also encountered that problem in some cases. Stacked PR are difficult to manage. We could potentially have multiple PR into a single channel to make communication easier abroad stacked PR.

To this date we don't have access to the code and it's easier for companies to try us this way. So not sure we will go too much into details on this topic.

Stacked PR shouldn't exist, or at least rarely. We plan to introduce analytics and we think that too many stacked PR should be a warning that something is not right.

[Game_Ender → cosydney]

Can you explain why you don’t think stacked PRs should exist? What repo sizes, team sizes, and CI practices does your recommendation apply to?

I have seen them used in a few ways:

- To enable the creation of PRs that change just one thing. This makes them easier to review, revert or cherry pick.

- Allow you to continue to work while a more intensive CI or review process is under way.

With a good stacked change system, like in Phabricator or Gerrit, I have seen some of the most productive ever devs always using stacked changes.