How to visualize a GitHub repository’s commit history
See a GitHub repo’s commit history as a graph and find which files change together. Free, no sign-in, works on any public repository.
Why a list of commits isn’t enough
GitHub shows commits as a flat, paginated list. That is fine for finding one change, but it hides the shape of the work: where history branches and merges, which parts of the code move together, and where activity is concentrated.
A commit graph lays the same history out as nodes and edges, so merges, parallel lines of work and bursts of activity are visible at a glance.
Draw the commit graph with RepoLens
Paste the repository URL (for example github.com/vercel/next.js) on the RepoLens home page and open the Commit graph tab. RepoLens fetches recent history from the GitHub REST API and draws each commit with its parent links, so merge commits show up where branches join.
For speed and to stay inside GitHub’s rate limits, the analysis covers the most recent 500 commits on the default branch. That is usually months of history for an active project and the whole history for a smaller one.
Find files that change together
Next to the graph, the file change heatmap shows which files are touched in the same commits. Files that always change together are coupled, even when nothing in the code imports one from the other: a component and its styles, an API route and its client, a config file and the code that reads it.
Use it before a refactor to see what else will probably need to change, or when reviewing a pull request to spot a file that usually changes alongside the ones in the diff but is missing.
Watch the history over time
The Evolution timeline tab adds a date-range slider. Drag it to filter commits and files to a period and see how the repository grew: when directories appeared, which areas were busy in a given release, and when work moved from one part of the code to another.