GitLens Commit Graph

Last updated: November 2026

Commit Graph

The Commit Graph is the starting point for working in GitLens. It brings repository history, branches, worktrees, Working Changes, pull requests, and supported agent activity into one connected workbench, so you can understand what’s happening and move changes toward merge without rebuilding context across tools.

Built on a high-performance rendering engine, the graph stays responsive on large repositories, showing commits, branches, and collaborators in one place.

The Commit Graph is included in GitLens Community and available to everyone on public and local repositories — no account required. A GitLens Pro subscription or trial is required only for private repositories.

---

Open the Commit Graph

The Commit Graph is the leading view in the GitLens sidebar. Click the GitLens icon in the Activity Bar to open it directly.

You can also open it from the Command Palette:

1. Open the Command Palette:
   • macOS: Cmd + Shift + P
   • Windows/Linux: Ctrl + Shift + P
2. Type Show Commit Graph and select it.

The Commit Graph opens in a new tab, where you can scroll through history and resize column widths.

If no repository is open, the Commit Graph shows No repository open with two groups of ways to get going:

• Get started: Open a Folder, Clone a Repository, or Start a New Project. In VS Code for the Web, this group offers Open a Remote Repository instead.
• Start from your work: Start Work on an Issue picks an issue from your connected integrations and creates a branch for it, and Start Review on a PR checks out a pull request for review. This group isn’t available in VS Code for the Web.

With no repository open, Start Work lists issues from all of your connected integrations. If GitLens can’t find the repository of the issue you pick, it asks how to find it: select Clone Repository… or Choose a Local Folder…, then continue to create the branch. Start Review offers the same two options when it can’t find a local copy of the pull request’s repository.

---

Repository Information

At the top of the Commit Graph, you’ll see:

• Repository — the hosting provider’s icon (hover it for the repository name; the editor tab is titled Commit Graph: <repository>)
• Checked-out branch (click to switch branches)
• Last fetched time — shown beside Fetch and in its hover (click Fetch to update). A repository with no remotes has nothing to fetch, so Fetch isn’t shown; instead the header offers Publish Repository (see Next steps)
• Account — the account button opens a popover with your plan and the Synchronize Status, Manage Account, Sign Out, and Send Feedback actions, plus rows for your connected integrations, your AI model and GitKraken AI usage, and your agents

You can enable automatic fetching with the gitlens.graph.autoFetch.enabled setting. When enabled, GitLens periodically runs git fetch for repositories visible in the Commit Graph, keeping your view up to date without manual refreshes.

---

Availability

• The Commit Graph is included in GitLens Community and available to all users on public and local repositories, with no account required.
• A GitLens Pro subscription or trial is required only for use with private repositories.
• If you aren’t signed in, the first time you open the Commit Graph on a privately hosted repository a 3-day preview starts automatically. While it runs, a banner above the graph shows how much time is left (for example, Previewing the Commit Graph on privately hosted repos — 3 days left.) with a Sign In link. The 3 days run continuously from the first open.
• When the preview ends, the Commit Graph shows Commit Graph Preview Ended for privately hosted repositories. Sign in or start a free Pro trial to keep using it there. If your workspace also has public or local repositories, select Switch Repos to keep working in one of them.
• The preview applies only while you’re signed out. If you’re signed in without a Pro trial or paid plan, private repositories show the upgrade prompt instead.

---

Feedback

You can send feedback to the GitKraken team without leaving the Commit Graph. Select the Send Feedback… (feedback) icon in the title bar of the Commit Graph editor tab or view, or select Send Feedback in the account popover. In the Send Feedback dialog, choose General, Bug, or Feature, enter your message, and select Send Feedback.

When you send a bug report, GitLens also opens a GitHub issue prefilled with your message so you can add more details. After you send a feature request, you can select File on GitHub to file it as a GitHub issue as well.

You can also share ideas in the GitLens Commit Graph discussion on GitHub.

---

Graph Sidebar

The Commit Graph includes an expandable sidebar panel that provides quick access to your repository refs. The sidebar lists branches, remotes, stashes, tags, and worktrees in both list and tree views. Click the sidebar toggle to expand or collapse it, or use the gitlens.graph.sidebar.pinned setting to keep it pinned open.

