Cross-Repository Compare View
When we launched Compare View earlier this year, we knew there was a killer feature still missing: the ability to compare branches across repositories. Easy forking and the networks that…
When we launched Compare View earlier this year, we knew there was a
killer feature still missing: the ability to compare branches across
repositories. Easy forking and the networks that emerge as a result is what
makes GitHub great. Limiting the Compare View to a single repository felt all
wrong. So today we’re flipping the switch on some non-trivial architectural
changes that make cross-repository comparisons a reality:

Here’s how it works: it’s now possible to specify a <user>: prefix on the
comparison’s starting or ending point. When given, the <user> part identifies
the owner of a another repository/fork in the same network. In the example
above, we’re comparing branches in the
homebrew network with
mxcl‘s master
branch as the starting point and adamv‘s rvm branch
as the ending point.
To change the starting or ending point, click the ref label buttons and enter
the branch name or commit SHA1 to switch to. For example, we can change the
starting point from mxcl’s master branch to the brew07 branch like this:
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.
