Comment by jon-wood

I can't help but see the irony of complaining that people don't read git commit messages or technical documentation in the comments for a product to assist in code review.

You know what really, really, helps while doing code review? Good commit messages, and more generally, good commit practices so that each commit is describing a set of changes which make sense together. If you have that then code review becomes much easier, you just step through each commit in turn and you can see how the code got to be where it is now, rather than Github's default "here's everything, good luck" view.

The other thing that helps? Technical documentation that describes why things are as they are, and what we're trying to achieve with a piece of work.