The sidebar contains several panels, including:

• Overview: Displays branch cards with Working Changes stats and upstream tracking information at a glance.
• Agents: Lists agent sessions so you can monitor and manage them. Branches with running agent sessions display status pills directly in the graph, so you can track agent activity at a glance. Select Show Agent Kanban in the sidebar to see sessions as a Kanban board.
• Worktrees: Lists your worktrees. Hover a worktree and select Scope to Worktree to work in it from the graph (see Scope to a Worktree).
• Pull Requests: Lists the repository’s pull requests. If the repository has no remotes yet, the panel explains that publishing comes first and offers a Publish Repository… button, which opens the same Publish step as Publish Repository in Next steps.

Select Show Past Sessions in the Agents panel to include sessions that have ended. You can resume a past Claude Code, Codex, OpenCode, or GitHub Copilot CLI session with Resume in Terminal, or with Resume in <agent> Extension when the agent’s VS Code extension can open it. Select Archive Session to remove a past session from the list. The gitlens.agents.resumeTarget setting controls where a session resumes when both are possible: GitLens asks the first time by default, terminal always resumes in a new integrated terminal, and extension uses the agent’s extension when it can.

Detail Sheets

Clicking on a branch, pull request, comparison, or agent session opens a slide-out detail sheet with rich information:

• Branch sheet: Shows branch details, tracking status, and recent commits.
• Pull request sheet: Displays PR description, reviewers, status checks, and stacked PR information when applicable.
• Compare sheet: Shows file-level comparison between branches or commits, with a pinned mode to keep the comparison visible while navigating.
• Rebase summary sheet: Appears after a rebase operation, summarizing what changed.
• WIP conflict sheet: Surfaces during conflict resolution to help resolve working changes.
• Agent session sheet: Opens when you click an agent session card or row. Shows the session’s status, the files the agent read or edited, its first and last prompts, and other worktrees it also worked in. Use the previous and next buttons to move between sessions, and select Resume or Archive for a session that has ended.

Visualizations and Repository Health

Select Show Visualizations & Health in the sidebar to replace the graph with a visualization of your repository: Visual History, Files Treemap, Commits Treemap, Agent Activity Treemap, or Repository Health. You can also run GitLens: Show Repository Health from the Command Palette to open the Commit Graph on the Repository Health view.

Repository Health checks whether Git can run faster in the current repository. It suggests optimizations (Untracked cache, File system monitor, Large-repository index, Sparse index, and Scheduled maintenance) that you can enable, disable, or undo one at a time, and it offers Run Maintenance Now. When GitLens notices slow Git operations or a very large repository, a banner links to Show Repository Health. Nothing changes until you apply an optimization.

While VS Code is open, GitLens also runs safe, repository-local Git maintenance in the background: loose-object packing, incremental repack, and the commit-graph cache. It never applies the optimizations listed above automatically. To turn off the background maintenance, disable the gitlens.gitOptimizations.enabled setting; Repository Health requires this setting.

---

Worktree Overview

See branch state, uncommitted changes, and unpushed commits across your worktrees. Each worktree has a pill above the graph; select it to jump to that worktree’s Working Changes row.

Each pill shows the branch name, a dirty indicator when there are uncommitted changes, and an unpushed arrow when commits have not been pushed. Hover a pill to see its ahead and behind counts and changed files. The gitlens.graph.overviewBar.visibility setting controls when the overview bar is shown: always, worktrees (when the repository has more than one worktree), dirtyWorktrees (the default, when another worktree has working changes or unpushed commits), or never.

Working Changes Rows

Each worktree’s uncommitted work appears on a Working Changes row, which shows the worktree’s branch as an inline pill. Working Changes rows of other worktrees carry a worktree row marker; hover it to see the worktree’s name. When a rebase, merge, cherry-pick, or revert is paused in a worktree, its row shows a status pill such as Rebase Paused or Resolve conflicts to continue rebasing.

To run a VS Code task in a worktree, select the Run Default Task (play) button on its Working Changes row. The first time, GitLens asks you to choose the default task. Alt-click the button to choose a different task to run. While the task runs, the button reads Running: <task>, and clicking it shows the running task.

