Hacker News new | ask | show | jobs
by mytailorisrich 1774 days ago
> With normal review cycle times, this would slow things very much.

I don't think it does. Ultimately you need to review everything so if you ensure that each commit is logically coherent it actually makes reviews easier.

Otherwise, in my experience, things can get quite messy and the history very difficult to follow.

It's also impossible to predict when or if you'll need to revert a commit. If you follow good practices and have discipline then you make your life much easier if things go wrong or you need to cherry-pick something, which is quite common with bug fixes if you have several branches (e.g. one branch per release).

1 comments

For whatever reason, the events you say are quite common, pretty much never happens on my teams.

So we don't need to optimize for handling them.