News for hackers. Stuff that matters.

A comment on Two Years of Squash Merge (2019). Parent comment

Re:Two Years of Squash Merge (2019) by garmaine on Friday April 30, 2021 @06:47PM (#27000493)
> On the other hand, if you kept the history, and if this history was clean from the get go, it becomes easy to read the commits one-by-one and understand the issue.

Or git-bisect.

[ Parent | on HN ]
Re:Two Years of Squash Merge (2019) by gouggoug on Friday April 30, 2021 @07:45PM (#27001114)
Yes, git bisect.

But what does git bisect require to be useful?

A set of small atomic commits that make it easy to identify which line of code might be the origin of a very subtle bug you're looking for. Squash+merge will not provide you with such history, and make bisecting much less useful.

[ Parent | on HN ]