You can also right-click a worktree’s Working Changes row and select Run Task on Worktree… to pick any task. The picker lists recent and workspace tasks first, with All Tasks… for the rest. Select a task’s checkmark to set it as the default task, or select it again to unset it.

Scope to a Worktree

Scope the graph to another worktree to work in it without leaving the Commit Graph. While the graph is scoped, it acts as if you had opened that worktree: you see its branch and its changes, and anything you commit, push, or pull happens there. To scope the graph, do one of the following:

• In the sidebar Worktrees panel, hover a worktree and select Scope to Worktree. Alt-click the action to focus on the worktree’s branch instead.
• Right-click a worktree’s Working Changes row and select Scope to Worktree.
• Double-click another worktree’s Working Changes row or its pill in the overview bar.

GitLens marks the scope in yellow on the header’s branch pill, which names the worktree’s branch, and on the worktree’s row in the sidebar. To return to your active worktree, select Unscope Worktree on the branch pill or on the worktree’s sidebar row.

Two settings control scoping. You can open them from Worktree Scope Settings… in the filter dropdown (see Filter Options):

• gitlens.graph.scopeBehavior: scopeAndFocus (default) also focuses the worktree’s branch, narrowing the visible rows. scope keeps every commit visible.
• gitlens.graph.doubleClickWorktreeAction: scope (default) scopes the graph when you double-click a worktree’s Working Changes row, overview bar pill, or sidebar row. focus toggles the branch focus instead.

Follow the Active Terminal

When the Commit Graph is visible, it follows your active terminal. Switching to a terminal, or to a Claude Code conversation tab, selects the Working Changes row of the repository or worktree that the terminal is in. If an agent session runs in the terminal, the graph follows the session’s worktree. The graph doesn’t open itself to follow a terminal.

• To turn following off, select Stop Following Active Terminal in the More Actions… (⋯) menu of the Commit Graph editor tab or view. Select Follow Active Terminal to turn it back on. Both commands change the gitlens.graph.followTerminal.enabled setting, which is on by default.
• By default, the graph ignores terminals in other repositories. Enable gitlens.graph.followTerminal.allowRepositorySwitching to let the graph switch to another repository.

Ref Find

The ref-finder widget provides a typeahead search for quickly jumping to any branch, tag, or Working Changes row in the graph. The gitlens.graph.refFindAutoHide setting controls whether the widget auto-hides after selecting a result.

---

Details Panel

The Commit Graph includes an embedded details panel that shows information about the selected commit or your current working changes. The details panel replaces the former standalone Graph Details view and is integrated directly within the graph.

When you select a commit, the details panel displays the commit message, author, changed files, and diff. When viewing working changes, it shows your uncommitted modifications. The panel can be positioned to the right or bottom of the graph using the gitlens.graph.details.location setting. An auto option is also available, which switches between right and bottom placement based on the graph width. The gitlens.graph.details.maximizeOnMode setting automatically maximizes the details panel when entering compose, review, or resolve modes.

The details panel supports multiple modes:

• Compare mode: Opens comparisons directly within the graph, showing Ahead, Behind, and All views between branches or commits. This replaces navigating to the standalone Search and Compare view for graph comparisons.
• Compose mode: Provides an integrated commit composition experience, letting you craft commit messages and select files to commit without leaving the graph. You can also access Compose from the graph context menu.
• Recompose: Helps clean up existing branch history by reorganizing selected commits into a clearer, more intentional sequence. GitKraken AI can propose the new structure and commit messages for you to review and refine before applying the result. Available from the graph context menu, Recompose can operate on an entire branch, from a specific commit, or on selected commits.
• Review mode: Helps you inspect commits or Working Changes before they move forward. GitKraken AI can surface potential bugs, security issues, and other areas that deserve attention — tagged by severity — while you decide what needs to change. You can configure separate AI models for compose and review using per-feature model scoping, and customize review behavior with the gitlens.ai.reviewChanges.customInstructions setting.

Next Steps

When you select a Working Changes row that has no uncommitted changes, the details panel suggests Next steps for the branch. Depending on the branch, the list offers actions such as publishing the branch, pulling or pushing commits, creating or viewing its pull request, and reviewing or recomposing its changes. If the branch has diverged from its upstream, the list starts with a Diverged from <remote> — N behind, M ahead step. Select Pull to bring in the remote commits, or select Force Push beside it to overwrite the remote branch with your local commits.

