diff --git a/_images/gl-17-7-recompose-branch-01-v4@2x.png b/_images/gl-17-7-recompose-branch-01-v4@2x.png new file mode 100644 index 0000000..40a9aa5 Binary files /dev/null and b/_images/gl-17-7-recompose-branch-01-v4@2x.png differ diff --git a/_images/gl-17-8-compose-in-wip-01-v4@2x.png b/_images/gl-17-8-compose-in-wip-01-v4@2x.png new file mode 100644 index 0000000..0aec3c6 Binary files /dev/null and b/_images/gl-17-8-compose-in-wip-01-v4@2x.png differ diff --git a/_images/gl-17-8-recompose-selected-commits-01-v5@2x.png b/_images/gl-17-8-recompose-selected-commits-01-v5@2x.png new file mode 100644 index 0000000..7bf46f0 Binary files /dev/null and b/_images/gl-17-8-recompose-selected-commits-01-v5@2x.png differ diff --git a/_images/gl-access-composer-1-17-4-01-v3@2x.png b/_images/gl-access-composer-1-17-4-01-v3@2x.png new file mode 100644 index 0000000..3eb8154 Binary files /dev/null and b/_images/gl-access-composer-1-17-4-01-v3@2x.png differ diff --git a/_images/gl-access-composer-2-17-4-01-v4@2x.png b/_images/gl-access-composer-2-17-4-01-v4@2x.png new file mode 100644 index 0000000..d3a7528 Binary files /dev/null and b/_images/gl-access-composer-2-17-4-01-v4@2x.png differ diff --git a/_images/gl-agent-working-01-v3@2x.png b/_images/gl-agent-working-01-v3@2x.png new file mode 100644 index 0000000..d01e5dc Binary files /dev/null and b/_images/gl-agent-working-01-v3@2x.png differ diff --git a/_images/gl-ai-commit-generate-01-v3@2x.png b/_images/gl-ai-commit-generate-01-v3@2x.png new file mode 100644 index 0000000..3004483 Binary files /dev/null and b/_images/gl-ai-commit-generate-01-v3@2x.png differ diff --git a/_images/gl-ai-generated-commit-message-01-v2.gif b/_images/gl-ai-generated-commit-message-01-v2.gif new file mode 100644 index 0000000..52ab9c8 Binary files /dev/null and b/_images/gl-ai-generated-commit-message-01-v2.gif differ diff --git a/_images/gl-ai-stash-01-v2@2x.png b/_images/gl-ai-stash-01-v2@2x.png new file mode 100644 index 0000000..07c0787 Binary files /dev/null and b/_images/gl-ai-stash-01-v2@2x.png differ diff --git a/_images/gl-autolinks-01-v4@2x.png b/_images/gl-autolinks-01-v4@2x.png new file mode 100644 index 0000000..a1c6abe Binary files /dev/null and b/_images/gl-autolinks-01-v4@2x.png differ diff --git a/_images/gl-branches-view-01-v3@2x.png b/_images/gl-branches-view-01-v3@2x.png new file mode 100644 index 0000000..6258cdb Binary files /dev/null and b/_images/gl-branches-view-01-v3@2x.png differ diff --git a/_images/gl-cloud-integrations-01-v3@2x.png b/_images/gl-cloud-integrations-01-v3@2x.png new file mode 100644 index 0000000..66b4e1b Binary files /dev/null and b/_images/gl-cloud-integrations-01-v3@2x.png differ diff --git a/_images/gl-code-lens-01-v3@2x.png b/_images/gl-code-lens-01-v3@2x.png new file mode 100644 index 0000000..c8d8d8d Binary files /dev/null and b/_images/gl-code-lens-01-v3@2x.png differ diff --git a/_images/gl-column-settings-v2@2x.png b/_images/gl-column-settings-v2@2x.png new file mode 100644 index 0000000..53c69ef Binary files /dev/null and b/_images/gl-column-settings-v2@2x.png differ diff --git a/_images/gl-column-settings.png b/_images/gl-column-settings.png deleted file mode 100644 index c769e62..0000000 Binary files a/_images/gl-column-settings.png and /dev/null differ diff --git a/_images/gl-commit-composer-17-4-01-v6@2x.png b/_images/gl-commit-composer-17-4-01-v6@2x.png new file mode 100644 index 0000000..72d7b34 Binary files /dev/null and b/_images/gl-commit-composer-17-4-01-v6@2x.png differ diff --git a/_images/gl-commit-graph-01-v4@2x.png b/_images/gl-commit-graph-01-v4@2x.png new file mode 100644 index 0000000..92f694e Binary files /dev/null and b/_images/gl-commit-graph-01-v4@2x.png differ diff --git a/_images/gl-commit-graph-compact-graph-01-v3@2x.gif b/_images/gl-commit-graph-compact-graph-01-v3@2x.gif new file mode 100644 index 0000000..903fefd Binary files /dev/null and b/_images/gl-commit-graph-compact-graph-01-v3@2x.gif differ diff --git a/_images/gl-commit-graph-settings-01-v4@2x.png b/_images/gl-commit-graph-settings-01-v4@2x.png new file mode 100644 index 0000000..4a75b0f Binary files /dev/null and b/_images/gl-commit-graph-settings-01-v4@2x.png differ diff --git a/_images/gl-commit-search-moving-arrow-keys-02-v4@2x.gif b/_images/gl-commit-search-moving-arrow-keys-02-v4@2x.gif new file mode 100644 index 0000000..06764c4 Binary files /dev/null and b/_images/gl-commit-search-moving-arrow-keys-02-v4@2x.gif differ diff --git a/_images/gl-commits-view-01-v2@2x.png b/_images/gl-commits-view-01-v2@2x.png new file mode 100644 index 0000000..520e74a Binary files /dev/null and b/_images/gl-commits-view-01-v2@2x.png differ diff --git a/_images/gl-connect-remote-integration-01-v3@2x.png b/_images/gl-connect-remote-integration-01-v3@2x.png new file mode 100644 index 0000000..e6e8484 Binary files /dev/null and b/_images/gl-connect-remote-integration-01-v3@2x.png differ diff --git a/_images/gl-connect-to-remote-ghe-01-v3@2x.png b/_images/gl-connect-to-remote-ghe-01-v3@2x.png new file mode 100644 index 0000000..480536f Binary files /dev/null and b/_images/gl-connect-to-remote-ghe-01-v3@2x.png differ diff --git a/_images/gl-contributors-view-01-v2@2x.png b/_images/gl-contributors-view-01-v2@2x.png new file mode 100644 index 0000000..7f1edb7 Binary files /dev/null and b/_images/gl-contributors-view-01-v2@2x.png differ diff --git a/_images/gl-current-line-blame-01-v4@2x.png b/_images/gl-current-line-blame-01-v4@2x.png new file mode 100644 index 0000000..f580fd6 Binary files /dev/null and b/_images/gl-current-line-blame-01-v4@2x.png differ diff --git a/_images/gl-delete-cloud-patch-01-v3@2x.png b/_images/gl-delete-cloud-patch-01-v3@2x.png new file mode 100644 index 0000000..6073b3d Binary files /dev/null and b/_images/gl-delete-cloud-patch-01-v3@2x.png differ diff --git a/_images/gl-enable-debug-log-01-v4@2x.png b/_images/gl-enable-debug-log-01-v4@2x.png new file mode 100644 index 0000000..287a3ed Binary files /dev/null and b/_images/gl-enable-debug-log-01-v4@2x.png differ diff --git a/_images/gl-filter-options-2-01-v3@2x.png b/_images/gl-filter-options-2-01-v3@2x.png new file mode 100644 index 0000000..caa4005 Binary files /dev/null and b/_images/gl-filter-options-2-01-v3@2x.png differ diff --git a/_images/gl-git-command-palette-01-v4@2x.png b/_images/gl-git-command-palette-01-v4@2x.png new file mode 100644 index 0000000..e0ed898 Binary files /dev/null and b/_images/gl-git-command-palette-01-v4@2x.png differ diff --git a/_images/gl-gitlab-github-integration-01-v4@2x.png b/_images/gl-gitlab-github-integration-01-v4@2x.png new file mode 100644 index 0000000..67d260b Binary files /dev/null and b/_images/gl-gitlab-github-integration-01-v4@2x.png differ diff --git a/_images/gl-graph-compose-01-v3@2x.png b/_images/gl-graph-compose-01-v3@2x.png new file mode 100644 index 0000000..1bdacb2 Binary files /dev/null and b/_images/gl-graph-compose-01-v3@2x.png differ diff --git a/_images/gl-graph-details-panel-01-v2@2x.png b/_images/gl-graph-details-panel-01-v2@2x.png new file mode 100644 index 0000000..4e5a299 Binary files /dev/null and b/_images/gl-graph-details-panel-01-v2@2x.png differ diff --git a/_images/gl-graph-info-01-v3@2x.png b/_images/gl-graph-info-01-v3@2x.png new file mode 100644 index 0000000..b989268 Binary files /dev/null and b/_images/gl-graph-info-01-v3@2x.png differ diff --git a/_images/gl-graph-sidebar-01-v3@2x.png b/_images/gl-graph-sidebar-01-v3@2x.png new file mode 100644 index 0000000..ab13704 Binary files /dev/null and b/_images/gl-graph-sidebar-01-v3@2x.png differ diff --git a/_images/gl-graph-wip-bar-01-v3@2x.png b/_images/gl-graph-wip-bar-01-v3@2x.png new file mode 100644 index 0000000..8411837 Binary files /dev/null and b/_images/gl-graph-wip-bar-01-v3@2x.png differ diff --git a/_images/gl-gutter-blame-01-v3@2x.png b/_images/gl-gutter-blame-01-v3@2x.png new file mode 100644 index 0000000..db1fd99 Binary files /dev/null and b/_images/gl-gutter-blame-01-v3@2x.png differ diff --git a/_images/gl-gutter-changes-01@2x.png b/_images/gl-gutter-changes-01@2x.png new file mode 100644 index 0000000..fdd5d84 Binary files /dev/null and b/_images/gl-gutter-changes-01@2x.png differ diff --git a/_images/gl-gutter-heatmap-01-v3@2x.png b/_images/gl-gutter-heatmap-01-v3@2x.png new file mode 100644 index 0000000..f03cf8c Binary files /dev/null and b/_images/gl-gutter-heatmap-01-v3@2x.png differ diff --git a/_images/gl-hide-refs-01-v3@2x.gif b/_images/gl-hide-refs-01-v3@2x.gif new file mode 100644 index 0000000..95a8229 Binary files /dev/null and b/_images/gl-hide-refs-01-v3@2x.gif differ diff --git a/_images/gl-hovers-annotations-01-v3@2x.png b/_images/gl-hovers-annotations-01-v3@2x.png new file mode 100644 index 0000000..5b84446 Binary files /dev/null and b/_images/gl-hovers-annotations-01-v3@2x.png differ diff --git a/_images/gl-hovers-annotations-changes-01-v3@2x.png b/_images/gl-hovers-annotations-changes-01-v3@2x.png new file mode 100644 index 0000000..c987971 Binary files /dev/null and b/_images/gl-hovers-annotations-changes-01-v3@2x.png differ diff --git a/_images/gl-hovers-annotations-details-01-v3@2x.png b/_images/gl-hovers-annotations-details-01-v3@2x.png new file mode 100644 index 0000000..ee7d4f3 Binary files /dev/null and b/_images/gl-hovers-annotations-details-01-v3@2x.png differ diff --git a/_images/gl-hovers-current-line-01-v3@2x.png b/_images/gl-hovers-current-line-01-v3@2x.png new file mode 100644 index 0000000..7f6feb6 Binary files /dev/null and b/_images/gl-hovers-current-line-01-v3@2x.png differ diff --git a/_images/gl-hovers-current-line-changes-01-v3@2x.png b/_images/gl-hovers-current-line-changes-01-v3@2x.png new file mode 100644 index 0000000..52b77be Binary files /dev/null and b/_images/gl-hovers-current-line-changes-01-v3@2x.png differ diff --git a/_images/gl-hovers-current-line-details-01-v3@2x.png b/_images/gl-hovers-current-line-details-01-v3@2x.png new file mode 100644 index 0000000..740f17e Binary files /dev/null and b/_images/gl-hovers-current-line-details-01-v3@2x.png differ diff --git a/_images/gl-inspect-commit-details-01-v3@2x.png b/_images/gl-inspect-commit-details-01-v3@2x.png new file mode 100644 index 0000000..a627bcf Binary files /dev/null and b/_images/gl-inspect-commit-details-01-v3@2x.png differ diff --git a/_images/gl-inspect-overview-01-v3@2x.png b/_images/gl-inspect-overview-01-v3@2x.png new file mode 100644 index 0000000..ae701f0 Binary files /dev/null and b/_images/gl-inspect-overview-01-v3@2x.png differ diff --git a/_images/gl-line-history-view-01-v2@2x.png b/_images/gl-line-history-view-01-v2@2x.png new file mode 100644 index 0000000..3cf8bbf Binary files /dev/null and b/_images/gl-line-history-view-01-v2@2x.png differ diff --git a/_images/gl-menu-commit-details-01-v2@2x.png b/_images/gl-menu-commit-details-01-v2@2x.png new file mode 100644 index 0000000..975a4a3 Binary files /dev/null and b/_images/gl-menu-commit-details-01-v2@2x.png differ diff --git a/_images/gl-menu-commit-search-01-v2@2x.png b/_images/gl-menu-commit-search-01-v2@2x.png new file mode 100644 index 0000000..a4da3c3 Binary files /dev/null and b/_images/gl-menu-commit-search-01-v2@2x.png differ diff --git a/_images/gl-menu-file-history-01-v3@2x.png b/_images/gl-menu-file-history-01-v3@2x.png new file mode 100644 index 0000000..62af3f3 Binary files /dev/null and b/_images/gl-menu-file-history-01-v3@2x.png differ diff --git a/_images/gl-menu-stash-details-01-v3@2x.png b/_images/gl-menu-stash-details-01-v3@2x.png new file mode 100644 index 0000000..a325a56 Binary files /dev/null and b/_images/gl-menu-stash-details-01-v3@2x.png differ diff --git a/_images/gl-menu-stash-list-01-v3@2x.png b/_images/gl-menu-stash-list-01-v3@2x.png new file mode 100644 index 0000000..b9ffcfe Binary files /dev/null and b/_images/gl-menu-stash-list-01-v3@2x.png differ diff --git a/_images/gl-menus-01-v2@2x.png b/_images/gl-menus-01-v2@2x.png new file mode 100644 index 0000000..06a9d91 Binary files /dev/null and b/_images/gl-menus-01-v2@2x.png differ diff --git a/_images/gl-menus-example-01-v2@2x.png b/_images/gl-menus-example-01-v2@2x.png new file mode 100644 index 0000000..e8bb88e Binary files /dev/null and b/_images/gl-menus-example-01-v2@2x.png differ diff --git a/_images/gl-minimap-gl-settings-01-v4@2x.png b/_images/gl-minimap-gl-settings-01-v4@2x.png new file mode 100644 index 0000000..c76437c Binary files /dev/null and b/_images/gl-minimap-gl-settings-01-v4@2x.png differ diff --git a/_images/gl-prefer-commit-graph-location-01-v3@2x.png b/_images/gl-prefer-commit-graph-location-01-v3@2x.png new file mode 100644 index 0000000..aa95435 Binary files /dev/null and b/_images/gl-prefer-commit-graph-location-01-v3@2x.png differ diff --git a/_images/gl-proxy-settings-01-v4@2x.png b/_images/gl-proxy-settings-01-v4@2x.png new file mode 100644 index 0000000..0655bbe Binary files /dev/null and b/_images/gl-proxy-settings-01-v4@2x.png differ diff --git a/_images/gl-pull-request-icon-01-v3@2x.png b/_images/gl-pull-request-icon-01-v3@2x.png new file mode 100644 index 0000000..1b7bd6b Binary files /dev/null and b/_images/gl-pull-request-icon-01-v3@2x.png differ diff --git a/_images/gl-rebase-01-v3@2x.gif b/_images/gl-rebase-01-v3@2x.gif new file mode 100644 index 0000000..ada7dd8 Binary files /dev/null and b/_images/gl-rebase-01-v3@2x.gif differ diff --git a/_images/gl-remotes-view-01-v3@2x.png b/_images/gl-remotes-view-01-v3@2x.png new file mode 100644 index 0000000..5c0a42d Binary files /dev/null and b/_images/gl-remotes-view-01-v3@2x.png differ diff --git a/_images/gl-repositories-view-01-v3@2x.png b/_images/gl-repositories-view-01-v3@2x.png new file mode 100644 index 0000000..260529f Binary files /dev/null and b/_images/gl-repositories-view-01-v3@2x.png differ diff --git a/_images/gl-rich-commit-search-02-v3@2x.png b/_images/gl-rich-commit-search-02-v3@2x.png new file mode 100644 index 0000000..0957413 Binary files /dev/null and b/_images/gl-rich-commit-search-02-v3@2x.png differ diff --git a/_images/gl-search-options-01-v3@2x.png b/_images/gl-search-options-01-v3@2x.png new file mode 100644 index 0000000..e1a7b5e Binary files /dev/null and b/_images/gl-search-options-01-v3@2x.png differ diff --git a/_images/gl-settings-01-v3@2x.png b/_images/gl-settings-01-v3@2x.png new file mode 100644 index 0000000..c5ceedf Binary files /dev/null and b/_images/gl-settings-01-v3@2x.png differ diff --git a/_images/gl-settings-account-01-v3@2x.png b/_images/gl-settings-account-01-v3@2x.png new file mode 100644 index 0000000..bd8b3d0 Binary files /dev/null and b/_images/gl-settings-account-01-v3@2x.png differ diff --git a/_images/gl-settings-ai-01-v2.png b/_images/gl-settings-ai-01-v2.png new file mode 100644 index 0000000..aba61ae Binary files /dev/null and b/_images/gl-settings-ai-01-v2.png differ diff --git a/_images/gl-settings-commit-graph-01-v2.png b/_images/gl-settings-commit-graph-01-v2.png new file mode 100644 index 0000000..5135937 Binary files /dev/null and b/_images/gl-settings-commit-graph-01-v2.png differ diff --git a/_images/gl-settings-dates-01-v2.png b/_images/gl-settings-dates-01-v2.png new file mode 100644 index 0000000..c185287 Binary files /dev/null and b/_images/gl-settings-dates-01-v2.png differ diff --git a/_images/gl-settings-hovers-01-v2@2x.png b/_images/gl-settings-hovers-01-v2@2x.png new file mode 100644 index 0000000..4ed4ac6 Binary files /dev/null and b/_images/gl-settings-hovers-01-v2@2x.png differ diff --git a/_images/gl-settings-integrations-01-v2.png b/_images/gl-settings-integrations-01-v2.png new file mode 100644 index 0000000..b718a55 Binary files /dev/null and b/_images/gl-settings-integrations-01-v2.png differ diff --git a/_images/gl-settings-views-01-v3@2x.png b/_images/gl-settings-views-01-v3@2x.png new file mode 100644 index 0000000..759730a Binary files /dev/null and b/_images/gl-settings-views-01-v3@2x.png differ diff --git a/_images/gl-sign-in-4-01-v4@2x.png b/_images/gl-sign-in-4-01-v4@2x.png new file mode 100644 index 0000000..8965827 Binary files /dev/null and b/_images/gl-sign-in-4-01-v4@2x.png differ diff --git a/_images/gl-sign-out-4-01-v4@2x.png b/_images/gl-sign-out-4-01-v4@2x.png new file mode 100644 index 0000000..334717f Binary files /dev/null and b/_images/gl-sign-out-4-01-v4@2x.png differ diff --git a/_images/gl-sign-out-ls-update-01-v4@2x.png b/_images/gl-sign-out-ls-update-01-v4@2x.png new file mode 100644 index 0000000..864c73c Binary files /dev/null and b/_images/gl-sign-out-ls-update-01-v4@2x.png differ diff --git a/_images/gl-status-bar-01-v3@2x.png b/_images/gl-status-bar-01-v3@2x.png new file mode 100644 index 0000000..0d51104 Binary files /dev/null and b/_images/gl-status-bar-01-v3@2x.png differ diff --git a/_images/gl-terminal-links-01-v3@2x.png b/_images/gl-terminal-links-01-v3@2x.png new file mode 100644 index 0000000..60ba8b5 Binary files /dev/null and b/_images/gl-terminal-links-01-v3@2x.png differ diff --git a/_images/gl-visual-file-history-01-v3@2x.png b/_images/gl-visual-file-history-01-v3@2x.png new file mode 100644 index 0000000..f67fd35 Binary files /dev/null and b/_images/gl-visual-file-history-01-v3@2x.png differ diff --git a/_images/gl-workspace-indicators-01-v3@2x.png b/_images/gl-workspace-indicators-01-v3@2x.png new file mode 100644 index 0000000..cbee37a Binary files /dev/null and b/_images/gl-workspace-indicators-01-v3@2x.png differ diff --git a/_images/gl-worktrees-multi-wip-01-v3@2x.png b/_images/gl-worktrees-multi-wip-01-v3@2x.png new file mode 100644 index 0000000..bc96874 Binary files /dev/null and b/_images/gl-worktrees-multi-wip-01-v3@2x.png differ diff --git a/_images/gl-worktrees-view-01-v2@2x.png b/_images/gl-worktrees-view-01-v2@2x.png new file mode 100644 index 0000000..52b6f55 Binary files /dev/null and b/_images/gl-worktrees-view-01-v2@2x.png differ diff --git a/gitlens/GL-Agents.md b/gitlens/GL-Agents.md index 3f9200c..355b60b 100644 --- a/gitlens/GL-Agents.md +++ b/gitlens/GL-Agents.md @@ -20,7 +20,7 @@ With GitLens, you can: - Review AI-generated changes inside the Commit Graph - Compose commits directly from agent-produced work - Quickly identify sessions waiting for input -- Manage parallel worktrees and WIP changes visually +- Manage parallel worktrees and Working Changes visually GitLens 18 currently supports Claude Code integrations through GitLens-managed hooks. @@ -137,7 +137,7 @@ From the Commit Graph details panel you can: ### Open the Commit Graph Details Panel 1. Open the Commit Graph. -2. Select a commit, branch, or WIP row. +2. Select a commit, branch, or Working Changes row. 3. Toggle the details panel if it is hidden. The panel can be docked on the right side or at the bottom of the Commit Graph. Hold `Alt` while toggling the panel to switch docking locations. @@ -151,7 +151,7 @@ GitLens 18 adds AI-powered review workflows directly inside the Commit Graph. ### Start an AI Code Review 1. Open the Commit Graph. -2. Select a WIP row or commit. +2. Select a Working Changes row or commit. 3. Open the details panel. 4. Switch to Review mode. @@ -175,7 +175,7 @@ Commit Composer is integrated directly into the Commit Graph details panel. You ### Compose a Commit 1. Open the Commit Graph. -2. Select a WIP row. +2. Select a Working Changes row. 3. Open the details panel. 4. Switch to Compose mode. 5. Review proposed commit groupings. @@ -193,7 +193,7 @@ Compose mode supports: ## Manage Multi-Worktree Workflows -GitLens 18 introduces multi-worktree WIP rows in the Commit Graph. Instead of showing changes only for the active worktree, the Commit Graph displays work-in-progress rows for every connected worktree. +GitLens 18 introduces multi-worktree Working Changes rows in the Commit Graph. Instead of showing changes only for the active worktree, the Commit Graph displays a Working Changes row for every connected worktree. This makes it easier to: @@ -203,11 +203,11 @@ This makes it easier to: - Resolve conflicts - Compose commits from multiple worktrees -Each WIP row updates live as files change. +Each Working Changes row updates live as files change. -### Use WIP Scroll Markers +### Use Working Changes Scroll Markers -The Commit Graph minimap includes WIP scroll markers that highlight work-in-progress rows. You can customize marker colors or enable and disable markers in settings. +The Commit Graph minimap includes scroll markers that highlight Working Changes rows. You can customize marker colors or enable and disable markers in settings. --- @@ -249,7 +249,7 @@ Pinned branches remain visible across Commit Graph sessions. ## Resolve Conflicts in the Commit Graph -Conflict resolution workflows extend directly into the Commit Graph. You can resolve merge conflicts from Commit Graph WIP rows or the Interactive Rebase editor. Conflict states appear inline inside the details panel. +Conflict resolution workflows extend directly into the Commit Graph. You can resolve merge conflicts from Commit Graph Working Changes rows or the Interactive Rebase editor. Conflict states appear inline inside the details panel. --- diff --git a/gitlens/GL-Branch-Prep-to-ship.md b/gitlens/GL-Branch-Prep-to-ship.md index f9e64be..e13c148 100644 --- a/gitlens/GL-Branch-Prep-to-ship.md +++ b/gitlens/GL-Branch-Prep-to-ship.md @@ -6,7 +6,7 @@ taxonomy: category: gitlens --- -Last updated: August 2026 +Last updated: September 2026 Writing the code is only part of getting work ready to merge. Upstream changes, messy commit history, overlapping work, and merge conflicts can all stand between a finished change and a branch that’s ready to ship. @@ -38,7 +38,7 @@ Development rarely produces perfectly organized commits on the first pass. Use Commit Composer to turn working changes into clean, logical commits that make the work easier to understand and review.
- + Commit Graph with the Composing Changes panel open beside it: the main branch, an Unstaged changes entry with four files changed (README.md, reports.ts, spending-analysis.ts, user-management.ts) and the Instructions box with the Compose button
With Compose, you can: diff --git a/gitlens/GL-Cloud-Patches.md b/gitlens/GL-Cloud-Patches.md index 74139d9..3d8b979 100644 --- a/gitlens/GL-Cloud-Patches.md +++ b/gitlens/GL-Cloud-Patches.md @@ -6,7 +6,7 @@ taxonomy: --- -Last updated: August 2025 +Last updated: September 2026 ## What Are Cloud Patches? @@ -80,7 +80,7 @@ Cloud Patches shared with you appear under **Shared with Me** in the Cloud Patch 2. Select **Delete Cloud Patch…**
- Deleting a Cloud Patch in GitLens + Cloud Patches view in the GitLens sidebar showing a right-click context menu with Delete Cloud Patch option on a patch entry
Deleting a Cloud Patch
diff --git a/gitlens/GL-Commit-Graph.md b/gitlens/GL-Commit-Graph.md index 37acf81..2d390b2 100644 --- a/gitlens/GL-Commit-Graph.md +++ b/gitlens/GL-Commit-Graph.md @@ -6,14 +6,18 @@ taxonomy: --- -Last updated: August 2025 +Last updated: September 2026 -## Commit Graph PRO +## Commit Graph -The GitLens Commit Graph provides an interactive view of your repository history. It shows commits, branches, and collaborators in one place, helping you understand contributions and make faster decisions. +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.
- Commit Graph in GitLens showing branches and commits + Commit Graph in GitLens showing branches and commits
Commit Graph overview in GitLens
@@ -21,6 +25,9 @@ The GitLens Commit Graph provides an interactive view of your repository history ### 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 @@ -39,12 +46,14 @@ The Commit Graph opens in a new tab, where you can scroll through history and re At the top of the Commit Graph, you’ll see: -- **Repository name** +- **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** (click **Fetch** to update) +- **Last fetched time** — shown beside **Fetch** and in its hover (click **Fetch** to update) + +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.
- Repository details in the Commit Graph toolbar + The top of the Commit Graph in the editor area: the tab reads "Commit Graph: Playground2026", the header shows the current branch (main) with Push and "Fetch (1wk ago)" buttons, and the Fetch button's hover popover lists the upstream (origin/main on GitHub), "Last fetched last week" and the Auto-fetch option
Repository details in the Commit Graph toolbar
@@ -52,8 +61,8 @@ At the top of the Commit Graph, you’ll see: ### Availability -- The Commit Graph is available to all users for **public** and **local** repositories. -- A **paid GitLens subscription or trial** is required for use with **private repositories**. +- 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**. --- @@ -61,18 +70,108 @@ At the top of the Commit Graph, you’ll see: We’d love your input! Share ideas and feedback in the [GitLens Commit Graph discussion on GitHub](https://github.com/gitkraken/vscode-gitlens/discussions/2158). +--- + +### 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: + +- **Overview**: Displays branch cards with Working Changes stats and upstream tracking information at a glance. +- **Focus Branch**: Scopes the graph to a single branch, filtering out unrelated history. +- **Agent Branches**: Filters branches to show only those associated with AI agent sessions. +- **Agent Sessions**: A Kanban-style panel for monitoring and managing active agent sessions. Branches with running agent sessions display status pills directly in the graph, so you can track agent activity at a glance. + +
+ The Commit Graph with its sidebar panel expanded on the Branches section, listing the repository's branches beside the graph; the rail also offers remotes, stashes, tags and worktrees +
The Commit Graph sidebar with branches, remotes, and worktrees
+
+ +#### Detail Sheets + +Clicking on a branch, pull request, or comparison in the sidebar 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. + +--- + +### 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, an unpushed arrow with an ahead count when commits have not been pushed, and changed file counts on hover. The `gitlens.graph.overviewBar.visibility` setting controls when the overview bar is shown. + +
+ The worktree overview above the Commit Graph, ringed, with one pill per worktree: main with its upstream legs, and the feature/api-hardening and docs/contributing-refresh worktree pills each showing a dirty indicator and an unpushed arrow +
Worktree pills above the graph
+
+ +#### 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. + +
+ The Commit Graph with the embedded details panel on the right, showing commit message, author, and changed files for the selected commit +
Embedded details panel showing commit information
+
+ +#### 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. + +#### 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. A keyboard shortcuts reference dialog is available listing all graph shortcuts organized by category. + +--- ### 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 shows added lines in green and deleted lines in red. +- 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. Lanes can be folded to collapse inactive branches and reduce visual clutter. + +#### 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 +- **Colored reference pills**: merge target and other branch roles
- Commit Graph column settings menu showing toggle options + Commit Graph settings menu showing options to hide the Author, Date, SHA, Changes, and other columns, switch the graph layout, and use a compact layout
Commit Graph column settings
@@ -82,21 +181,23 @@ You can configure the Commit Graph to control what information is shown and how - You can open the Commit Graph in both layouts simultaneously. To switch layouts: -1. Select the settings gear in the top-right corner of the Commit Graph editor. -2. Choose **Prefer Commit Graph in Panel Layout** or **Prefer Commit Graph in Editor Area**. +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 `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.
- Commit Graph layout preference menu + The Commit Graph open in the editor area with the tab's More Actions (…) menu expanded, listing Prefer Commit Graph in Editor and Prefer Commit Graph as a View among the editor actions
Switching between Editor and Panel Layout
#### Compact Graph Layout -- Right-click the **Graph** column header and select **Compact Graph Column Layout** to reduce visual complexity. +- 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.
- Compact Commit Graph layout with icons and avatars + Compact Commit Graph layout toggle showing the graph switching from normal to compact view with icons and avatars
Compact Graph and Author column with avatars
@@ -105,9 +206,12 @@ 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](/gitlens/gitlens-features/#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. +
Commit Graph scroll markers indicating branch and search results
Scroll markers in the Commit Graph
@@ -124,10 +228,14 @@ Adjust Commit Graph settings from the Command Palette: Search for **GitLens: Open Settings**.
- Commit Graph settings in VS Code + VS Code Command Palette filtered to "GitLens: Settings" with the GitLens: Open Settings command highlighted, the step that opens the GitLens settings for the Commit Graph
Opening Commit Graph settings
+
+

Note: The gitlens.graph.showDetailsView setting and the standalone Graph Details view have been removed. The details panel is now always embedded in the Commit Graph. The gitlens.proxy setting has also been removed.

+
+ --- ### Rich Commit Search @@ -141,7 +249,7 @@ The Commit Graph supports rich search across your entire repository. You can sea - Previous result: Shift + F3 (Windows/Linux) or Shift + Cmd + G (macOS)
- Commit Graph search bar highlighting results + Commit Graph search bar highlighting results
Searching commits in the Commit Graph
@@ -149,7 +257,7 @@ You can also: - Jump to the **first or last result** by holding Shift while clicking the arrow icons.
- Navigating commit search results with arrow keys + Navigating commit search results with arrow keys in the Commit Graph, showing the selection jumping between matching commits
Navigating commit search results
@@ -162,13 +270,15 @@ Use these filters in the search bar: - `Change:` - `@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. Time-based operators such as `after:` and `before:` are available for filtering commits by date. + Additional options: - Match all - Match case - Use regular expressions
- Commit Graph search options for case sensitivity and regex + Commit Graph search box with the query "fix" and a ring around the search option toggles at its right end: Match Case, Match Whole Word, Use Regular Expression and Match All, next to the 1 of 6 result counter
Commit Graph search options
@@ -185,6 +295,25 @@ 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. + +--- + +### AI Auto Rebase PRO + +AI 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: AI Auto Rebase** from the Command Palette or the graph context menu. +- 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. +- If the result is unsatisfactory, use **GitLens: Undo AI Auto Rebase** to revert to the 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. --- @@ -192,8 +321,10 @@ Helpful context menu actions include: 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](/gitlens/settings/#remote-provider-integration-settings). +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. +
- Commit Graph branch showing pull request icon + The Commit Graph with the fixture/code-suggest-demo branch pill ringed: after the branch name and its origin remote the pill carries the pull-request icon, which marks the branch as having an associated open pull request
Pull request icon in Commit Graph
@@ -202,18 +333,19 @@ For GitHub and GitLab, the Commit Graph displays a Pull Request icon for any bra ### Hiding Remotes, Branches, or Tags The Commit Graph shows refs to your remotes, branches, and tags. -- Hover over any ref to use the **Hide** option. +- 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 scope/filter popover next to the search box. - To show them again, hover over the **Hide** option at the top of the Commit Graph and select the desired refs.
- Hiding refs from the Commit Graph view + Hiding a branch in the Commit Graph: right-clicking the conflict-branch ref opens its context menu, and choosing Hide Local Branch removes the ref from the graph
Hiding refs in the Commit Graph
#### Filter Options Access filters from the dropdown menu to choose: -- **Show Current Branch Only**: Displays the current branch and its upstream remote. -- **Show All Local Branches** *(default)*. +- **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. Additional options let you hide or show: - Remote-only branches @@ -223,19 +355,20 @@ Additional options let you hide or show: You can also dim merge commit rows for clarity.
- Commit Graph filter options for branches, tags, and stashes + Commit Graph filter options for branches, tags, and stashes
Commit Graph filter options
--- -### Minimap (Experimental) +### 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 graph icon dropdown to switch between **Commits** or **Lines Changed** views. +- 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`.
Commit Graph Minimap enabled in the toolbar @@ -243,7 +376,7 @@ The Minimap provides a high-level overview of repository activity. It shows comm
- Commit Graph Minimap settings with commits or lines changed options + Commit Graph with the minimap strip above the rows and its Minimap Options popover open: a Minimap group with Commits (selected), Lines Changed and Reverse Direction, and a Markers group with checkboxes for Local Branches, Remote Branches, Pull Requests, Stashes, Tags and Worktrees
Minimap settings and options
diff --git a/gitlens/GL-GK-AI.md b/gitlens/GL-GK-AI.md index 115227b..980b559 100644 --- a/gitlens/GL-GK-AI.md +++ b/gitlens/GL-GK-AI.md @@ -7,6 +7,8 @@ taxonomy: --- +Last updated: September 2026 + Merge cutting-edge AI capabilities with your Git workflow to save time, increase clarity, and enhance collaboration. GitLens' AI features transform how you create, understand, and document code changes. --- @@ -20,12 +22,16 @@ GitLens integrates powerful AI capabilities across different subscription tiers, Generate clear, descriptive commit messages based on your code changes, saving time and ensuring consistency across your repository. The AI analyzes your staged changes and creates meaningful messages that accurately describe what you've modified. +In addition to single commit messages, the Commit Composer can create multiple logical commits from your working tree changes, and Automatic Rebase restructures an existing branch onto a target commit with AI-generated commits. Both include undo support and first-time confirmation dialogs. + **How to access:** -- From the Command Palette: `GitLens: Generate Commit Message with AI` -- From the SCM panel: Click the "Generate Commit Message" button +- From the Command Palette: `GitLens: Generate Commit Message` +- From the Command Palette: `GitLens: Compose Commits...` (the Commit Composer creates multiple logical commits from your working changes) +- From the Command Palette: `GitLens: Automatic Rebase...` (restructures branch commits) +- From the SCM panel: Open the GitLens sparkle menu in the Changes header and choose **Generate Commit Message** - During the commit process: Look for the AI option in the commit interface - +The Source Control view with a staged file and an empty commit message box; GitLens's sparkle button in the Changes header — the way to generate the commit message with AI — is ringed ### AI Stash Messages`Pro` **Available in:** Pro, Advanced, and Business plans @@ -37,7 +43,7 @@ Create intelligent descriptions for stashed changes, making it easier to find an - When creating a stash: Look for the AI option in the stash creation interface - From the stash view: Generate descriptions for existing stashes - +Push Stash QuickPick with an AI-generated stash message filled into the message input by GitKraken AI ### AI Commit Explain `Pro` **Available in:** Pro, Advanced, and Business plans @@ -53,8 +59,9 @@ Understand the reasoning behind changes with AI-generated explanations of commit ### AI Changes Explain `Preview` -Gitkraken AI can also be used to generate summaries in Branches, Working changes, and Stashes. +Gitkraken AI can also be used to generate summaries for Commits, Branches, Working Changes, and Stashes. +What a specific commit introduced – ✨Explain Commit What changed across all commits in a branch – ✨Explain Branch What you’ve modified in your working directory – ✨Explain Working Changes What you’ve previously stashed – ✨Explain Stash @@ -64,6 +71,7 @@ You’ll find ✨Explain options for commits, branches, stashes, and working cha - In the Commit Graph - Available as commands in the command palette - In many GitLens views: Commits, Branches, Stashes, Search & Compare, etc. +- In editor blame hovers via the ✨Explain button ### AI Changelog Creation `Pro` **Available in:** Advanced and Business plans only @@ -87,6 +95,43 @@ Open Pull Requests: Automatically generate clear PR titles and descriptions dire +### AI Review `Pro` +**Available in:** Pro, Advanced, and Business plans + +Inspect commits or Working Changes before they move forward. GitKraken AI surfaces potential bugs, security issues, and other areas that deserve attention — tagged by severity — directly in the Commit Graph details panel, while you decide what needs to change. + +**How to access:** +- In the Commit Graph: Select a commit or the Working Changes row, then open Review mode in the details panel +- Customize review behavior with the `gitlens.ai.reviewChanges.customInstructions` setting + +You can configure separate AI models for different features (such as compose and review) to optimize for your preferred balance of speed and quality. + +### AI Auto Rebase `Pro` +**Available in:** Pro, Advanced, and Business plans + +Move a rebase forward with AI-assisted conflict resolution. AI Auto Rebase resolves a conflict only when its confidence meets the threshold you configure; anything below that threshold pauses the rebase so you can resolve it yourself. A rebase summary sheet shows what was resolved and how, and full undo support returns you to the pre-rebase state if the result is not what you wanted. + +**How to access:** +- From the Command Palette: `GitLens: AI Auto Rebase` +- From the Commit Graph: Right-click a branch and select AI Auto Rebase + +**Key settings:** +- `gitlens.ai.autoRebase.confidenceThreshold` — Set the minimum confidence level (0-1) for automatic conflict resolution +- `gitlens.ai.resolveConflicts.customInstructions` — Provide custom instructions for how conflicts should be resolved + +### Compose and Recompose `Pro` +**Available in:** Pro, Advanced, and Business plans + +Shape your commit history with AI-assisted commit crafting and branch restructuring. + +- **Compose**: Craft clean, logical commits from your Working Changes using the Commit Composer in the Commit Graph +- **Recompose**: 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 + +**How to access:** +- From the Commit Graph: Enter Compose mode to create commits from working changes +- From the Commit Graph context menu: Right-click commits to access Recompose Branch, Recompose from Commit, or Recompose Selected Commits +- From the Command Palette: `GitLens: Recompose Branch` + --- ## AI Credit Allocation by Plan @@ -106,6 +151,7 @@ GitLens offers flexibility in choosing your AI provider: 3. **Custom Provider** (BYOK): Connect your own key from supported AI services > - New OpenAI and Google models +- Mistral - Self-hosted Azure AI models - OpenAI-compatible API providers - Local Ollama models @@ -128,6 +174,14 @@ To configure your AI provider: - **Credit usage monitoring**: Track your credit consumption for better allocation management - **Default AI mode**: Choose between concise or detailed outputs for each feature +### AI File Exclusions + +Control which files are included in AI context to protect sensitive data: + +- **Ignore files**: GitLens respects `.aiignore`, `.cursorignore`, and `.aiexclude` files in your repository to exclude matching paths from AI prompts +- **Exclude setting**: Use the `gitlens.ai.exclude.files` setting to define additional file patterns to exclude +- Common files like lock files, minified assets, and build output directories are excluded by default + ### Organization-Level Controls `Business` - **Enforceable AI rules**: Set organization-wide policies for AI usage diff --git a/gitlens/GL-Integrations.md b/gitlens/GL-Integrations.md index 170a2b7..d2fd389 100644 --- a/gitlens/GL-Integrations.md +++ b/gitlens/GL-Integrations.md @@ -5,7 +5,7 @@ taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026 GitLens supports a wide range of remote providers to enhance your Git workflow inside Visual Studio Code. Supported platforms include: @@ -14,7 +14,8 @@ GitLens supports a wide range of remote providers to enhance your Git workflow i - Gitea - Gerrit - Bitbucket (Cloud and Server) -- Azure DevOps +- Azure DevOps (Cloud and Server) +- Linear (issue tracking) You can also define [custom remote providers or providers with custom domains](/gitlens/settings/#remote-provider-integration-settings). @@ -42,6 +43,7 @@ You can use the following GitLens commands to interact with files, commits, and ### Files - **Open File from Remote** (`gitlens.openFileFromRemote`) — Open a local file by specifying a remote file URL +- **Open Revision from Remote** (`gitlens.openRevisionFromRemote`) — Open a specific file revision from a remote URL, resolving the exact revision rather than the working copy - **Open File on Remote** (`gitlens.openFileOnRemote`) — Open the current file or revision on the remote - **Copy Remote File URL** (`gitlens.copyRemoteFileUrlToClipboard`) — Copy the URL of the current file or revision - **Open File on Remote From...** (`gitlens.openFileOnRemoteFrom`) — Open a file/revision from a specific branch or tag @@ -82,18 +84,18 @@ To connect GitHub or GitLab to GitLens, you'll use your GitKraken account via th #### Steps to Connect: 1. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`) and run `GitLens: Manage Integrations`, **or** -2. Go to the **GitKraken Account** section in the GitLens Activity Bar and choose **Integrations**. +2. In the GitLens **Home** view, select the integrations chip in the header to open the **Integrations** popover, then its gear (**Manage Integrations**).
- -
Navigate to Integrations in the GitKraken Account menu
+ The GitLens Home view with the Integrations popover open from the header's integrations chip: a list of providers — GitHub, GitLab, Azure DevOps, Bitbucket, Jira, Linear — each with what it supports and a connected check mark, a Show: All | Connected filter, and the Manage Integrations gear ringed in the popover header +
Open the Integrations popover from the Home view header
3. If you’re not already signed in, log into your GitKraken account. 4. Click **Connect with GitHub** or **Connect with GitLab** and complete the sign-in process. 5. Select **Complete Setup** to return to Visual Studio Code and activate the integration. -You can connect multiple integrations if needed. +You can connect multiple integrations if needed, including multiple accounts for the same provider. For example, you can connect both a personal and a work GitHub account simultaneously. Use the integration settings to set a primary account, manage connections, and scope searches to a specific account.
@@ -104,6 +106,14 @@ You can connect multiple integrations if needed.

