GITKRAKEN Commit Graph

Commit history made visual & Interactive

Visualize your repo history like never before. The Commit Graph turns your repo’s past into a clear, interactive map. Every branch, merge, and commit laid out to explore. See who did what, when, and act on it instantly.

Bring color & clarity to your commit history

Explore what Commit Graph lets you do

GitLens Commit Graph interface for the vscode-gitlens repository. Multiple branches are color-coded, including fix-e2e, debt/improvement, chore/string-interpolate, and release/17.4. The graph visually displays commits as nodes, with connecting lines indicating their relationships and merges. On the right, detailed commit info is shown, including messages like “Adds gates and deeplink command support,” number of file changes, authors, timestamps (e.g., “2 weeks ago”), and commit SHAs. The top panel includes filters for branch selection, history navigation, and author search.

Interactive commit history

Digging through past commits in the CLI is slow work. The commit graph makes it instant. Open any repo in GitKraken Desktop or GitLens for IDEs, and you’ll see your project’s history mapped out. Branches, merges, and commit relationships all brought to life in rich color. Scroll to explore, zoom to focus. It’s Git made visual.

Rich search & filtering 

Track down exactly what you need. Search by message, author, file, code changes, or even with natural language using AI. Filter by author or team, show or hide tags, branches, or stashes, and dim the noise of merge commits to keep your focus sharp.
GitLens Commit Graph showing the search filter dropdown in use. The dropdown menu under the search bar titled “SEARCH BY” displays options to filter commits by: • My changes (@me) • Message (message: or =) • Author (author: or @:) • Commit SHA (commit: or #:) • Type (type: or is: e.g., stash) • File (file: or ?) • Change (change: or ~:) • After Date (after: or since:) • Before Date (before: or until:) In the background, a vertical timeline of blue commit nodes is visible, with one commit row highlighted and showing 1 file changed. The interface includes buttons for Push, Fetch, and other commit graph controls.
GitKraken Desktop Commit Graph showing a context menu for a selected commit (ea94fa0) on the fix-e2e-tests branch. The graph displays multiple vertical commit lines representing branches such as fix-e2e-tests, debt/impro..., chore/string-in..., release/17.4, and debt/compose..., each with colored paths and user avatars on commits. The context menu offers various Git actions, including: • Merge origin/fix-e2e-tests into aifeatures • Rebase or Interactive Rebase aifeatures onto origin/fix-e2e-tests • Checkout, Create worktree from, Create branch here • Cherry pick commit, Reset or Revert the commit • GitHub-related options like Review code & suggest changes, View pull request, and Copy pull request link • Push the branch and start a pull request • Delete origin/fix-e2e-tests • Copy actions: branch name, commit SHA, links to branch or commit • Share as a Cloud Patch, open in Solo view, and options to Create tag The UI includes a graph panel, commit details, and toolbar above with repository, branch selection, push/fetch status, and search functionality.

Reveal actions in 1-click

Right-click any commit, branch, or tag in the graph and the options are right there: compare against a base, open diffs, revert, rebase, checkout, and more. No memorizing commands, no second-guessing. Want to rebase this branch? Roll back that commit? Just right-click and GitKraken tells you exactly what you can do.

Gauge the size of changes

Some commits are tiny tweaks, others reshape the codebase. The Commit Graph makes the difference obvious, surfacing change sizes at a glance so you can spot the big shifts and zero in faster.
GitLens Commit Graph interface zoomed into the “CHANGES” column, helping users gauge the size of changes per commit. Each row shows: • The number of files changed. • A visual gauge using horizontal bars to represent lines added (green) and removed (red). • Commits vary from small single-line updates to large, multi-file modifications. This visual breakdown allows users to quickly assess the impact of each commit at a glance.