If the repository has no remotes yet, the list instead offers Create a remote repository and publish <branch> to it with a Publish Repository button, and Add a remote, then publish <branch> to it with an Add Remote button. Both open the Git Command Palette’s Publish step with your choice already selected (see Git Command Palette). Publish Repository… creates the repository on a hosting provider, adds it as a remote, and pushes the current branch. Add Remote… adds a remote you enter, which suits a host VS Code can’t publish to, and then continues to Confirm Publish for the branch. In a repository with no remotes, Publish Repository also replaces Publish Branch in the Commit Graph header and in a branch’s context menu, and Fetch is hidden. In a branch’s details, Publish Repository appears only for the current branch, and in the Working Changes header only for the current worktree.

Multi-file Selection

File lists in the details panel (Working Changes, commit details, compare, compose, and review panels) support multi-file selection using Shift-click and Ctrl/Cmd-click. With multiple files selected, you can perform batch operations including stage, unstage, discard changes, and stash. Individual files also show inline action buttons for quick single-file operations.

To ignore an untracked file, right-click it in the Working Changes file list and select Add to .gitignore. With several files selected, the action applies to the untracked ones. GitLens adds each file as a pattern anchored to the repository root, such as /local-config.json, to the .gitignore file at the root of the repository. GitLens creates the file if it doesn’t exist and opens it so you can see what was added.

Co-authors

When composing a commit in the graph, use the Add Co-authors button to append Co-authored-by trailers to your commit message.

Navigation and Keyboard Shortcuts

The details panel includes back and forward navigation buttons for browsing through previously viewed commits.

Press ? in the Commit Graph to open the Keyboard Shortcuts sheet, which lists all graph shortcuts organized by category. Frequently used shortcuts include:

• /: Find a branch, tag, or worktree.
• Ctrl/Cmd + F: Search commits.
• 1 through 0: Jump to a recent worktree.
• Alt + 1 through Alt + 8: Toggle a sidebar panel.
• Alt + K, V, M, S, or D: Toggle the Agent Kanban, visualizations, minimap, sidebar, or details panel.
• Ctrl/Cmd + Up/Down: Follow the branch to the previous or next commit.
• Alt + Up/Down: Jump to the previous or next fork point.
• Ctrl/Cmd + Left/Right: Switch branch at a fork.

Hold Ctrl or Alt while you hover a commit to highlight its lane and the commits in its chain, dimming the rest of the graph.

To change or turn off shortcuts, select Customize… in the Keyboard Shortcuts sheet to open the gitlens.graph.shortcuts settings. Hover a shortcut in the sheet to see its id. In gitlens.graph.shortcuts.overrides, set an id to a different key combination, or to false to turn it off. To turn off all customizable shortcuts, disable gitlens.graph.shortcuts.enabled. Navigation keys such as the arrow keys, Enter, and Esc always work.

---

Configuration and Layout

You can configure the Commit Graph to control what information is shown and how it is displayed.

Graph Style

The gitlens.graph.style setting controls the overall row layout of the graph. Options include table (columnar layout with visible borders), list (compact list layout), and auto (switches based on available width).

Columns

• Drag and drop column headers to rearrange columns.
• Right-click a column header to toggle columns on or off.
• The Changes column visualizes added and deleted lines per commit. The gitlens.graph.changesColumn.mode setting controls the display style: numbers (numeric counts), squares (colored blocks), bar (horizontal bar), or bipolar (split additions/deletions bar).
• Column grouping is enabled by default, combining the Graph and Branches/Tags columns into a compact layout. To change it, right-click a column header and select Group Graph Column, Ungroup Graph Column, Group Branches / Tags Column, or Ungroup Branches / Tags Column. Lanes can be folded to collapse inactive branches and reduce visual clutter.
• To reuse a layout, right-click a column header and select Save as Default Layout. GitLens saves your columns and panel layout, and new workspaces open with it. Select Apply Saved Layout to apply the saved layout to the current workspace, or Reset Layout to restore the original layout.

Lane Colors and Row Markers

