Fewer repeated adjustments
On October 22, GitHub announced two improvements to reviewing proposed changes: saved whitespace preferences and full-width display for new or deleted files in split view.
Think of editing a document where someone changed the text and adjusted the margins. Separating those changes can make reading easier. In code, though, presentation is not always an unimportant detail.
A personal preference
Under Settings → Whitespace changes, you can choose to always show changes, always hide them or hide them only for the current comparison. The saved preference is personal; it does not force everyone on the team to use the same view.
Our recommendation is to use the filter to get your bearings, not as a guarantee that hidden changes are harmless. If a change raises questions, show it again and ask why it was made before approving it.
Context still matters
GitHub’s documentation recommends reviewing one file at a time, leaving specific comments and marking reviewed files to track progress. It also suggests understanding the request’s purpose before examining the details.
That is a useful way to divide your attention: first the problem being solved, then the changes made and finally what still needs checking. A clearer screen helps, but the decision still depends on what you review.
Sources and context
Sources used for this article. Follow the links to read the original material.
See the linked sources for more information. Corrections and contact →
