Why it matters
Rich diffs gives ForkMesh a concrete mechanism for review diffs that understand syntax, images, and binary changes. Syntax-aware diffs with side-by-side image comparison and clear badges for binary changes, in the app and on the web.
Review becomes risky when merge state, discussion, and final application are trapped in a central service. In ForkMesh, rich diffs addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles rich diffs through the same split it uses across the product: ForkMesh derives diffs from live branches or signed patches, checks mergeability against the live base, and records review activity as portable data.
The behavior is intentionally narrow: Syntax-aware diffs with side-by-side image comparison and clear badges for binary changes, in the app and on the web. Maintainers can verify what changed, who proposed it, and whether it will merge before touching the base branch.
Where it fits
Use rich diffs when contributors need familiar review mechanics without making one hosted PR database the source of truth.
It pairs with the rest of Pull requests & review because Rich diffs keeps review diffs that understand syntax, images, and binary changes connected to the repository, its signatures, and the nodes that serve it.