The graph uses perceptually-uniform lane colors that are tuned for both dark and high-contrast themes. Row markers indicate important commits at a glance:

• Green marker: HEAD commit
• Blue marker: upstream tracking commit
• Worktree marker: Working Changes row of another worktree
• Colored reference pills: merge target and other branch roles

By default, each row shows one branch or tag pill and collapses the rest behind a +N badge. To show more pills on a row, set gitlens.graph.refs.maxInline to a number from 1 to 10, or to auto to fit as many pills as the row allows.

To show pills on their own line above the commit, set gitlens.graph.refs.layout to stacked; rows with pills become taller. The gitlens.graph.refs.maxStacked setting (default auto) limits the pills on that line. The stacked layout applies when the graph style is table and the Branches/Tags column is grouped with the Graph column. You can also change these options in the GitLens settings (GitLens: Open Settings).

Layout Options

• Panel Layout: Displays the Commit Graph in the bottom panel (near the Terminal) with a details view alongside it.
• Editor Layout: Opens the Commit Graph in an editor tab.
• You can open the Commit Graph in both layouts simultaneously.

To switch layouts:

1. Open the More Actions… (⋯) menu in the top-right corner of the Commit Graph editor tab (or of the Commit Graph view in the side bar).
2. Choose Prefer Commit Graph in Editor or Prefer Commit Graph as a View.

The same menu holds Follow Active Terminal and Stop Following Active Terminal, which control whether the graph follows your active terminal (see Follow the Active Terminal).

The gitlens.graph.editorOpeningBehavior setting controls how files open from the graph — either in the active editor group or automatically based on context. You can also open the Commit Graph in a separate VS Code window using the GitLens: Open Commit Graph in New Window command.

You can also open the Commit Graph from a terminal. Right-click a terminal tab in the Terminal panel, or open the More Actions… (⋯) menu of a terminal editor tab, and choose one of these actions for the worktree the terminal is in:

• Open in Commit Graph: Opens the Commit Graph with the worktree’s Working Changes row selected.
• Focus in Commit Graph: Also scopes the graph to the worktree and keeps the details panel closed. A terminal editor tab shows this action as a button in its title bar.
• Open in New Window: Opens the worktree folder in a new VS Code window.

Claude Code conversation tabs offer the same actions in their title bar and tab context menu, for the worktree of the agent session in that tab.

Compact Graph Layout

• Select the gear in the Graph column header and choose Use Compact Graph Column to reduce visual complexity.
• When the Author column is resized to minimum width, it shows avatars instead of text.
• Columns that become too narrow automatically switch to icons to preserve information.

Scroll Markers

Scroll markers highlight key points in the Commit Graph, including:

• Checked-out branches
• Selected rows
• Search results
• Working Changes rows

Use scroll markers to quickly jump to important points such as HEAD or refs. You can toggle this feature in the Commit Graph settings.

The gitlens.graph.showWorktreeWipStats setting displays file add/change/delete statistics on worktree Working Changes rows. The gitlens.graph.minimap.reversed setting reverses the minimap direction.

---

Settings

Adjust Commit Graph settings from the Command Palette:

• macOS: Cmd + Shift + P
• Windows/Linux: Ctrl + Shift + P

Search for GitLens: Open Settings.

---

Rich Commit Search

The Commit Graph supports rich search across your entire repository. You can search by commit, message, author, file, or even specific code changes.

How to Search

1. Type search criteria in the search bar.
2. Use the arrow icons or keyboard shortcuts to navigate results:
   • Next result: F3 (Windows/Linux) or Cmd + G (macOS)
   • Previous result: Shift + F3 (Windows/Linux) or Shift + Cmd + G (macOS)

You can also:

• Jump to the first or last result by holding Shift while clicking the arrow icons.

Search Filters

Use these filters in the search bar:

• commit:
• message:
• -message: excludes commits whose message contains a term (you can’t combine it with message:)
• author:
• committer: filters by the person who committed the change (supports @me)
• file:
• change:
• type:merge shows only merge commits (is:merge also works)
• @me