Community users are limited to basic functionality only.

+## GitHub PR Stacks `PRO` + +GitLens supports stacked pull request workflows on GitHub.com. When working with stacked PRs, GitLens shows stack information including the stack size, your PR's position within the stack, and the base ref. Merge operations are stack-aware, letting you choose to merge a single layer or the entire stack. + +PR stack details appear in the Commit Graph pull request sheet when viewing a PR that belongs to a stack. + +*** + ## GitHub Enterprise Server and GitLab Self-Managed Integration `PRO` GitLens Pro supports advanced integration with GitHub Enterprise Server and GitLab Self-Managed. @@ -115,7 +125,7 @@ Once authenticated, GitLens enhances autolinks for these services in hover cards - Pull request and issue details directly in the Sidebar views
- + The Commit Graph with the pull-request hover card open over the #7 badge of the fixture/code-suggest-demo branch pill: the pull request's title "fix: add types and config to rate limiter", its number, who opened it and when it was last updated — metadata supplied by the connected GitHub integration
Enhanced hover cards with issue and PR metadata
@@ -141,7 +151,7 @@ Or for GitLab: 5. Click **Connect to Remote**
- + GitLens Remotes sidebar view listing repository remotes with the Connect to Remote action icon for linking a self-hosted provider
Use the plug icon to connect a self-managed remote
@@ -167,14 +177,14 @@ GitLens Pro supports integration with Jira Cloud via your GitKraken Account. Thi ### Connect the Jira Integration -1. Open the GitLens Sidebar and navigate to the **GitKraken Account** view. -2. Select **Cloud Integrations**. +1. Open the GitLens Settings editor (run _GitLens: Open Settings_ from the Command Palette). +2. Select **Cloud Integrations** under **Integrations** in the navigation rail. 3. Choose **Jira Cloud** and follow the prompts to connect. 4. Allow GitKraken access to your Atlassian Account. You can also configure this via the [Integration Settings](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens) in a browser.
- -
Jira integration via GitLens Cloud Integrations panel
+ GitLens Settings Cloud Integrations category showing provider connection cards for GitHub, GitLab, Azure DevOps, Bitbucket, Jira, and Linear +
Cloud Integrations category in the GitLens Settings editor
diff --git a/gitlens/GL-Parallel-dev-workflow.md b/gitlens/GL-Parallel-dev-workflow.md index 62c1da5..ec80ac9 100644 --- a/gitlens/GL-Parallel-dev-workflow.md +++ b/gitlens/GL-Parallel-dev-workflow.md @@ -6,7 +6,7 @@ taxonomy: category: gitlens --- -Last updated: August 2026 +Last updated: September 2026 Modern development rarely happens in a single branch. Developers and coding agents can work across multiple branches, worktrees, and tasks at the same time, creating more parallel streams of work to understand and coordinate. @@ -27,7 +27,7 @@ See branches, worktrees, working changes, commits, HEAD, upstream, merge targets Multi-worktree WIP also surfaces working changes across your worktrees, so active work stays visible even when you aren’t currently working in that worktree.
- + Commit Graph with Working Changes rows for three worktrees: the main worktree's row at the top, then "Working Changes (feature/api-hardening)" and "Working Changes (docs/contributing-refresh)" above their branches' unpushed commits, each branch pill showing its ahead count
## 2. Monitor Agent Work @@ -42,7 +42,7 @@ From the Commit Graph, you can: - Resume active or previous sessions with the surrounding Git context intact
- + The Working Changes details panel with its Agents section expanded: three Claude Code session cards — "Add retry logic to the rate limiter middleware" marked Working with the file it is editing, "Review the authentication module for discrepancies" marked Idle, and "Update README with API rate limiting docs" marked Completed — above the changed files and the commit box
diff --git a/gitlens/GL-Visual-File-History.md b/gitlens/GL-Visual-File-History.md index d9e3f88..ca5b36c 100644 --- a/gitlens/GL-Visual-File-History.md +++ b/gitlens/GL-Visual-File-History.md @@ -6,28 +6,34 @@ taxonomy: --- -Last updated: August 2025 +Last updated: September 2026 -## Visual File History +## Visual History -The GitLens **Visual File History** shows how a file has evolved, including when changes were made, the size of those changes, and who made them. +The GitLens **Visual History** (formerly Visual File History) shows how your code has evolved, including when changes were made, the size of those changes, and who made them. Visual History supports multiple scopes: view the history of a single file, a folder, an entire repository, or a specific branch. --- -### Open Visual File History +### Open Visual History -You can open the Visual File History view in two ways: +You can open the Visual History view in two ways: 1. From the **GitLens Inspect** sidebar. - - Open the sidebar, then select the **Visual File History** view. + - Open the sidebar, then select the **Visual History** view. 2. From the **Command Palette**: - macOS: Cmd + Shift + P - Windows/Linux: Ctrl + Shift + P - - Search for **GitLens: Show Visual File History View**. + - Search for **GitLens: Show Visual History View**. + +### Scope Options + +- **File or Folder**: Visualize the history of a specific file or folder +- **Repository**: See the full history of your entire repository +- **Branch**: Slice history by branch to focus on a specific line of work
- Visual File History view in GitLens showing commits plotted by author and time -
Visual File History view
+ Visual History view for CHANGELOG.md showing eight commits by four authors plotted as colour-coded bubbles over the last four weeks, with the additions and deletions of each commit shown as bars +
Visual History view
--- diff --git a/gitlens/GL-Workflow-Cleanup-prepare-for-review.md b/gitlens/GL-Workflow-Cleanup-prepare-for-review.md index 89ed243..6a738a3 100644 --- a/gitlens/GL-Workflow-Cleanup-prepare-for-review.md +++ b/gitlens/GL-Workflow-Cleanup-prepare-for-review.md @@ -5,6 +5,8 @@ taxonomy: category: gitlens --- +Last updated: September 2026 + **Level:** Intermediate Developers **Primary Goal:** Use Git intelligence to transform iterative work into clean, reviewable history @@ -71,6 +73,8 @@ GitLens uses Git intelligence to help you ship work that is easier to review, re - [Launchpad (PR and review awareness)](https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro) +- [Start Review](/gitlens/gl-accelerate-pr-reviews/#start-review-pro) (quick-pick wizard to select a PR, check out branch or worktree, and optionally open AI review chat) + - Worktrees (parallel branch workflows) - Commit Graph context menu actions diff --git a/gitlens/GL-Workspaces.md b/gitlens/GL-Workspaces.md index 0067894..78a4497 100644 --- a/gitlens/GL-Workspaces.md +++ b/gitlens/GL-Workspaces.md @@ -5,7 +5,7 @@ taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026 Workspaces in GitLens help you organize and manage multiple repositories from one convenient interface. Whether you're working solo or collaborating with a team, Workspaces simplify project access and context switching. @@ -105,10 +105,10 @@ Your Cloud Workspace will be synced to your GitKraken account and accessible via ### Understanding Workspace Indicators and Colors Visual indicators in Workspaces help you quickly understand their status. For example: -- A **green Workspace** with an **O** symbol indicates it is open in your current window. +- A **green Workspace** with a **green dot** indicates it is open in your current window.
- + The Cloud Workspaces view filtered to Playground2026: under Current Window the repository is listed, and in the Demo2026 workspace the same repository is drawn in green with a green dot at the end of its row — the indicator for the repository open in the current window
Workspace status indicators
diff --git a/gitlens/GL-Worktrees.md b/gitlens/GL-Worktrees.md index c66526d..218407f 100644 --- a/gitlens/GL-Worktrees.md +++ b/gitlens/GL-Worktrees.md @@ -6,12 +6,12 @@ taxonomy: --- -Last updated: August 2025 +Last updated: September 2026 ## Worktrees View
- GitLens Worktrees view in VS Code showing multiple branches + GitLens Worktrees view in VS Code showing multiple branches
GitLens Worktrees view
diff --git a/gitlens/GL-accelerate-pr-reviews.md b/gitlens/GL-accelerate-pr-reviews.md index 4589468..11110a5 100644 --- a/gitlens/GL-accelerate-pr-reviews.md +++ b/gitlens/GL-accelerate-pr-reviews.md @@ -5,7 +5,7 @@ taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026
@@ -48,6 +48,20 @@ To start reviewing:
+## Start Review `PRO` + +The **Start Review** command provides a quick-pick wizard for jumping into a pull request review. It walks you through selecting an integration, picking a PR, and choosing how to check it out (as a branch or in a new worktree). You can also optionally open an AI chat with a review prompt to assist your review. + +To use Start Review: + +1. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`). +2. Run: `GitLens: Start Review`. +3. Select your integration and pull request, then choose your checkout method. + +
+

This feature is available with a GitLens Pro subscription or higher.

+
+ ## Worktrees Worktrees let you check out multiple branches simultaneously in separate working directories. This means you don’t need to commit or stash in-progress changes before switching to another branch—perfect for reviewing pull requests without disrupting your workflow. diff --git a/gitlens/gitlens-faq.md b/gitlens/gitlens-faq.md index 59116d6..2ddf25f 100644 --- a/gitlens/gitlens-faq.md +++ b/gitlens/gitlens-faq.md @@ -7,7 +7,7 @@ taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026 Get answers to frequently asked questions about GitLens features, sign-in options, and GitKraken account integration. @@ -39,7 +39,7 @@ You can also sign in via the VS Code Command Palette: - Type and select `GitLens: Sign In to GitKraken...`.
- VS Code command palette with sign-in command + VS Code Command Palette filtered to "GitLens: Sign" with the GitLens: Sign In to GitKraken command highlighted
Sign in using the command palette
@@ -47,11 +47,11 @@ You can also sign in via the VS Code Command Palette: To sign out: -- Click the GitLens icon in the sidebar. -- Under **GITKRAKEN ACCOUNT**, select `Sign Out`. +- Click the GitLens icon in the sidebar to open the **Home** view. +- Select the account chip (your plan name) at the top of the view, then select the **Sign Out** button in the popover.
- GitLens sidebar with sign-out option + The GitLens Home view with the account chip's popover open: the GitLens Pro plan header with its ENTERPRISE badge and the Synchronize Status, Manage Account and Sign Out icon buttons — Sign Out ringed — above the organization row and the Refer a friend link (the account's name, e-mail and avatar are blanked)
Sign out from the GitLens sidebar
@@ -61,7 +61,7 @@ Or use the VS Code Command Palette: - Type and select `GitLens: Sign Out of GitKraken`.
- VS Code command palette with sign-out command + VS Code Command Palette filtered to "GitLens: Sign" with the GitLens: Sign Out of GitKraken command highlighted
Sign out using the command palette
@@ -69,9 +69,9 @@ Or use the VS Code Command Palette: ## How do I enable debug logging? -You can enable debug logging by opening the Command Palette (`ctrl+shift+p` or `command+shift+p`) and running the command `GitLens: Enable Debug Logging`. +You can enable debug logging by opening the Command Palette (`ctrl+shift+p` or `command+shift+p`) and running the command `GitLens: Enable Debug (Trace) Logging`. - +VS Code Command Palette filtered to "GitLens: Debug Logging" with the GitLens: Enable Debug (Trace) Logging command highlighted To view logs, open the Output Window (View > Output). The logs will be listed in the _GitLens_ and _GitLens (Git)_ channels. These channels can be toggled from the dropdown. @@ -89,10 +89,16 @@ You can export logs using the actions in the overflow menu of the Output view. ## Can GitLens or Visual Studio Code Work with a Proxy? -Yes, you can configure proxy settings from the Visual Studio Code settings. To open these settings, use the keyboard shortcut `command/ctrl + ,`. Then, search for "proxy" to see all related settings. +Yes. GitLens has no proxy setting of its own; it uses Visual Studio Code's **Http: Proxy** settings (`http.proxy` and related settings). To open these settings, use the keyboard shortcut `command/ctrl + ,`. Then, search for `http.proxy` to see the related settings. + +VS Code Settings editor searched for "http.proxy": the Http: Proxy settings — Proxy (empty), Proxy Authorization, Proxy Kerberos Service Principal, Proxy Strict SSL (checked) and Proxy Support — each with its description + + +*** - +## Does GitLens Support Git Submodules? +Yes. GitLens provides basic Git submodule support, including automatic discovery and tracking of submodules in your workspace. Submodules are distinguished with their own icons in sidebar views, and diffs correctly handle submodule pointer changes. GitLens detects superproject paths and tracks submodule status alongside your main repository. *** diff --git a/gitlens/gitlens-features.md b/gitlens/gitlens-features.md index 6294cd9..edd1e51 100644 --- a/gitlens/gitlens-features.md +++ b/gitlens/gitlens-features.md @@ -4,7 +4,7 @@ description: Learn how to use GitLens autolinks, terminal links, powerful Git co taxonomy: category: gitlens --- -Last updated: June 2025 +Last updated: September 2026 Features marked with `PRO` require a [trial or paid plan](https://www.gitkraken.com/gitlens/pricing?source=help_center&product=gitlens) for use on privately hosted repositories. @@ -50,7 +50,7 @@ Available commands: ## Current Line Blame
- GitLens current line blame showing inline annotation + Editor with the current line's blame annotation shown inline at the end of the line: the author, the date and the start of the commit message
Blame annotation showing author, date, and commit message
@@ -72,7 +72,7 @@ You can control visibility with the command: ## Git CodeLens
- GitLens CodeLens annotations above file and code blocks + GitLens CodeLens annotations above file and code blocks
Inline Git insights for authorship and history
@@ -108,7 +108,7 @@ Click behavior for each CodeLens is fully [customizable](/gitlens/settings/#git- ## Status Bar Blame
- Status bar showing Git blame annotation with author and date + The right end of the VS Code status bar with the GitLens blame item ringed: the author and date of the commit for the current line, beside the line/column, indentation, encoding, line-ending and language items
Quick access to blame details in the VS Code status bar
@@ -143,14 +143,14 @@ GitLens provides rich, [customizable](/gitlens/settings/#hover-settings) hover a ### Current Line Hovers
- Current line hover in GitLens + Hover tooltip over the current line blame annotation showing commit summary and author for the active line
Git blame hover shown over the current line
#### Details Hover
- GitLens current line details hover with commit info and actions + Details hover for the current line showing commit metadata, author, date, the commit message, and the quick-action command bar (SHA, copy, search, graph, Explain)
Expanded commit info and quick actions
@@ -166,8 +166,8 @@ Features: #### Changes (Diff) Hover
- GitLens diff hover showing current vs. previous line version -
View the previous version of a changed line
+ Changes hover for the current line showing the inline diff of the commit that introduced the line, with a link to compare the two revisions +
View the diff of the commit that changed the current line
Displays the previous version of the current line. @@ -178,7 +178,7 @@ Displays the previous version of the current line. ### Annotation Hovers
- GitLens annotation hover example + Hover tooltip over a blame annotation in the gutter showing commit summary and author information
Hover insights while annotating with blame
@@ -187,7 +187,7 @@ Accessible when blame annotations are active, these hovers provide the same deta #### Details Hover
- Details hover during annotation + Details hover over a blame annotation showing commit metadata, author, date, the commit message, and the quick-action command bar (SHA, copy, search, graph, Explain, PR)
Commit metadata and action menu per line
@@ -200,7 +200,7 @@ Shows rich commit details per line with: #### Changes (Diff) Hover
- Changes hover during annotation + Changes hover over a blame annotation showing an inline diff with the previous version of the line
Inline diff hover showing previous line content
@@ -215,8 +215,8 @@ Reveals the previous version of each annotated line. ## File Blame
- GitLens file blame annotations in the editor gutter -
View who last modified each line and when
+ File blame annotations in the editor gutter of README.md: every line carries the message and date of the commit that last changed it, so the blocks of lines from different commits stand out +
See which commit last modified each line, and when — hover for the author
File Blame adds [customizable](/gitlens/settings/#gutter-blame-settings), [themable](/gitlens/settings/#themable-colors) inline annotations that show the commit and author responsible for each line in a file. @@ -238,7 +238,7 @@ File Blame adds [customizable](/gitlens/settings/#gutter-blame-settings), [thema ## File Changes
- File changes annotations highlighting modified lines + File Changes annotations in README.md with the gutter and line locations enabled: the uncommitted edits at the bottom of the file — one modified line and a new "Release checklist" section — are highlighted, with the matching marker in the gutter, while the unchanged lines above are plain
Highlight unpublished or most recent changes
@@ -258,7 +258,7 @@ This feature is [customizable](/gitlens/settings/#file-changes-settings) and [th ## File Heatmap
- GitLens file heatmap on the right gutter of the editor + File heatmap annotations at the bottom of README.md with the gutter and line locations enabled: the gutter stripe and a faint line tint are colored by the age of each line's last change — the two recently edited lines at the bottom in hot red, the older lines above them in cool purple — and the older lines' text is faded
Visualize how recently each line was modified
@@ -416,7 +416,7 @@ You can also apply Cloud Patches directly from a shared URL. Simply click or pas To delete a Cloud Patch, right-click it and choose **Delete Cloud Patch...**.
- Delete option in GitLens Cloud Patch view + Cloud Patches view in the GitLens sidebar showing a right-click context menu with Delete Cloud Patch option on a patch entry
Remove unused patches with one click
@@ -429,12 +429,16 @@ Learn how to configure this in our [Self-Hosting Guide](/gk-dev/gk-dev-home/#sel *** -## Commit Graph `PRO` +## Commit Graph -The Commit Graph helps visualize your repository's commit history by displaying branches, commits, and contributors in a unified view. This makes it easier to understand project activity and make informed decisions quickly. +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 contributors 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.
- Commit Graph in GitLens showing branches and commits + Commit Graph in GitLens showing branches and commits
Explore your full Git history at a glance
@@ -442,15 +446,13 @@ The Commit Graph helps visualize your repository's commit history by displaying ### How to Open the Commit Graph -To open the Commit Graph: +The Commit Graph opens automatically when you click the GitLens icon in the Activity Bar. You can also open it from the Command Palette: 1. Open the Command Palette: Cmd/Ctrl + Shift + P 2. Type: - `Show Commit Graph` - -A new tab will open, displaying your current repository’s commit history. You can scroll through the graph and resize column widths for easier viewing. + `GitLens: Show Commit Graph`
Using the Command Palette to open the GitLens Commit Graph @@ -463,9 +465,9 @@ A new tab will open, displaying your current repository’s commit history. You At the top of the graph, you’ll see: -- **Repository name** +- **Repository** — the hosting provider's icon (hover it for the repository name; the editor tab is titled *Commit Graph: <repository>*) - **Checked-out branch** -- **Last fetched timestamp** +- **Last fetched time** — beside **Fetch** and in its hover From here, you can: @@ -473,13 +475,13 @@ From here, you can: - Click **Fetch** to update commit data
- Commit Graph header with repo name, branch, and fetch option + The top of the Commit Graph in the editor area: the tab reads "Commit Graph: Playground2026", the header shows the current branch (main) with Push and "Fetch (1wk ago)" buttons, and the Fetch button's hover popover lists the upstream (origin/main on GitHub), "Last fetched last week" and the Auto-fetch option
Access key branch controls directly from the header
-

Note: The Commit Graph is available to all users on public or local repositories without needing an account.

- Private repository access requires a GitLens Pro subscription or trial.

+

Note: The Commit Graph is included in GitLens Community and available to all users on public or local repositories, without needing an account.

+ Only private repository access requires a GitLens Pro subscription or trial.

We welcome your input—join the discussion on GitHub.

@@ -495,10 +497,10 @@ All columns in the Commit Graph are fully customizable: - Drag and drop column headers to rearrange the layout. - Right-click a column header to toggle columns on or off. -- The **Changes** column displays visual indicators for added (green) and deleted (red) lines in each commit. +- 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 customization context menu in Commit Graph + Commit Graph settings menu showing options to hide the Author, Date, SHA, Changes, and other columns, switch the graph layout, and use a compact layout
Customize visible columns with right-click options
@@ -508,18 +510,18 @@ All columns in the Commit Graph are fully customizable: You can choose where the Commit Graph appears: -- **Panel Layout** — displays the graph in the bottom panel (next to Terminal) with a dedicated Commit Graph Details view. +- **Panel Layout** — displays the graph in the bottom panel (next to Terminal) with the embedded details panel. - **Editor Area Layout** — shows the graph in a standard VS Code editor tab. To switch layouts: -1. Click the gear icon in the top-right of the Commit Graph. -2. Select **Prefer Commit Graph in Panel Layout** or **Prefer Commit Graph in Editor Area**. +1. Open the **More Actions…** (⋯) menu in the top-right of the Commit Graph editor tab (or of the Commit Graph view in the side bar). +2. Select **Prefer Commit Graph in Editor** or **Prefer Commit Graph as a View**. You can even open both layouts simultaneously.
- Layout settings for Commit Graph + The Commit Graph open in the editor area with the tab's More Actions (…) menu expanded, listing Prefer Commit Graph in Editor and Prefer Commit Graph as a View among the editor actions
Choose where the graph displays: Panel or Editor
@@ -529,14 +531,14 @@ You can even open both layouts simultaneously. For smaller screens or simplified views: -- **Compact Graph Column Layout** reduces the visual size of the graph. +- **Use Compact Graph Column** reduces the visual size of the graph. - The **Author** column shows avatars when minimized. - Columns display icons instead of truncated text when resized to narrow widths. -To enable the compact graph layout, right-click the **Graph** column header and select **Compact Graph Column Layout**. +To enable the compact graph layout, select the gear in the **Graph** column header and choose **Use Compact Graph Column**.
- Compact layout in Commit Graph + Compact Commit Graph layout toggle showing the graph switching from normal to compact view with icons and avatars
Enable compact mode for cleaner visuals
@@ -571,7 +573,7 @@ You can adjust Commit Graph preferences through the GitLens Settings panel. `GitLens: Open Settings`
- Commit Graph settings in GitLens + VS Code Command Palette filtered to "GitLens: Settings" with the GitLens: Open Settings command highlighted, the step that opens the GitLens settings for the Commit Graph
Access GitLens settings from the Command Palette
@@ -581,6 +583,12 @@ You can adjust Commit Graph preferences through the GitLens Settings panel. The Commit Graph includes a powerful search bar to locate commits by message, author, file, or even specific code changes. +#### Natural Language Search `PRO` + +You can type plain-language queries (e.g., "changes to the login page last week") and GitKraken AI converts them into structured Git search operators automatically. Natural language search works in the Commit Graph search bar, the Search & Compare view, and the Search Commits command. + +#### Search Prefixes + Use the following search prefixes: - `Commit:` @@ -589,9 +597,10 @@ Use the following search prefixes: - `File:` - `Change:` - `@me` (to filter commits made by your user) +- Time-based operators such as `after:` and `before:` to scope results by date
- Search bar filtering commit history in the Commit Graph + Commit Graph search bar highlighting results
Search commit history with advanced filtering
@@ -602,7 +611,7 @@ Use keyboard shortcuts to navigate results: - Hold Shift and click arrows to jump to first or last match
- Navigating through commit search results + Navigating commit search results with arrow keys in the Commit Graph, showing the selection jumping between matching commits
Jump through results using keyboard or search controls
@@ -613,7 +622,7 @@ You can also refine results with: - **Regular expression**
- Commit Graph search filter toggles + Commit Graph search box with the query "fix" and a ring around the search option toggles at its right end: Match Case, Match Whole Word, Use Regular Expression and Match All, next to the 1 of 6 result counter
Adjust search filters for more precision
@@ -632,6 +641,40 @@ Popular options include: - **Compare with Common Base** — View changes between the current and selected branches based on their shared ancestor. - **Open All Changes with Common Base** — Launch a multi-diff view showing all changes that would be merged. +- **Squash**, **Drop**, **Reword**, and **Modify Commits** — Run interactive rebase operations directly from the graph without opening the Rebase Editor. Select one or more commits, right-click, and choose the desired operation. +- **Undo Commit** — Appears as an inline action on the HEAD commit row to soft-reset the latest commit. +- **Push to Commit** — Appears as an inline action on unpushed commit rows to push up to that specific commit. + +--- + +### Compare Mode `PRO` + +Compare mode lets you view comparisons directly inside the Commit Graph rather than switching to the Search & Compare view. Select two references to see Ahead, Behind, and All views inline within the graph details panel. + +--- + +### Compose Mode `PRO` + +Compose mode integrates commit composition directly within the Commit Graph. Select the Working Changes row to see your uncommitted work, then switch to Compose mode in the details panel to create commits from those changes or to reorganize branch history. GitKraken AI can propose the commits and messages for you to review and refine before applying them. + +
+ Commit Graph in Compose mode: the ringed Compose (wand) action on the Working Changes row, and the composer panel beside the graph listing Staged changes and Unstaged changes entries, the changed files, and the Instructions box with the Compose button +
Compose mode in the Commit Graph details panel
+
+ +Click the **Compose** button to generate an AI-assisted commit message based on your staged changes, or write your own message manually. + +
+ Commit Graph composer with AI-generated commit message ready for review +
AI-generated commit message populated in the composer
+
+ +--- + +### Multi-File Selection + +The Commit Graph and Inspect panels support multi-file selection using Shift-click and Ctrl/Cmd-click in Working Changes, commit details, compare, compose, and review file lists. Selected files can be batch-operated on with stage, unstage, discard, and stash actions. Inline per-file action buttons are also available for individual operations. + ### Pull Request Indicators For GitHub and GitLab, GitLens displays a **Pull Request icon** on branches with active pull requests. To enable this: @@ -640,7 +683,7 @@ For GitHub and GitLab, GitLens displays a **Pull Request icon** on branches with 2. The icon will appear next to branches in the graph once linked.
- Pull request icon displayed in Commit Graph + The Commit Graph with the fixture/code-suggest-demo branch pill ringed: after the branch name and its origin remote the pill carries the pull-request icon, which marks the branch as having an associated open pull request
Active pull requests are shown with branch-level icons
@@ -650,11 +693,11 @@ For GitHub and GitLab, GitLens displays a **Pull Request icon** on branches with You can hide individual remotes, branches, or tags from the Commit Graph to reduce clutter and focus your view. -- **To hide**: Hover over any ref and click **Hide**. +- **To hide**: 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 scope/filter popover next to the search box. - **To show again**: Use the **Hide** panel at the top of the graph and reselect the ref.
- Hiding Git refs in the Commit Graph + Hiding a branch in the Commit Graph: right-clicking the conflict-branch ref opens its context menu, and choosing Hide Local Branch removes the ref from the graph
Use the “Hide” option to declutter the graph
@@ -662,8 +705,9 @@ You can hide individual remotes, branches, or tags from the Commit Graph to redu You can further control what is shown using the filter dropdown: -- **Show Current Branch Only** — Display the current branch and its upstream (minimal view) -- **Show All Local Branches** — Default view showing all local refs +- **All Branches** — Display all branches +- **Current Branch** — Display the current branch and its upstream (minimal view) +- **Smart Branches** — Display only the relevant branches: the current branch, its upstream, and its base or target branch - Toggle visibility of: - Remote-only branches - Tags @@ -671,7 +715,7 @@ You can further control what is shown using the filter dropdown: - Option to **dim merge commits**
- Commit Graph filter options + Commit Graph filter options
Customize your view with filter presets
@@ -692,7 +736,7 @@ The **Minimap** gives you a visual summary of repository activity at a glance: #### Minimap Settings -Customize the Minimap via the **graph icon dropdown**: +Customize the Minimap via the **gear at the right end of the minimap**: - Toggle between: - **Commits view** @@ -701,7 +745,7 @@ Customize the Minimap via the **graph icon dropdown**: - Markers for branches, tags, stashes, search results
- Minimap settings in Commit Graph + Commit Graph with the minimap strip above the rows and its Minimap Options popover open: a Minimap group with Commits (selected), Lines Changed and Reverse Direction, and a Markers group with checkboxes for Local Branches, Remote Branches, Pull Requests, Stashes, Tags and Worktrees
Choose your preferred Minimap display and markers
@@ -784,6 +828,14 @@ You can also start or review [Code Suggestions](/gitlens/gitlens-features/#code- --- +### Start Review `PRO` + +The **Start Review** command (`gitlens.startReview`) provides a guided wizard for beginning a pull request review. It walks you through selecting a PR from your connected integration, choosing whether to check out the branch or create a worktree, and optionally launching an AI chat pre-filled with a review prompt. + +Access it from the Command Palette: `GitLens: Start Review` + +--- + ### Pin or Snooze PRs Use the pin icon to keep important PRs in the **Pinned** group. @@ -808,16 +860,23 @@ Click the icon again to unpin or unsnooze as needed. *** -## Visual File History +## Visual History + +Visual History (formerly Visual File History) provides a clear timeline of changes—showing when, what, and who modified your code—helping you quickly understand how a file, folder, repository, or branch evolved. -Visual File History provides a clear timeline of a file's changes—showing when, what, and who modified it—helping you quickly understand how a file evolved. +Visual History supports multiple scopes: -To open Visual File History: +- **File** — View the history of a single file +- **Folder** — View the history of a directory +- **Repository** — View the history of the entire repository +- **Branch** — Slice the history by branch to focus on specific lines of work + +To open Visual History: - Use the GitLens **Inspect Sidebar**, or -- From the **Command Palette**: `Cmd/Ctrl + Shift + P` → `GitLens: Show Visual File History View` +- From the **Command Palette**: `Cmd/Ctrl + Shift + P` → `GitLens: Show Visual History View`
- Visual File History overview + Visual History view for CHANGELOG.md showing eight commits by four authors plotted as colour-coded bubbles over the last four weeks, with the additions and deletions of each commit shown as bars
Track authorship, size, and timing of file changes
@@ -838,7 +897,7 @@ Hover over a bubble or bar for detailed insights.
-

The Community plan supports Visual File History only on public and local repositories.

+

The Community plan supports Visual History only on public and local repositories.

@@ -855,20 +914,18 @@ GitKraken AI enhances your development workflow with automated commit messages, Automatically generate descriptive commit messages based on staged changes.
- Generating AI commit messages + The Source Control view with a staged file: the empty commit message box, then an AI-generated commit message appearing in it
AI-generated commit messages from staged changes
To use: - Stage your changes. -- Open the **Commit Graph** and click **Generate Commit Message**, or -- Use the Command Palette: `GitLens: Generate Commit Message (Experimental)` +- In the Source Control view, open the GitLens sparkle menu in the Changes header and choose **Generate Commit Message**, or +- Use the Command Palette: `GitLens: Generate Commit Message` GitKraken AI will analyze the diff of staged changes to generate a message. You may provide additional context in the commit box to improve results. -You can customize behavior using: -- `gitlens.experimental.generateCommitMessagePrompt` for message formatting -- Additional [`gitlens.ai` settings](/gitlens/gitlens-settings/#misc-settings) for provider and model preferences +You can customize behavior using [`gitlens.ai` settings](/gitlens/gitlens-settings/#misc-settings) for provider, model, and prompt preferences.

Pro users and above can optionally use a custom API key to connect to a different AI provider. GitKraken AI currently uses the Google Gemini model.

@@ -898,17 +955,20 @@ Let GitKraken AI help explain complex changes across your repo with natural lang
AI summaries in rendered markdown for improved clarity
-✨**Explain** functionality provides markdown summaries for: -- Branches — ✨**Explain Branch** -- Working changes — ✨**Explain Working Changes** -- Stashes — ✨**Explain Stash** +Standalone **Explain** commands provide markdown summaries for: +- Commits — **Explain Commit** +- Branches — **Explain Branch** +- Working changes — **Explain Working Changes** +- Stashes — **Explain Stash** **Where to find it:** - Commit Graph - Command Palette - GitLens views: Commits, Branches, Stashes, Search & Compare +- Editor blame hovers (sparkle Explain button) With GitKraken AI explanations, you can quickly understand: +- The purpose and impact of individual commits - What changed across all commits in a branch - What you've modified in your working directory - What your previous stashes contain @@ -940,14 +1000,37 @@ Automatically generate detailed and structured changelogs from a set of selected

More questions about GitKraken AI? See the GitKraken AI FAQ for additional details.

-### Commit Composer View `Pro` -The Commit Composer has evolved from a simple one-step process into a comprehensive drafting and review experience. Previously, AI would analyze your changes and immediately create commits. Now, the new Commit Composer view gives you complete control over the composition process, with options to auto-compose with AI or compose manually. +### AI Generate Commits `PRO` -*This feature is available through the [Gitkraken MCP](https://help.gitkraken.com/mcp/mcp-tools-reference/)* +Generate well-structured commits from your working tree changes using AI analysis. The **Generate Commits** command analyzes your staged and unstaged changes, groups them logically, and creates commits with descriptive messages. A first-time confirmation dialog explains what the command will do, and an **Undo** button is available after generation to revert if needed. + +### AI Rebase `PRO` + +The **AI Rebase** command restructures commits on an existing branch onto a target commit using AI-generated commit grouping and messages. Like Generate Commits, it includes an undo button and a first-time confirmation dialog. Both commands produce markdown explanation documents summarizing the changes made. + +### AI Auto Rebase `PRO` + +AI Auto Rebase (`gitlens.ai.autoRebase`) carries a rebase forward through the conflicts GitKraken AI can resolve confidently, and hands the rest back to you. When a rebase encounters a conflict, AI analyzes it and resolves it only when its confidence meets the threshold you set; anything below that threshold pauses the rebase so you can resolve the conflict yourself and continue. Every run is reviewable and reversible. + +Key capabilities: + +- **Confidence threshold** — Configure `gitlens.ai.autoRebase.confidenceThreshold` (0 to 1) to control how confident the AI must be before resolving a conflict on its own. Raise it to keep more decisions in your hands. +- **Stops rather than guesses** — Conflicts that fall below the threshold are left for you to resolve manually, with the rebase paused at that point. +- **Custom instructions** — Use `gitlens.ai.resolveConflicts.customInstructions` to provide project-specific guidance for conflict resolution +- **Rebase summary sheet** — After the rebase completes, a summary sheet shows what was resolved and how, so you can review each decision +- **Full undo support** — Undo the entire auto-rebase with `gitlens.ai.autoRebase.undo` to return to the pre-rebase state if the results are not what you wanted + +Access it from the Commit Graph context menu or the Command Palette: `GitLens: AI Auto Rebase` + +### Commit Composer View `Pro` +The Commit Composer has evolved from a simple one-step process into a comprehensive drafting and review experience. Previously, AI would analyze your changes and immediately create commits. Now, the Commit Composer gives you complete control over the composition process, with options to auto-compose with AI or compose manually. It is integrated directly into the Commit Graph details panel as Compose mode, and is also available as a standalone view. Join the [Commit Composer discussion](https://github.com/gitkraken/vscode-gitlens/discussions/4530) and provide feedback. - +
+ Commit Graph in Compose mode: the ringed Compose (wand) action on the Working Changes row, and the composer panel beside the graph listing Staged changes and Unstaged changes entries, the changed files, and the Instructions box with the Compose button +
The Commit Composer drafting view
+
#### Interactive Draft Commits @@ -959,18 +1042,28 @@ When composing commits, GitLens now creates "draft" commits that you can review, - **Iterate and refine**: Regenerate individual messages or entire commit compositions - **Review and edit**: Manually tweak any commit message or approach - +
+ Commit Composer with AI-composed commit message populated and ready for review +
AI-composed commit message ready for review
+
You can launch the new Commit Composer view from several places in GitLens: - **GitLens commit details view** -- **Context menu on the WIP row** in the GitLens Commit Graph +- **Context menu on the Working Changes row** in the GitLens Commit Graph - **Commit Graph details panel**: Switch to **Compose** mode - **✨ icon in the SCM view header** - **Command palette**: Search for "Compose Commits" - - +
+ Commit Graph toolbar showing the Compose button entry point +
Access Commit Composer from the graph toolbar
+
+ +
+ The Commit Graph's Working Changes details panel with the Compose and Review mode chips ringed in its header, above the branch row, the four changed files and the commit-message box +
Or switch to Compose mode in the Working Changes details panel
+
The foundation is now in place for even more powerful composition features in future releases, including intuitive drag-and-drop functionality for moving lines and hunks between commits, creating new draft commits on the fly, and reordering commit sequences. @@ -980,7 +1073,10 @@ Whether you prefer to let AI handle the heavy lifting or want granular control o Commit Composer now lets you clean up and reorganize commits on existing branches, making it perfect for preparing pull requests or refining your commit history before pushing. - +
+ The Commit Composer opened for the feature/spending-insights branch: its four commits sit in the scope list with drag handles, main's commits are dimmed beneath them above the base, the three changed files are listed, and the Instructions box with the Compose button waits at the bottom +
Recompose an entire branch from the Commit Graph
+
#### Recompose Entire Branches @@ -1004,21 +1100,41 @@ Commit Composer now handles edge cases that previously blocked composition: Commit Composer now lets you recompose specific commits within a branch, giving you precise control over cleaning up your commit history. - +
+ The Commit Composer scoped to two selected commits of the feature/spending-insights branch — "fix(insights): exclude refunds from spending totals" and "feat(insights): add budget threshold alerts" — shown in the scope list with drag handles while the branch's other commits are dimmed, above the changed files and the Compose instructions box +
Select specific commits to recompose
+
Previously, you could only recompose all working changes or an entire branch. Now you can select specific commits that need refinement—like those quick "wip" or "fix" commits made during rapid iteration—and let AI restructure just those changes with better messages. Select multiple contiguous commits on the same branch using Shift or Cmd click, then right-click and choose "Recompose Selected Commits." Commit Composer opens with only your selected commits as drafts, ready for AI-powered or manual refinement. -Commit Composer is also more discoverable, with a new button on the WIP row in the Commit Graph that opens the composer for all working directory changes. Additionally, when rebasing, you can now switch directly into Commit Composer from the Rebase Editor, canceling your rebase to let AI handle the composition instead. +Commit Composer is also more discoverable, with a new wand button on the Working Changes row in the Commit Graph that opens the composer for all working directory changes. Additionally, when rebasing, you can now switch directly into Commit Composer from the Rebase Editor, canceling your rebase to let AI handle the composition instead. + +
+ The Working Changes row at the top of the Commit Graph with its row actions at the right: the wand button that opens Commit Composer for all working directory changes is ringed +
Open Commit Composer from the Working Changes row
+
+ +### Compose and Recompose Commands + +Commit Composer can also be launched via dedicated commands: - +- **Compose Commits** (`gitlens.compose`) — Opens the Commit Composer for working changes in the current repository, or from a Compose mode entry in the Commit Graph details panel. +- **Recompose Branch** (`gitlens.recomposeBranch`) — Opens the Commit Composer scoped to an entire branch. GitKraken AI can propose a clearer, more intentional sequence of commits and messages for you to review and refine before applying the result. +- **Recompose from Commit** (`gitlens.recomposeFromCommit`) — Scopes the same workflow to a specific commit onward. +- **Recompose Selected Commits** (`gitlens.recomposeSelectedCommits`) — Scopes the same workflow to only the selected commits on a branch. + +These commands are available from the Commit Graph context menu, branch context menus throughout GitLens, and the Command Palette. Coach marks guide first-time users through the workflow. *** ## Git Command Palette - +
+ GitLens Git Command Palette showing guided step-by-step command options +
Guided Git commands through the Command Palette
+
Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Command Palette (`gitlens.gitCommands`) for guided, step-by-step access to many common Git commands. Quickly navigate Git actions, explore commit history, manage stashes, and more—all through intuitive, confirmable menus. @@ -1031,9 +1147,9 @@ Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Comma - **Show Current Branch History** (`gitlens.showQuickRepoHistory`): View the commit history of your current branch. -- **Show File History** (`gitlens.showQuickFileHistory`): Access the full commit history of the current file. +- **Show File History** (`gitlens.showQuickFileHistory`): Access the full commit history of the current file. The File History view supports a **contributors mode** (`gitlens.views.fileHistory.mode`) that shows all contributors to the file instead of the commit list. - + File History QuickPick for README.md listing its six commits with message, author, date, SHA and line-change counts; the newest commit is highlighted - **Search Commits** (`gitlens.showCommitSearch`): Use a quick pick menu to search by: @@ -1043,13 +1159,13 @@ Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Comma - File path or glob: `:` - Patch changes: `~` - + Commit Search QuickPick showing the search mode options, including Search by Message, Author, Commit ID, File, and Changes, with their usage patterns Refer to the [Git log documentation](https://git-scm.com/docs/git-log) for advanced usage. - **Show Commit Details** (`gitlens.showQuickCommitDetails`): Review commit information and actions. - + Commit Details QuickPick showing the commit message, author, SHA, and changed-file count, with actions including Revert, Reset, Create Branch, and Create Tag - **Show Line Commit Details** (`gitlens.showQuickCommitFileDetails`): Explore the file's commit and take action on it. @@ -1059,11 +1175,11 @@ Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Comma ### Quick Stash Access
- + Stash list QuickPick showing all stash entries in the repository with stash messages and selection options
- + Stash details QuickPick for stash #0 showing its files-changed summary and the Apply Stash, Rename Stash, Drop Stash, Copy Message, Open, Compare and Browse Repository actions
- Adds a _Show Stashes_ command (`gitlens.showQuickStashList`) to show a quick pick menu to explore your stashes. @@ -1083,13 +1199,32 @@ Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Comma ## Interactive Rebase Editor
- + GitLens interactive rebase editor: five commits each with an action dropdown, the second entry's dropdown open on pick / reword / edit / squash / fixup / drop, and then squash applied to it; the footer lists the keyboard shortcuts including alt + up/down to move a commit
Adds a user-friendly interactive rebase editor to easily configure an interactive rebase session: - Quickly re-order, edit, squash, and drop commits. - Includes drag & drop support. +- Toolbar commands for **Abort**, **Continue**, **Reopen as Interactive Editor**, and **Reopen as Text Editor**. + +### Conflict Detection + +The rebase editor includes a **conflict files panel** that displays files with potential conflicts along with per-file conflict counts and status indicators. **Predictive conflict detection** warns about upcoming conflicts against the current base before you start the rebase, helping you prepare for issues in advance. + +### Rebase Editor Settings + +The rebase editor offers several configuration options: + +- `gitlens.rebaseEditor.openOnPausedRebase` — Automatically open the rebase editor when a rebase is paused (e.g., due to conflicts). +- `gitlens.rebaseEditor.openBehavior` — Controls how the rebase editor opens: `auto` (default) or `beside` (opens alongside the current editor). +- `gitlens.rebaseEditor.revealLocation` — Where to reveal commit details: `graph` or `inspect`. +- `gitlens.rebaseEditor.revealBehavior` — When to reveal details: `never`, `onOpen`, or `onSelection`. +- `gitlens.rebaseEditor.density` — Controls row padding in the editor: `compact` (default) or `comfortable` for more spacing. + +### Conflict Resolution Actions + +When a rebase is paused due to conflicts, the rebase editor provides inline actions to **stage current changes** or **stage incoming changes** directly, streamlining the conflict resolution workflow. ### To use this directly from your terminal (e.g., when running `git rebase -i`): @@ -1106,6 +1241,29 @@ Adds a user-friendly interactive rebase editor to easily configure an interactiv > To use the Insiders edition of VS Code, replace `code` with `code-insiders` in the commands above. +*** + +## Commit Signature Verification `PRO` + +GitLens verifies commit signatures using GPG, SSH, and X.509 certificates, displaying verification badges directly in the Commit Details view, Graph Details panel, and inline blame hovers. + +### Verification Badges + +Each signed commit shows a badge indicating its verification status: + +- **Verified** — The signature is valid and the signer is trusted +- **Unverified** — The signature could not be verified (missing key, untrusted signer, etc.) +- **Unsigned** — The commit has no signature + +The `${signature}` token is available in commit tooltip format strings to display signature status in custom tooltip layouts. + +### Allowed Signers Management + +The **Allowed Signers** webview (`gitlens.allowedSigners`) provides a dedicated panel for managing SSH trusted signers. It scans recent commits for SSH signatures, discovers candidate signers with their avatars, and lets you select which keys to trust. Trusted entries are saved to your SSH `allowed_signers` file. + +Access it from the Command Palette: `GitLens: Manage Allowed Signers` + + *** ## Autolinks @@ -1113,14 +1271,14 @@ Adds a user-friendly interactive rebase editor to easily configure an interactiv Use autolinks to convert external references—such as Jira issues or Zendesk tickets—into clickable links directly from commit messages.
- + Commit details in the GitLens Inspect view for a commit whose message ends in "Closes #7": the #7 reference is a link, and the Autolinks section below the message shows the #7 chip with its hover popover naming the open pull request "fix: add types and config to rate limiter"
Example of autolinks in commit messages
## Terminal Links
- + The integrated terminal showing git log --oneline output, with the pointer on the first commit's SHA: GitLens underlines it as a link and shows the "Show Commit (ctrl + click)" hover
Autolinks in the integrated terminal
@@ -1145,6 +1303,7 @@ Basic integrations offer issue and pull request autolinking. Richer integrations These integrations also support various commands to open or copy URLs for files, commits, branches, and repositories: - **Open File from Remote** (`gitlens.openFileFromRemote`) — Open a local file from a URL on a remote provider +- **Open Revision from Remote** (`gitlens.openRevisionFromRemote`) — Open the specific file revision referenced by a remote URL, rather than the working copy - **Open File on Remote** (`gitlens.openFileOnRemote`) — Open a file or revision on the remote provider - **Copy Remote File URL** (`gitlens.copyRemoteFileUrlToClipboard`) — Copy the URL of a file or revision - **Open File on Remote From...** (`gitlens.openFileOnRemoteFrom`) — Open a file or revision from a specific branch or tag @@ -1170,11 +1329,11 @@ To connect an integration: 1. Open the Command Palette (`Cmd`/`Ctrl`+`Shift`+`P`). 2. Run `GitLens: Manage Integrations`. -3. Alternatively, open **GitKraken Account** from the GitLens Activity Bar and select **Integrations**. +3. Alternatively, in the GitLens **Home** view, select the integrations chip in the header to open the **Integrations** popover, then its gear (**Manage Integrations**).
- -
Connect integrations from the GitKraken dashboard
+ The GitLens Home view with the Integrations popover open from the header's integrations chip: a list of providers — GitHub, GitLab, Azure DevOps, Bitbucket, Jira, Linear — each with what it supports and a connected check mark, a Show: All | Connected filter, and the Manage Integrations gear ringed in the popover header +
Open the Integrations popover from the Home view header
If you're not already signed in, you'll be prompted to log in to your GitKraken account. Then, select **Connect with GitHub** or **Connect with GitLab**, and follow the sign-in steps. You can connect multiple integrations if needed. @@ -1198,7 +1357,7 @@ GitLens Pro offers a richer integration with GitHub Enterprise Server and GitLab Once authenticated, GitLens enhances autolinks in hovers with additional context. You’ll see your GitHub Enterprise Server or GitLab Self-Managed avatar, links to related pull requests, and a summary of pull request or issue details. Sidebar views for commits or branches also show this contextual information.
- + The Commit Graph with the pull-request hover card open over the #7 badge of the fixture/code-suggest-demo branch pill: the pull request's title "fix: add types and config to rate limiter", its number, who opened it and when it was last updated — metadata supplied by the connected GitHub integration
Enhanced hover integration with GitHub Enterprise and GitLab Self-Managed
@@ -1227,7 +1386,7 @@ Or - If this option is missing, verify the format in your `settings.json` matches the example above.
- + GitLens Remotes sidebar view listing repository remotes with the Connect to Remote action icon for linking a self-hosted provider
Connect to a GitHub Enterprise or GitLab Self-Managed instance
@@ -1252,14 +1411,14 @@ The Jira Integration, connected through your GitKraken Account, enables Jira [Au To connect the integration: -1. Open the GitLens Sidebar. -2. From the GitKraken Account view, select **Cloud Integrations**. +1. Open the GitLens Settings editor (run _GitLens: Open Settings_ from the Command Palette). +2. Select **Cloud Integrations** under **Integrations** in the navigation rail. 3. Choose **Jira Cloud**, and authorize access to your Atlassian Account. 4. Alternatively, visit your [Integration Settings](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens) in a browser.
- -
Connect Jira from GitKraken Cloud Integrations
+ GitLens Settings Cloud Integrations category showing provider connection cards for GitHub, GitLab, Azure DevOps, Bitbucket, Jira, and Linear +
Cloud Integrations category in the GitLens Settings editor
@@ -1291,6 +1450,9 @@ GitLens provides powerful commands to improve your workflow: - **Disable Debug Logging** (`gitlens.disableDebugLogging`) — Disable debug logging. - **Copy as Patch** (`gitlens.copyPatchToClipboard`) — Copy patch data from views, changes, or stashes. - **Apply Copied Patch** (`gitlens.applyPatchFromClipboard`) — Apply a patch from clipboard contents. +- **Change Branch Merge Target** (`gitlens.changeBranchMergeTarget`) — A multi-step wizard to set or reset a branch's merge target. Pick a local branch, then select a remote branch as its merge target, or reset an existing target. +- **Copy Changes to Worktree** (`gitlens.worktree.copyChanges`) — Copy working changes from one worktree to another. +- **Unlock Worktree** (`gitlens.worktree.unlock`) — Unlock a locked worktree from the tree view context menu. *** @@ -1312,10 +1474,68 @@ Deep Links are URLs that open specific GitLens resources, improving collaboratio *** +## Git Submodule Support + +GitLens provides basic support for Git submodules. Submodule repositories are automatically discovered and tracked when you open a project that contains them. In the sidebar views, submodule repositories are distinguished with dedicated icons and tooltips. Submodule changes are handled in diffs so you can see when a submodule reference has been updated. + +*** + +## Welcome View + +The **Welcome** sidebar view provides a guided multi-step walkthrough for new and returning users. It covers getting started with GitLens, the Home view, the Commit Graph, AI features, Git Blame, PR reviews, and MCP agent integration. The walkthrough content adapts based on your subscription level. + +Access it from the GitLens sidebar — the Welcome view appears at the top of the sidebar panel. + +*** + +## AI Agent Integration `PRO` + +GitLens integrates with AI coding agents to monitor their activity and coordinate their work alongside your own development workflow. + +### Supported Agents + +Agent integration supports multiple AI agents: + +- Claude Code +- OpenAI Codex +- GitHub Copilot +- Google Gemini +- OpenCode + +### Agent Hooks + +GitLens can install hooks for AI agents so their activity is tracked within your repository. Use the following commands: + +- **Install Agent Hooks** (`gitlens.installHooks`) — Install hooks for all detected agents +- **Install Hooks for Agent** (`gitlens.installHooksForAgent`) — Install hooks for a specific agent +- **Uninstall Agent Hooks** (`gitlens.uninstallHooks`) — Remove hooks for all agents +- **Uninstall Hooks for Agent** (`gitlens.uninstallHooksForAgent`) — Remove hooks for a specific agent + +### Agent Sessions + +When hooks are active, GitLens tracks agent sessions and displays status indicators: + +- **Agent session cards** appear in the Home view showing active and recent sessions +- **Status pills** on branches in the Commit Graph indicate which branches have active agent sessions +- **Resume Session** (`gitlens.resumeSession`) and **Archive Session** (`gitlens.archiveSession`) commands manage session lifecycle + +### MCP Server Management + +GitLens manages the GitKraken MCP server installation on a per-agent basis. The **Connect Agents** flow walks you through installing the CLI, registering MCP for your current IDE, and connecting additional agents. + +- **Connect Agents** (`gitlens.mcp.connectAgents`) — Interactive flow to install and configure MCP for your agents +- **Install MCP for All Agents** (`gitlens.mcp.installForAllAgents`) — Install the GitKraken MCP server for all detected agents +- **Install MCP for Agent** (`gitlens.mcp.installForAgent`) — Install for a specific agent +- **Uninstall MCP for Agent** (`gitlens.mcp.uninstallForAgent`) — Remove MCP from a specific agent + +The agent settings panel provides a centralized view for managing agent configurations. + +*** + ## Menus & Toolbars
- + GitLens Visual Settings Editor showing the Menus and Toolbars category, with toggle options controlling where GitLens commands appear in editor menus, context menus, and toolbars
GitLens menu and toolbar options
@@ -1324,7 +1544,7 @@ GitLens provides [customizable](/gitlens/gitlens-settings/#elementor-toc__headin For example, disabling **Add to the editor group toolbar** removes those items from the toolbar:
- + VS Code editor tab bar with the GitLens editor group toolbar items removed, showing a toolbar without GitLens action buttons
Editor group toolbar items removed
diff --git a/gitlens/gitlens-settings.md b/gitlens/gitlens-settings.md index 0830762..124b8e8 100644 --- a/gitlens/gitlens-settings.md +++ b/gitlens/gitlens-settings.md @@ -4,20 +4,104 @@ description: Learn how to access and customize GitLens settings in Visual Studio taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026 ## Overview +GitLens is highly customizable. Nearly every feature can be tailored through the built-in **Visual Settings Editor** or by editing `settings.json` directly. + +To open the editor, run _GitLens: Open Settings_ (`gitlens.showSettingsPage`) from the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette). + +
+ GitLens Visual Settings Editor showing the Inline Blame category with toggle controls and format options +
The Visual Settings Editor — Inline Blame category
+
+ +The editor's navigation rail on the left lists **Account** and **Get Started** at the top, followed by four groups: **Integrations**, **Views**, **Editor**, and **General**. Each category shows its controls with live previews — changes apply immediately. A search bar at the top filters across all categories, and a **User / Workspace** scope toggle determines whether changes apply globally or to the current workspace. + +You can deep-link to any category by appending its anchor to the command: `gitlens.showSettingsPage!` (for example, `gitlens.showSettingsPage!ai` opens the AI category directly). + +### Setup + +The **Account** and **Get Started** entries at the top of the navigation rail cover account management and onboarding. +
- GitLens settings editor UI in Visual Studio Code -
GitLens interactive settings editor in VS Code
+ GitLens Settings with the Account category selected: the GitLens Pro plan header with its badge and the Synchronize Status, Manage Account and Sign Out buttons, the signed-in account and organization rows (masked here), a referral line and a Learn more link +
Account category
-GitLens offers a powerful and easy-to-use **interactive settings editor** that helps you configure many features directly in Visual Studio Code. +**Account** (`account`) — view your subscription status, manage your GitKraken account, and sign in or out. **Get Started** (`setup`) — onboarding steps for new users and feature discovery. -To open the editor, run the _GitLens: Open Settings_ command (`gitlens.showSettingsPage`) from the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette). +### Integrations + +Settings for AI, cloud integrations, and external service connections. + +
+ GitLens Settings AI category showing AI provider selection and model configuration +
AI category
+
+ +**AI** (`ai`) — choose your AI provider, configure models, and control AI-powered features like commit message generation and code explanations. **Agents** (`agents`) — configure AI agent behavior for automated code tasks. **Cloud Integrations** (`integrations`) — connect GitHub, GitLab, Bitbucket, Azure DevOps, and other hosting providers for pull request information, avatars, and deep links. + +
+ GitLens Settings Cloud Integrations category showing provider connection cards +
Cloud Integrations category
+
+ +**Custom Remotes** (`remotes`) — define URL patterns for self-hosted or non-standard remote providers. **Autolinks** (`autolinks`) — create patterns that automatically turn issue references (like `JIRA-123`) into clickable links. **Launchpad** (`launchpad`) — configure the Launchpad status bar indicator and notification behavior. **Terminal Links** (`terminal-links`) — control how git references in the integrated terminal become clickable links. + +### Editor + +Annotation and decoration settings for the code editor. + +
+ GitLens Settings Inline Blame category showing current line blame annotation options +
Inline Blame category — the default view
+
+ +**Inline Blame** (`current-line`) — configure the blame annotation shown at the end of the current line, including format, date style, and pull request information. **Git CodeLens** (`code-lens`) — toggle and format the authorship and change indicators above code blocks. **Status Bar Blame** (`status-bar`) — control the blame summary in the VS Code status bar. **Hovers** (`hovers`) — configure hover tooltips that appear over blame annotations and code, including details, changes, and pull request information. + +
+ GitLens Settings Hovers category showing hover annotation toggles +
Hovers category
+
+ +**File Blame** (`blame`) — gutter annotations showing per-line authorship across the entire file. **File Changes** (`changes`) — gutter indicators highlighting additions, deletions, and modifications relative to the previous commit. **File Heatmap** (`heatmap`) — color-coded gutter annotations showing the relative age of each line of code. + +### Views + +Configuration for Commit Graph and source control tree views. + +
+ GitLens Settings Commit Graph category showing graph layout options +
Commit Graph category
+
-GitLens is highly customizable—nearly every feature can be tailored to fit your workflow using the available settings. +**Commit Graph** (`commit-graph`) — layout, columns, minimap, scroll markers, details panel position, and graph style (table, list, or auto). This is a Pro feature. **GitLens SCM** (`scm-views`) — configure the Source Control Manager view integration. **Commits** (`commits-view`) — format templates for the Commits view (commit label, description, and tooltip formats; file and file description formats), with a link to the VS Code Settings UI for the view's remaining `gitlens.views.commits` settings. **Stashes** (`stashes-view`) — configure the Stashes view layout and display options. + +
+ GitLens Settings with the Commits view category selected in the Views group: format templates for the commit label, commit description, commit tooltip, file rows and file description, each with a token picker, and a footer link to the full gitlens.views.commits options in the VS Code Settings UI +
Commits view category
+
+ +> **Note:** In v19.0, ten view-specific settings categories (Repositories, Branches, Remotes, Tags, Worktrees, Contributors, File History, Line History, Search & Compare, and File Annotations) moved to VS Code's native settings. Configure them in `settings.json` or through _Preferences: Open Settings (UI)_ by searching for `gitlens.views`. + +### General + +Date formatting and UI customization. + +
+ GitLens Settings Dates and Times category showing date format options +
Dates & Times category
+
+ +**Dates & Times** (`dates`) — control absolute and relative date formatting across all GitLens surfaces. **Menus & Toolbars** (`menus`) — show or hide GitLens items in editor context menus, title bars, and toolbars. + +*** + +## Settings Reference + +The sections below document every `settings.json` parameter grouped by feature area. You can edit these directly in `settings.json` or use the Visual Settings Editor above. ## Current Line Blame Settings @@ -425,6 +509,10 @@ These settings control how the GitLens Commits view displays commit dat branch – compares current branch to another reference
working – compares working tree to a selected reference + +gitlens.views.commits.showSignatureVerification +Shows commit signature verification status in views. + @@ -525,6 +613,10 @@ These settings customize how repositories are displayed and interacted with in t gitlens.views.repositories.showUpstreamStatus Displays upstream tracking status of the current branch for each repository. + +gitlens.views.repositories.branches.compact +Flattens branch folders when using tree layout, combining single-child folders into a single entry. + @@ -552,6 +644,10 @@ These settings configure the behavior and display options for the GitLens Fi gitlens.advanced.fileHistoryShowMergeCommits Controls whether merge commits are shown in file history:

show – includes merge commits
hide – excludes merge commits + +gitlens.views.fileHistory.mode +Controls the display mode — commits shows commit history, contributors groups by contributor. + @@ -642,6 +738,10 @@ These settings configure the display and behavior of the GitLens Branchesfalse – hides comparisons
branch – compares the current branch with a selected reference + +gitlens.views.branches.compact +Flattens branch folders when using tree layout, combining single-child folders into a single entry. + @@ -708,6 +808,10 @@ These settings define how branches, files, and pull requests appear in the GitLe false – hides comparisons
branch – compares the current branch with a selected reference + +gitlens.views.remotes.compact +Flattens branch folders when using tree layout, combining single-child folders into a single entry. + *** @@ -793,6 +897,10 @@ These settings control how Git tags and related files appear in the GitLens gitlens.views.tags.reveal Determines whether tags are shown in the Tags view or revealed in the Repositories view. + +gitlens.views.tags.compact +Flattens branch folders when using tree layout, combining single-child folders into a single entry. + @@ -1150,6 +1258,55 @@ These settings control the display options for files and avatars in the GitLens gitlens.terminalLinks.enabled Enables terminal links—autolinks in the integrated terminal that provide quick access to details for commits, branches, tags, and more. + +gitlens.terminalLinks.showIn +Controls where terminal link references open.

+graph – opens in the Commit Graph
+inspect – opens in the Inspect view
+quickpick – opens in a quick pick menu + + + + +*** + +## Rebase Editor Settings + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
gitlens.rebaseEditor.openOnPausedRebaseControls whether the rebase editor auto-opens when a rebase is paused. The auto option only opens for rebases started within GitLens.

+true – always opens
+false – never opens
+auto – only opens for rebases started within GitLens
gitlens.rebaseEditor.revealLocationControls where the rebase editor opens.
gitlens.rebaseEditor.revealBehaviorControls how the rebase editor reveals itself.
gitlens.rebaseEditor.densityControls the visual density of commits in the rebase editor.

+compact – compact display
+comfortable – comfortable display with more spacing
gitlens.rebaseEditor.openBehaviorControls whether the rebase editor opens beside the current editor.

+auto – automatically determined
+beside – opens beside the current editor
@@ -1514,6 +1671,10 @@ Another custom example:
Specifies custom instructions to provide to the AI provider when generating a pull request title and description
+ +gitlens.ai.exclude.files +Glob patterns for files to exclude from AI context. Also respects .aiignore, .cursorignore, and .aiexclude files. + @@ -1547,7 +1708,7 @@ Another custom example:
gitlens.outputLevel -Controls the verbosity of output sent to the GitLens output channel. +Removed in v17.11 — This setting has been removed. Use the VS Code native output channel log level instead. gitlens.showWelcomeOnInstall @@ -1671,7 +1832,7 @@ Another custom example:
gitlens.visualHistory.allowMultiple -Allows opening multiple Visual File History instances in the editor area. +Allows opening multiple Visual History instances in the editor area. gitlens.liveshare.enabled @@ -1689,6 +1850,36 @@ Another custom example:
gitlens.experimental.cloudIntegrations.enabled Enables GitHub integration via GitKraken account cloud integration. + +gitlens.advanced.git.maxConcurrentProcesses +Maximum number of concurrent git processes, with priority-based queuing. + + +gitlens.defaultCurrentUserNameStyle +Controls how the current user's name is displayed across blame, hovers, views, and graph. + + +gitlens.advanced.gitTimeout +Timeout in milliseconds for git operations. + + +gitlens.advanced.resolveSymlinks +Resolves symbolic links before performing git operations. + + +gitlens.advanced.skipOnboarding +Skips the welcome walkthrough on new installations. + + +gitlens.sortWorkingChangesBy +Controls how working changes are sorted.

+stage – sorts by staging status
+flat – flat sort order + + +gitlens.visualHistory.editorOpeningBehavior +Controls how files open from the Visual History view. + @@ -1793,6 +1984,75 @@ Honored when opening the Commit Graph from the command palette. gitlens.graph.sidebar.enabled Shows or hides the sidebar in the Commit Graph. + +gitlens.graph.stickyTimeline +Pins the timeline panel to stay visible while scrolling the graph. + + +gitlens.graph.autoFetch.enabled +Enables periodic automatic git fetch in the Commit Graph. + + +gitlens.graph.details.location +Controls where the details panel appears relative to the graph.

+right – details panel on the right
+bottom – details panel on the bottom
+auto – automatically positioned + + +gitlens.graph.details.maximizeOnMode +Automatically maximizes the details panel when entering Compose or Review mode. + + +gitlens.graph.editorOpeningBehavior +Controls how files open from the graph (e.g., in the current editor group or beside it). + + +gitlens.graph.sidebar.pinned +Pins the graph sidebar to stay visible. + + +gitlens.graph.showWorktreeWipStats +Shows working tree change statistics on WIP rows. + + +gitlens.graph.minimap.reversed +Reverses the minimap direction. + + +gitlens.graph.minimap.defaultVisibility +Controls when the minimap is visible by default.

+hidden – minimap is hidden
+onSearch – minimap appears during search
+always – minimap is always visible + + +gitlens.graph.overviewBar.visibility +Controls visibility of the overview bar in the graph. + + +gitlens.graph.refFindAutoHide +Auto-hides the ref-finder widget after selection. + + +gitlens.graph.style +Controls the graph display style.

+table – table layout
+list – list layout
+auto – automatically selected + + +gitlens.graph.changesColumn.enabled +Shows or hides the Changes column in the graph. + + +gitlens.graph.changesColumn.mode +Controls how changes are visualized in the Changes column.

+numbers – shows numeric counts
+squares – shows colored squares
+bar – shows a bar indicator
+bipolar – shows a bipolar indicator + diff --git a/gitlens/gitlens-start-here.md b/gitlens/gitlens-start-here.md index 4407243..d1e788e 100644 --- a/gitlens/gitlens-start-here.md +++ b/gitlens/gitlens-start-here.md @@ -6,6 +6,9 @@ taxonomy: category: gitlens --- + +Last updated: September 2026 + --- Welcome to the GitLens Support Documentation site! @@ -34,7 +37,7 @@ Understanding code history can be difficult when looking at complex repositories #### Commit Graph -Once you have a repository open in VS Code, the Commit Graph gives you an interactive, action oriented visual of your commit and branch history. This allows you to follow your repository over time to see what is happening with branches and see why it was done with commit messages. You can quickly jump to any point in history by searching for either branches or commits. To view the commit graph, use the command palette (command/ctrl + shift + P) > _GitLens: Show Commit Graph View_ or select the _Show Commit Graph_ icon. +The Commit Graph is the main view in the GitLens sidebar and your starting point for working with GitLens. Once you have a repository open in VS Code, it gives you an interactive, action-oriented visual of your commit and branch history, powered by a high-performance rendering engine built for speed at scale. This allows you to follow your repository over time to see what is happening with branches and see why it was done with commit messages. You can quickly jump to any point in history by searching for either branches or commits. The Commit Graph opens automatically in the GitLens sidebar, or you can access it from the command palette (command/ctrl + shift + P) > _GitLens: Show Commit Graph View_. Open the Commit Graph in GitLens. diff --git a/gitlens/home-view.md b/gitlens/home-view.md index 1b68922..d3e4a2b 100644 --- a/gitlens/home-view.md +++ b/gitlens/home-view.md @@ -6,7 +6,7 @@ taxonomy: --- -Last updated: August 2026 +Last updated: September 2026 The Commit Graph is your starting point for working in GitLens. More than a visualization of repository history, it brings your repository state, working changes, branches, worktrees, and supported coding agent activity together in one connected workbench. From here, you can understand what’s happening across your repository, coordinate parallel work, review and shape changes, and move work toward merge without rebuilding context across disconnected views and tools. @@ -17,6 +17,10 @@ From here, you can understand what’s happening across your repository, coordin
GitLens Commit Graph
+## Welcome View + +When you first install or update GitLens, the **Welcome** sidebar view appears above the Commit Graph. It provides a multi-step walkthrough covering Getting Started, Home, Commit Graph, AI Features, Git Blame, PR Reviews, and MCP. The content adapts to your subscription level, helping you discover the features available on your plan. + ## Start in the Commit Graph When you open GitLens, the Commit Graph gives you a connected view of your repository and the work happening across it. @@ -39,10 +43,10 @@ As development spreads across multiple branches, worktrees, and coding agents, k
-Multi-worktree WIP shows working changes across your worktrees, not just the one you currently have open. Agent Sessions connects supported coding agent activity to the branches and worktrees where that work is happening. +Multi-worktree Working Changes shows uncommitted work across your worktrees, not just the one you currently have open. Agent Sessions connects supported coding agent activity to the branches and worktrees where that work is happening.
- + Commit Graph with Working Changes rows for three worktrees: the main worktree's row at the top, then "Working Changes (feature/api-hardening)" and "Working Changes (docs/contributing-refresh)" above their branches' unpushed commits, each branch pill showing its ahead count
From the Commit Graph, you can: @@ -71,7 +75,7 @@ The Commit Graph is more than a place to see the work. It gives you the context 1. Monitor See human and agent work happening across branches, worktrees, and sessions, and quickly identify what needs your attention.
- + The Working Changes details panel with its Agents section expanded: three Claude Code session cards — "Add retry logic to the rate limiter middleware" marked Working with the file it is editing, "Review the authentication module for discrepancies" marked Idle, and "Update README with API rate limiting docs" marked Completed — above the changed files and the commit box
@@ -89,7 +93,7 @@ Review human or agent-generated changes with AI-powered Review. Surface meaningf Turn working changes into clean, logical commits with Commit Composer. Organize related changes, refine commits with AI assistance, and preview the result before writing it to your history.
- + Commit Graph with the Composing Changes panel open beside it: the main branch, an Unstaged changes entry with four files changed (README.md, reports.ts, spending-analysis.ts, user-management.ts) and the Instructions box with the Compose button
4. Compare @@ -119,6 +123,14 @@ When parallel work collides, use AI-assisted conflict resolution to understand a **Monitor parallel work. Review what changed. Shape it. Compare it. Rebase and resolve it. Get it ready to merge. All from the Commit Graph.** +## Change Branch Merge Target + +You can set or reset the merge target for any branch using the Change Branch Merge Target command. This multi-step wizard lets you pick a repository, select a local branch, and choose a remote branch as its merge target. You can also reset the merge target if one was previously set. + +**How to access:** +- From the Commit Graph: Use the merge target indicator in the branch header +- From the Command Palette: `GitLens: Change Branch Merge Target` + ## Stay Oriented as Work Moves The Commit Graph keeps important reference points visible as your repository changes. @@ -136,7 +148,7 @@ Continue exploring the workflows available from the Commit Graph: - [Compare](/gitlens/side-bar/#search-and-compare-view) to understand differences across your work - [AI-powered Rebase](/gitlens/gitlens-features/#interactive-rebase-editor) to automate and clean up rebases - [AI-assisted Conflict Resolution](/gitlens/gl-agents/#resolve-conflicts-in-the-commit-graph) to resolve overlapping work -- [Visual History](/gitlens/gl-visual-file-history/) to understand how your codebase evolved +- [Visual History](/gitlens/gl-visual-file-history/) to visualize how files, branches, or your entire repository evolved over time - [Launchpad](/gitlens/gl-launchpad/) to prioritize pull requests and move work toward merge Or follow a complete workflow from start to finish: diff --git a/gitlens/side-bar.md b/gitlens/side-bar.md index bdb388a..6a469c9 100644 --- a/gitlens/side-bar.md +++ b/gitlens/side-bar.md @@ -5,7 +5,7 @@ taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: September 2026 GitLens provides multiple sidebars that extend the functionality of Visual Studio Code, making it easier to navigate and understand your Git repositories. These include: @@ -32,7 +32,7 @@ This sidebar includes: - **Overview** - **Line History** - **File History** -- **Visual File History** +- **Visual History** - **Search & Compare**
@@ -111,7 +111,7 @@ To restore the default layout, open the Command Palette (Cmd/Ctrl + Shift + ## Commits View
- GitLens Commits view + GitLens Commits view
A [customizable](/gitlens/settings/#commits-view-settings) view to visualize, explore, and manage Git commits. @@ -155,7 +155,7 @@ To open GitLens Inspect, launch the Command Palette (Cmd/Ctrl + Shift + P - Commit details in GitLens Inspect view + GitLens Inspect view showing the details of the commit under the caret: the author and date, the commit message ending in "Closes #7", the Autolinks section listing the resolved #7 pull-request chip, and the changed file
### Overview @@ -163,7 +163,7 @@ The **Commit Details** tab updates as you move your cursor through the file or s The **Overview** tab helps you stage or unstage changes, open files to view modifications, and access associated pull requests. You can also [suggest changes or view Code Suggestions](/gitlens/gitlens-features/#code-suggest-preview) when working on a pull request.
- GitLens Inspect view with code overview and pull request context + GitLens Inspect view showing the Overview of the working changes: the Compose and Review mode toggle, the Working row with its change counts, and the three modified TypeScript files
@@ -172,7 +172,7 @@ The **Overview** tab helps you stage or unstage changes, open files to view modi ## Repositories View
- GitLens Repositories view + GitLens Repositories view with the Playground2026 repository expanded: its upstream status on the repository row and the sub-views beneath it — Commits, Branches, Remotes, Tags, Worktrees and Contributors (Stashes is an optional sub-view, off by default)
A hidden by default, [customizable](/gitlens/settings/#repositories-view-settings) view to visualize, explore, and manage Git repositories. @@ -214,6 +214,7 @@ The **File History** view lists all commits that modified the current file on th - A toggle to pin (pause) automatic tracking of the current editor - A toggle to switch between file and line history +- A toggle to switch between **Commits** mode (default) and **Contributors** mode, which shows all contributors to the file instead of the commit list - The ability to change the base branch or reference for history - (File history only) A toggle to follow renames - (File history only) A toggle to show commits from all branches @@ -229,7 +230,7 @@ The **File History** view lists all commits that modified the current file on th ## Line History View
- GitLens Line History view + GitLens Line History view
A hidden by default, [customizable](/gitlens/settings/#line-history-view-settings) view to visualize, navigate, and explore the revision history of the selected lines of the current file. @@ -247,13 +248,14 @@ The **Line History** view lists all commits that modified the selected lines. It ## Branches View
- GitLens Branches view + GitLens Branches view showing local branches with upstream status indicators, commit history, and branch comparison tools
A [customizable](/gitlens/settings/#branches-view-settings) view to visualize, explore, and manage Git branches. The **Branches** view lists all local branches and includes: +- A repository filter with an **All Repositories excluding worktrees** option that hides linked worktrees whose main repository is also open - A toggle to switch between list or tree layout - A toggle to change file layout: list, tree, or auto - Upstream status icons: @@ -283,7 +285,7 @@ The **Branches** view lists all local branches and includes: ## Remotes View
- GitLens Remotes view + GitLens Remotes view with two remotes: origin, expanded to show its GitHub provider icon, the gitkraken/Playground2026 repository and its remote branches with their last-commit dates, and a self-hosted enterprise remote below it
A [customizable](/gitlens/settings/#remotes-view-settings) view to visualize, explore, and manage Git remotes and remote branches. @@ -404,7 +406,7 @@ To convert a local Workspace, click **Convert to Cloud Workspace**, add a name a Workspace status indicators use symbols and colors, such as a green **O** for the currently open Workspace.
- GitLens Workspace status indicators + The Cloud Workspaces view filtered to Playground2026: under Current Window the repository is listed, and in the Demo2026 workspace the same repository is drawn in green with a green dot at the end of its row — the indicator for the repository open in the current window
### Workspace Linking @@ -431,7 +433,7 @@ To manually add repositories, use the **Add Repositories from Linked Workspace** ## Worktrees View
- GitLens Worktrees view + GitLens Worktrees view
A [customizable](gitlens/gitlens-settings/#worktrees-view-settings) view to create, view, and manage [Git worktrees](https://www.gitkraken.com/learn/git/git-worktree). Worktrees allow you to check out multiple branches at once within the same repository—useful for parallel development or testing workflows without switching branches. @@ -441,7 +443,7 @@ A [customizable](gitlens/gitlens-settings/#worktrees-view-settings) view to crea ## Contributors View
- GitLens Contributors view + GitLens Contributors view
A hidden by default, [customizable](/gitlens/settings/#contributors-view-settings) view to explore repository contributors. @@ -467,7 +469,9 @@ The **Search & Compare** view displays pinnable results from search or compariso ### Pinnable Search -Search commits by message, author, file, ID, or patch using: +Search commits by message, author, file, ID, patch, or natural language query. AI-powered natural language search converts plain English queries into structured Git search operators, so you can search for commits by describing what you are looking for. Time-based search operators are also available for filtering by date ranges. + +Search using: - **Search Commits** (`gitlens.showCommitSearch`): - `` — message match