A GitHub-style code review shows a side-by-side diff, with the whitespace visibility menu open and new code highlighted in green.
GitHub has fixed a long-running annoyance in code review. You can now tell pull request diffs how to treat whitespace once, instead of re-toggling it on every review. A second change gives new and deleted files the full width in split view. Both changes landed on October 22, 2026, in the "Files changed" page.

A GitHub-style code review shows a side-by-side diff, with the whitespace visibility menu open and new code highlighted in green. What GitHub changed​

GitHub's changelog lists two improvements to the "Files changed" page:

  • A saved whitespace preference. The older behavior remembered "hide whitespace" only on the pull requests where you had enabled it. The new setting is personal and applies across pull requests.
  • Full-width new and deleted files in split view. These files now span both columns, as they already did in unified view.

The changelog is a one-minute read, and GitHub labels it an "Improvement" rather than a major release.

How to set the whitespace preference​

GitHub's changelog describes the steps this way:

  1. Open a pull request and go to Files changed.
  2. Open Settings → Whitespace changes.
  3. Choose one of three options: Always show, Always hide, or Hide for this diff only.

The first two are saved defaults. "Hide for this diff only" is the one-off option.

When whitespace is hidden, an active Hide whitespace filter appears beside All commits. Click its X to show whitespace temporarily. That does not change your saved preference.

GitHub also says file counts and diff statistics reflect the diff you are looking at. Hiding whitespace can therefore change the numbers you see. If a pull request looks smaller than expected, check whether the filter is on.

GitHub's announcement doesn't say whether the setting syncs across devices, browsers, or accounts. It also gives no rollout schedule or plan restrictions. Treat those as unknown until GitHub says more.

Why this matters: a five-year request​

This has been a persistent community request. A GitHub staff member said in 2021 that GitHub had considered a user-level setting but chose to remember the choice per pull request first. That per-PR change shipped in October 2021. The staff member said GitHub might reassess the user-level option later.

Users kept asking. One 2023 community thread asked for the whitespace preference to persist across PRs, as the unified/split preference already does. As recently as July 2026, a commenter in that thread was still complaining the feature was missing. The October 22 change is the answer to that request.

GitHub's review documentation currently says the opposite. It says the whitespace choice only applies to this pull request and is remembered the next time you visit that page. The docs predate the change, so the changelog is the authority for the new behavior.

The case for each setting​

There is a trade-off here, and it isn't only about convenience.

Always hide suits teams that reformat code often. Indentation-only churn can bury the real change. Hiding it makes a refactor much easier to read.

Always show is safer when whitespace is meaningful. YAML, Python, Makefiles, and some shell heredocs can break on a whitespace change. One community commenter made a related point: choosing to hide whitespace is a deliberate act, and a hidden change can still break something. A permanent "hide" default removes that moment of deliberate choice. (This is a general code-review caution, not something GitHub's announcement states.)

Hide for this diff only is the cautious middle path. It lets you suppress noise on a big reformatting PR without changing your default for other reviews.

If you choose Always hide, one habit helps. Glance at the Hide whitespace filter chip on every PR, and click its X when the file type makes whitespace meaningful.

Split view for new and deleted files​

In split view, a brand-new file has nothing to compare against on the left. The old layout used only half the width for the right-hand side, which made wrapping worse. Deleted files had the mirror-image problem.

Now both file types span both columns, matching unified view. GitHub says this gives more room and reduces line wrapping. The changelog doesn't claim any change to modified files, to diff calculation, or to the underlying content.

The release is a layout refinement, not a new diff engine. This is the style of work GitHub has been doing on the page all year. The January 2026 rollout made the improved "Files changed" experience the default. That rollout added a resizable file tree, locally saved draft comments, and an experimental virtualized mode for large pull requests.

GitHub hasn't said whether the October changes apply in that experimental large-PR mode. Don't assume they do.

Quick summary​

ItemWhat changed
Whitespace settingNew personal preference: Always show, Always hide, or Hide for this diff only
Temporary overrideClick the X on the Hide whitespace filter; the saved preference is untouched
Counts and statsReflect the displayed diff, so they can shift when whitespace is hidden
Split viewNew and deleted files now span both columns
Not statedDevice sync, rollout timing, plan limits, large-PR mode behavior

Bottom line​

This is a small change with a real payoff. It spares reviewers a repetitive click and gives the whitespace setting the same persistence as the split/unified choice. Before relying on a saved "always hide" default, decide how much you trust whitespace-insensitive reviews in your repositories. GitHub invites questions and feedback in its Community discussion.

 

References

  1. Pull requests: Saved whitespace preferences and improved split view GitHub Changelog 2026-10-22T17:24:56+00:00
  2. Reviewing proposed changes in a pull request - GitHub Docs docs.github.com
  3. Reviewing proposed changes in a pull request - GitHub Docs docs.github.com