When doing code reviews, I go through pull request commits in chronological order. It sometimes takes more time (eg. if the author didn't know exactly how to approach the problem from the start), but gives a much clearer picture of what was going on inside their mind when they wrote it.
That's one of the main reasons I dislike pull req squashing (or doing large compound "clean" commits in the first place). It destroys this information.
Comments
When doing code reviews, I go through pull request commits in chronological order. It sometimes takes more time (eg. if the author didn't know exactly how to approach the problem from the start), but gives a much clearer picture of what was going on inside their mind when they wrote it.
That's one of the main reasons I dislike pull req squashing (or doing large compound "clean" commits in the first place). It destroys this information.