You can also use natural language search to describe what you are looking for in plain English. GitLens uses AI to convert your query into the appropriate structured search operators; hover the search query to see how GitLens interpreted it. A request such as “only my commits” filters the graph to the matches, and a request such as “take me to” jumps to the first match. If a natural-language search finds nothing, GitLens suggests broader searches with their result counts, such as searching without the date filter or across all branches. If AI isn’t available, select Search as text instead. Time-based operators such as after: and before: are available for filtering commits by date.

Additional options:

• Match all
• Match case
• Use regular expressions

If a regular expression isn’t valid, GitLens matches the pattern literally instead. When that search finds nothing, select Match literally to turn off regular expressions, or Fix with AI to have AI repair the pattern. When there are more results than the graph has loaded, a bar shows how many results are loaded, with Load More Results… to load the rest.

Full Context Menu Support

You can right-click a branch, commit, tag, author, Working Changes row, or column header (Author, Commit Date/Time, or SHA) to access context menu actions.

Helpful context menu actions include:

• Compare with Common Base: Review changes that would occur if the selected branch were merged by comparing its common ancestor (merge base) with the current branch.
• Open All Changes with Common Base: Review all merge changes in the multi-diff editor.
• Squash Commits: Squash selected commits into one without opening the rebase editor.
• Drop Commits: Remove selected commits from history.
• Reword Commit: Change a commit message in place.
• Modify Commit: Amend a commit’s contents.
• Undo Commit: Appears as an inline action on HEAD commit rows, soft-resetting the commit to return changes to the working tree.
• Push to Commit: Appears as an inline cloud-upload icon on unpushed commit rows, pushing all commits up to and including the selected one.
• Fixup Commit…: Selects the Working Changes row and fills in the commit message as fixup! <subject> for the selected commit. The commit button becomes a Commit Fixup split button whose menu offers Commit Fixup & Squash.
• Squash Fixups…: Available on the current branch. After you confirm, squashes each fixup! commit on the branch into its target commit.
• Push Tag…: Pushes the selected tag to a remote.
• Copy Worktree Path: Copies the path of the worktree where the selected branch is checked out.

Right-click a Working Changes row for actions on its worktree:

• Start Agent Session…: Starts a session in the worktree with your default agent, or asks you to choose an agent if you haven’t set one. Select Always use this agent in that list before you choose to make the agent your default. A CLI agent starts in a terminal at the worktree.
• Start Agent Session With…: Asks you to choose the agent before starting the session.
• Run Task on Worktree…: Runs a VS Code task in the worktree (see Working Changes Rows).
• Copy Branch Name: Copies the name of the branch checked out in the worktree.

---

Auto-Rebase PRO

Auto-Rebase carries a rebase forward through the conflicts GitKraken AI can resolve confidently. When conflicts arise, GitLens analyzes each one and resolves it only when its confidence meets the threshold you configure; anything below that threshold pauses the rebase so you can resolve it yourself.

• Run GitLens: Auto-Rebase… from the Command Palette, or choose Auto-Rebase when you rebase from the graph context menu (for example, Rebase Current Branch onto Branch…).
• If a rebase is already paused, run GitLens: Continue with Auto-Rebase or select Continue with Auto-Rebase in the paused-operation bar.
• The gitlens.ai.autoRebase.confidenceThreshold setting (0 to 1) controls how confident the AI must be before automatically applying a resolution.
• Use gitlens.ai.resolveConflicts.customInstructions to provide custom instructions that guide how the AI resolves conflicts.
• When Auto-Rebase pauses, its notification offers Review & Resolve, Resume with AI, and Abort Rebase. The resolve panel in the graph also offers Resume with AI and Abort Rebase.
• If the result is unsatisfactory, select Undo in the completion notification or Undo Rebase in the rebase summary sheet to reset the branch to its pre-rebase state.

During the rebase, a progress animation appears in the graph to indicate the operation is in progress. A rebase summary sheet opens in the sidebar when the operation completes.

---

Pull Request Information

For GitHub and GitLab, the Commit Graph displays a Pull Request icon for any branch with an open pull request. To enable this, connect a rich integration.

If the repository has no remotes yet, the sidebar’s pull request panel explains that publishing it to GitHub, GitLab, Azure DevOps, or Bitbucket lets you see its pull requests there, and offers Publish Repository… in place of connecting an integration.

