Merge Commits are Back (and Better than Ever)
After a long hiatus, we’re linking to merge commits again. We truncated merge commits months ago, because they didn’t provide any information beyond the shas of the parents, but now…
After a long hiatus, we’re linking to merge commits again. We truncated merge commits months ago, because they didn’t provide any information beyond the shas of the parents, but now we’re exposing the diff between them as an overview of what changed in the branch.
Essentially, what we’re doing behind the scenes is: git diff parent1…parent2
This page will become the basis for a more extensive code review system that, coupled with our current code commenting, will really provide a lot of value for large projects.
(If older merge commits aren’t showing diffs, it’s most likely that it got cached without the additional data)
Written by
Related posts
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.