For GitHub repositories, the graph also recognizes stacked pull requests. When a branch is part of a PR stack, the PR sheet in the sidebar shows the stack ID, the total number of PRs in the stack, and the current PR’s position. Merge operations are stack-aware, distinguishing between merging a single layer and merging the entire stack.

When a stack has fallen behind its base branch or conflicts with it, the PR sheet shows a Rebase Stack… button beside Merge Stack, and the stack’s row in the sidebar’s pull request panel offers Rebase Stack… as an action. The button’s menu holds Auto-Rebase Stack…. GitLens rebases every branch in the stack from the bottom up: the bottom branch onto the base branch, then each branch onto the one below it. Branches whose pull requests are already merged are skipped, and a branch you don’t have locally is created from its remote branch first. Commit or stash your changes before you start.

GitLens asks you to choose how to run the rebase:

• Rebase Stack: Stops at each conflict. Resolve the conflicts and continue the rebase, and GitLens moves on to the next branch. Select Stop Stack Rebase in the notification to end the run.
• Auto-Rebase Stack PRO: Resolves conflicts with AI for every branch, as Auto-Rebase does, and pauses only when it needs your help. Progress appears in the resolve panel with the branch’s position in the stack, for example Branch 2 of 4. When it pauses, select Review & Resolve or Continue with Auto-Rebase.

When the rebase finishes, GitLens switches back to the branch you started on and offers Force Push Stack. Clear any branch you want to hold back, then confirm to force push the rest. If you dismiss the offer, run GitLens: Git Force Push Stacked Pull Requests… from the Command Palette. After an Auto-Rebase Stack run, you can also select Force Push Stack in the rebase summary sheet. You can also start a rebase with GitLens: Git Rebase Stacked Pull Requests… or GitLens: Auto-Rebase Stacked Pull Requests….

---

Hiding Remotes, Branches, or Tags

The Commit Graph shows refs to your remotes, branches, and tags.

• Right-click a branch or tag pill and select Hide Local Branch, Hide Remote Branch, or Hide Tag. To hide whole classes of refs, use the filter dropdown next to the search box (see Filter Options).
• To hide every branch of a remote, including branches added later, right-click one of its remote branches, or the remote in the sidebar Remotes panel, and select Hide Remote.
• To show them again, hover over the Hide option at the top of the Commit Graph and select the desired refs. Hidden refs also stay in the sidebar Branches, Remotes, and Tags panels, dimmed and marked Hidden. Right-click one and select Show Local Branch, Show Remote Branch, Show Tag, or Show Remote.
• If you jump to a hidden ref, the graph tells you that it’s hidden and offers to show it.

Filter Options

Access filters from the dropdown menu to choose:

• All Branches: Displays all branches.
• Current Branch: Displays the current branch and its upstream remote.
• Smart Branches: Displays only the relevant branches — the current branch, its upstream, and its base or target branch.
• Agent Branches: Displays only branches with running agents, or with agents idle for less than 24 hours.
• Favorited Branches: Displays only branches you starred as favorites.
• Focus Branch: Focuses the graph on a single branch you choose, filtering out unrelated history. While a branch is focused, the dropdown reads Focused. If you jump to a ref outside the focus, select Clear Focus to show it.

When one of these options narrows the graph, a bar shows how many branches are loaded, with Load More… to load the rest.

Additional options let you hide or show:

• Remote-only branches
• Stashes
• Tags

You can also dim merge commit rows for clarity.

---

Minimap

The Minimap provides a high-level overview of repository activity. It shows commits, branches, HEAD/upstream, and more, letting you quickly jump to points of interest.

• Select the Toggle Minimap icon in the Commit Graph toolbar to enable or disable it.
• Use the gear at the right end of the minimap to switch between Commits or Lines Changed views.
• Toggle markers on or off from the same menu.
• The gitlens.graph.minimap.defaultVisibility setting controls when the minimap appears: hidden, onSearch (default, shows during search), or always.

Minimap Overview

• Reads left to right: Left = most recent, right = older.
• Highlighted region: Area currently in view.
• Green lines: HEAD.
• Yellow lines: Search results.
• Upper row markers:
  • Blue blocks = remote branches
  • Brown blocks = tags
• Lower row markers:
  • Pink blocks = stashes
  • Blue blocks = local branches