@@ -22,7 +32,7 @@ Reviewers can then view, accept, and apply these suggestions directly to the pul
---
-## Start a Code Suggestion
+## How to Start a Code Suggestion
1. Open the [GitLens Inspect Overview](/gitlens/side-bar/#overview) for your repository.
2. Check out a branch with an open pull request.
@@ -46,7 +56,7 @@ This action adds a comment on the pull request with two options:
---
-## Review and Apply Suggestions Locally
+## How to Review and Apply Suggestions Locally
1. Select **Locally on your machine**.
2. Open the suggestion in GitLens or [GitKraken Desktop](/gitkraken-client/pull-requests/#review-code-and-suggest-changes).
@@ -60,7 +70,7 @@ This action adds a comment on the pull request with two options:
---
-## Review and Commit Suggestions in gitkraken.dev
+## How to Review and Commit Suggestions in gitkraken.dev
1. Select **Code Suggestion for #PR** to open the suggestion in **gitkraken.dev**.
2. Review each file and its proposed changes.
@@ -79,4 +89,4 @@ This creates a new commit on the remote branch (shown under **COMMIT SUGGESTIONS
Note: Code Suggest is currently supported only for repositories on GitHub.com.
-PRO
-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.
+GitLens Commit Graph gives GitLens users an interactive repository history view for branches, commits, and collaborators. Use it when you need branch-level context or commit relationships that are harder to see in file history, line history, or the standard Source Control view.
+
+| View | Best for | Scope | Access |
+|---|---|---|---|
+| Commit Graph | Branch relationships, rebases, and repository-wide history | Entire repository | Public and local repos for all users; private repos require paid access |
+| Visual File History | Understanding how one file evolved | Single file | Available in GitLens |
+| Line History / Inline Blame | Tracing one line or code region | Single line or selection | Available in GitLens |
@@ -19,7 +32,7 @@ The GitLens Commit Graph provides an interactive view of your repository history
---
-### Open the Commit Graph
+### How to Open the Commit Graph
1. Open the Command Palette:
- macOS: Cmd + Shift + P
@@ -35,7 +48,7 @@ The Commit Graph opens in a new tab, where you can scroll through history and re
---
-### Repository Information
+### How to Read Repository Information
At the top of the Commit Graph, you’ll see:
@@ -62,7 +75,7 @@ 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).
-### Configuration and Layout
+### How to Configure the Commit Graph Layout
You can configure the Commit Graph to control what information is shown and how it is displayed.
@@ -115,7 +128,7 @@ Use scroll markers to quickly jump to important points such as `HEAD` or refs. Y
---
-### Settings
+### How to Open Commit Graph Settings
Adjust Commit Graph settings from the Command Palette:
- macOS: Cmd + Shift + P
@@ -130,7 +143,7 @@ Search for **GitLens: Open Settings**.
---
-### Rich Commit Search
+### How to Search Commits in the Commit Graph
The Commit Graph supports rich search across your entire repository. You can search by commit, message, author, file, or even specific code changes.
@@ -261,4 +274,4 @@ The Minimap provides a high-level overview of repository activity. It shows comm
Note: We’d love your feedback on the Minimap. Please share it on the GitHub Discussion board.
-Note: GitKraken accounts are not compatible with Git Integration for Jira.
@@ -73,4 +80,3 @@ To delete your GitKraken account: > Important: If you're a non-admin member of a GitKraken organization, you must ask an admin to remove your account before you can delete it. Organization admins have control over employee accounts. GitKraken complies with GDPR. Once deleted, your account cannot be restored. This action permanently removes your subscriptions, Cloud Workspaces, Insights data, and organizations. - diff --git a/gitlens/GL-Integrations.md b/gitlens/GL-Integrations.md index 170a2b7..de0bda8 100644 --- a/gitlens/GL-Integrations.md +++ b/gitlens/GL-Integrations.md @@ -1,13 +1,22 @@ --- title: GitLens Integrations description: Explore GitLens integrations with remote providers +product: GitLens +feature: Integrations +content_type: integration +audience: developer +plan_required: all +status: GA +last_verified: 2026-03 taxonomy: category: gitlens --- -Last updated: July 2025 +Last updated: March 2026 -GitLens supports a wide range of remote providers to enhance your Git workflow inside Visual Studio Code. Supported platforms include: +This page explains which remote services GitLens integrates with across supported GitLens IDEs, what each integration enables, and how to connect supported providers. Use it when you need pull request, issue, repository, or Launchpad features that depend on an authenticated Git host or Jira connection. + +Supported platforms include: - GitHub (including GitHub Enterprise) - GitLab @@ -162,7 +171,7 @@ GitLens Pro supports integration with Jira Cloud via your GitKraken Account. Thi
-
### Connect the Jira Integration
diff --git a/gitlens/GL-Interactive-Code-History.md b/gitlens/GL-Interactive-Code-History.md
index e628585..e99ee68 100644
--- a/gitlens/GL-Interactive-Code-History.md
+++ b/gitlens/GL-Interactive-Code-History.md
@@ -1,11 +1,18 @@
---
title: GitLens Interactive Code History
description: Learn how GitLens helps you explore and understand your repository’s commit history.
+product: GitLens
+feature: Interactive Code History
+content_type: concept
+audience: developer
+plan_required: all
+status: GA
+last_verified: 2026-03
taxonomy:
category: gitlens
---
-Last updated: July 2025
+Last updated: March 2026
This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
PRO
-The GitLens Launchpad helps you manage pull requests by status, so you can quickly identify bottlenecks, prioritize work, and take action.
+GitLens Launchpad helps GitLens users organize pull requests by status and next action without leaving the editor. Use it when you need a prioritized review queue across repositories and connected Git hosts, especially for pull requests waiting on you or needing follow-up.
+
+| Workflow | Recommended tool | Best for |
+|---|---|---|
+| Prioritizing pull requests across repositories | Launchpad | A single action queue for reviews and follow-up |
+| Inspecting current repository activity | Home View | Quick status and recent work in one repository |
+| Reviewing one pull request in the host UI | Browser or host UI | Host-specific merge or admin actions |
@@ -19,7 +32,7 @@ The GitLens Launchpad helps you manage pull requests by status, so you can quick
---
-### Open the Launchpad
+### How to Open Launchpad
1. Open the Command Palette:
- macOS: Cmd + Shift + P
@@ -33,7 +46,7 @@ The GitLens Launchpad helps you manage pull requests by status, so you can quick
---
-### Review Pull Requests
+### How to Review Pull Requests from Launchpad
The Launchpad displays pull requests for your repositories, grouped by status:
- Ready to merge
@@ -57,7 +70,7 @@ Select a pull request to:
---
-### Code Suggestions
+### How to Start or Review Code Suggestions from Launchpad
You can start or review [Code Suggestions](/gitlens/gitlens-features/#code-suggest-preview) directly from pull requests in the Launchpad.
@@ -68,7 +81,7 @@ You can start or review [Code Suggestions](/gitlens/gitlens-features/#code-sugge
---
-### Pin or Snooze Pull Requests
+### How to Pin or Snooze Pull Requests
- **Pin**: Use the pin icon to move a pull request to the pinned group.
- **Snooze**: Use the snooze icon to move it to the snoozed group.
@@ -85,4 +98,4 @@ You can start or review [Code Suggestions](/gitlens/gitlens-features/#code-sugge
- Supported for **GitHub.com** and **GitLab.com** repositories only. Connect the [GitHub or GitLab integration](/gitlens/gitlens-features/#connecting-the-github-and-gitlab-integration) to use Launchpad.
- Launchpad prioritizes items that require immediate action, placing them at the top. (This may change in future updates.)
-- This feature is available with a **Pro subscription tier or higher**.
\ No newline at end of file
+- This feature is available on **Pro, Advanced, Business, and Enterprise** plans.
diff --git a/gitlens/GL-Security.md b/gitlens/GL-Security.md
index 6122ee9..75fbb12 100644
--- a/gitlens/GL-Security.md
+++ b/gitlens/GL-Security.md
@@ -1,12 +1,21 @@
---
title: GitLens Security Information
description: Learn how GitLens secures your data, including collection, transfer, storage, and SOC 2 certification.
+product: GitLens
+feature: Security Information
+content_type: security
+audience: all
+plan_required: all
+status: GA
+last_verified: 2026-03
taxonomy:
category: gitlens
---
-Last updated: August 2025
+Last updated: March 2026
+
+This page explains GitLens data collection, storage, transport security, and SOC 2 status for users evaluating GitLens security and compliance. Use it when you need to confirm what GitLens stores, where service data lives, and which protections apply to subscription, account, and AI-related data.
## Data Collection and Storage
@@ -30,4 +39,4 @@ Please note: an MNDA must be signed before we can provide a copy of the report.
Note: SOC 2 reports are only available for Business and Enterprise customers.
-This feature is available with a GitLens Pro subscription or higher.
The Community plan supports Public and Local repositories only. A paid GitLens subscription is required for private repositories.
-
@@ -47,7 +61,7 @@ Available commands:
***
-## Current Line Blame
+## How to Use Current Line Blame
@@ -802,7 +816,7 @@ Click the icon again to unpin or unsnooze as needed.
diff --git a/llms-full.txt b/llms-full.txt
index 79639dd..7343dcc 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -1,29 +1,39 @@
# GitLens Documentation — Full Content
-> GitLens documentation — the #1 Git extension for Visual Studio Code. Supercharge your Git workflows with blame, code history, commit graphs, and more.
+> GitLens documentation for VS Code, Cursor, Windsurf, Trae, and Kiro.
-Generated: 2026-03-23
+Generated: 2026-03-24
---
## Get Started with GitLens
URL: https://help.gitkraken.com/gitlens/gitlens-home/
-Description: How to install and start using GitLens in Visual Studio Code
+Description: How to install and start using GitLens in VS Code, Cursor, Windsurf, Trae, and Kiro
+Last updated: March 2026
-Last updated: July 2025
+This page helps GitLens users install GitLens and choose the first workflows to try after installation in VS Code, Cursor, Windsurf, Trae, or Kiro. Start here if you are new to GitLens and want a guided path into history inspection, pull request review, collaboration features, and integrations.
-Welcome to the GitLens Support Documentation site!
+GitLens can be installed for **VS Code**, **Cursor**, **Windsurf**, **Trae**, and **Kiro**. Use the install flow for your IDE:
-GitLens is the #1 most downloaded [Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) Git extension that supercharges your developer workflows. You can download GitLens from the VS Code marketplace:
+Install GitLens (https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens)
-Install GitLens
+- Install GitLens in Cursor (cursor:extension/eamodio.gitlens)
+- Install GitLens in Windsurf (windsurf:extension/eamodio.gitlens)
+- Install GitLens in Trae (trae:extension/eamodio.gitlens)
+- Install GitLens in Kiro (kiro:extension/eamodio.gitlens)
-GitLens is known for its blame, hover, and annotations, but there’s much more to the extension. Users are leveraging its rich features to increase their developer productivity, which you can learn more about in the popular workflows below.
+GitLens includes history inspection, pull request review, collaboration, and integration workflows, which you can explore below.
-* [Interactive Code History](/gitlens/gitlens-home/#interactive-code-history)
-* [Accelerate PR Reviews](/gitlens/gitlens-home/#accelerate-pr-reviews)
-* [Streamline Collaboration](/gitlens/gitlens-home/#streamline-collaboration)
+**Quick start:**
+1. Install GitLens in your IDE.
+2. Open a repository in your IDE.
+3. Open Commit Graph or GitLens Inspect to start exploring history.
+4. Connect GitHub, GitLab, or Jira integrations if you need pull request and issue workflows.
+
+* Interactive Code History (/gitlens/gitlens-home/#interactive-code-history)
+* Accelerate PR Reviews (/gitlens/gitlens-home/#accelerate-pr-reviews)
+* Streamline Collaboration (/gitlens/gitlens-home/#streamline-collaboration)
***
@@ -31,7 +41,7 @@ GitLens is known for its blame, hover, and annotations, but there’s much more
-
+
Understanding your repository's history is easier with GitLens. Whether you're navigating complex branches or reviewing past changes, GitLens offers intuitive tools to reveal who changed what and why.
@@ -48,7 +58,7 @@ The Commit Graph provides an interactive visual history of your branches and com
- Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`) and run **GitLens: Show Commit Graph View**, or
- Click the **Commit Graph** icon in the sidebar
-[Open the Commit Graph in GitLens](vscode://eamodio.gitlens/link/command/graph)
+Open the Commit Graph in GitLens (vscode://eamodio.gitlens/link/command/graph)
### Use GitLens Inspect
@@ -62,7 +72,7 @@ GitLens Inspect helps you dive deeper into a specific commit. It shows:
- Right-click any commit and select **Inspect Details**
-[Open the Inspect View in GitLens](vscode://eamodio.gitlens/link/command/inspect)
+Open the Inspect View in GitLens (vscode://eamodio.gitlens/link/command/inspect)
### Explore Inline Blame and Hovers
@@ -79,19 +89,15 @@ These insights help you trace decisions and collaborate more effectively.
## Accelerate PR Reviews
-
-
-Video: Review pull requests without leaving your IDE
-
Manually switching between browser tabs, emails, and PR tools can interrupt your development flow. GitLens helps you stay focused in Visual Studio Code by organizing pull request tasks and supporting multiple workspaces with worktrees.
### Launchpad `PRO`
-This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
Launchpad provides a centralized view of your pull requests. You can:
-- Connect your [GitHub Integration](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens)
+- Connect your GitHub Integration (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens)
- View PRs by action status: needs review, follow-up, blocked, draft, and more
- Open pull requests in a new worktree or switch branches directly
@@ -99,7 +105,7 @@ Launchpad provides a centralized view of your pull requests. You can:
- Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`) and run **GitLens: Open Launchpad**
-[Open the Launchpad in GitLens](vscode://eamodio.gitlens/link/command/launchpad)
+Open the Launchpad in GitLens (vscode://eamodio.gitlens/link/command/launchpad)
### Worktrees
@@ -113,21 +119,17 @@ Worktrees let you check out multiple branches at once without stashing or commit
**To open Worktree View:**
-[Open the Worktree View in GitLens](vscode://eamodio.gitlens/link/command/worktrees)
+Open the Worktree View in GitLens (vscode://eamodio.gitlens/link/command/worktrees)
***
## Streamline Team Collaboration
-
-
-Video: Share code and suggest changes in GitLens
-
GitLens enables flexible collaboration without needing to commit or push unfinished code. Use **Cloud Patches** to share changes privately and **Code Suggest** to offer improvements across a pull request—even for unmodified files.
### Cloud Patches `PRO`
-This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
Cloud Patches are sharable Git patches that can be applied across your GitKraken organization:
@@ -135,11 +137,11 @@ Cloud Patches are sharable Git patches that can be applied across your GitKraken
- Open the Command Palette and run **GitLens: Share as Cloud Patch…**
- Select collaborators to notify via the Cloud Patch sidebar
-[Open the Cloud Patches View in GitLens](vscode://eamodio.gitlens/link/command/cloud-patches)
+Open the Cloud Patches View in GitLens (vscode://eamodio.gitlens/link/command/cloud-patches)
### Code Suggest `PRO`
-This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
Suggest code edits to any file—even those not changed in the original PR:
@@ -153,10 +155,6 @@ The pull request owner can apply, modify, and commit these suggestions to stream
## Connect GitLens to External Services
-
-
-Video: Use integrations and autolinks to connect GitLens to tools like Jira
-
Boost your productivity by integrating GitLens with platforms like GitHub, GitLab, Azure DevOps, Bitbucket, Jira, and Trello. Reduce context switching and bring external issue tracking directly into your Git workflows.
### Integrations
@@ -167,7 +165,7 @@ Connect GitLens to your code host and issue tracker to:
- Automatically show pull requests and issues related to your branch
- Avoid switching between your editor and browser
-To set up an integration, go to **Settings > Integrations** or visit the [GitLens Integrations Settings](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
+To set up an integration, go to **Settings > Integrations** or visit the GitLens Integrations Settings (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
### Autolinks
@@ -179,9 +177,9 @@ You can also create custom autolinks by defining pattern-matching rules for exte
## Other Resources
-- 📌 [GitHub Repository](https://github.com/gitkraken/vscode-gitlens) — Submit feature requests or bug reports
-- 💬 [Join GitKraken Slack](https://slack.gitkraken.com/) — Connect with the GitLens community
-- 🛠️ [Contact Support](https://help.gitkraken.com/gitlens/gl-contact-support) — Paid users can get direct help from our support team
+- 📌 GitHub Repository (https://github.com/gitkraken/vscode-gitlens) — Submit feature requests or bug reports
+- 💬 Join GitKraken Slack (https://slack.gitkraken.com/) — Connect with the GitLens community
+- 🛠️ Contact Support (https://help.gitkraken.com/gitlens/gl-contact-support) — Paid users can get direct help from our support team
---
@@ -189,26 +187,28 @@ You can also create custom autolinks by defining pattern-matching rules for exte
URL: https://help.gitkraken.com/gitlens/gl-accelerate-pr-reviews/
Description: Explore how GitLens helps streamline pull request reviews using Launchpad and Worktrees.
+Last updated: March 2026
-Last updated: July 2025
-
-
-
-
+This page explains how GitLens helps users review pull requests faster with Launchpad and Worktrees across supported GitLens IDEs. Use Launchpad to prioritize incoming pull requests and Worktrees to inspect or test multiple pull request branches locally without repeated branch switching.
-Reviewing pull requests (PRs) in the browser can interrupt your workflow. Switching tabs, checking email notifications, and managing local branches can be time-consuming—especially when the PRs aren’t even relevant to you.
+Reviewing pull requests (PRs) in the browser can interrupt your workflow. Switching tabs, checking email notifications, and managing local branches can be time-consuming, especially when the PRs are not relevant to you.
-GitLens helps streamline PR reviews directly inside Visual Studio Code. With **Launchpad** and **Worktrees**, you can:
+GitLens helps streamline PR reviews directly inside supported GitLens IDEs. With **Launchpad** and **Worktrees**, you can:
- View all relevant PRs grouped by actionable categories.
- Avoid context switching with an integrated experience.
- Work across multiple branches using separate working directories.
-## Launchpad `PRO`
+| Review task | Recommended feature | Why |
+|---|---|---|
+| Decide what to review next | Launchpad | Prioritizes pull requests by required action |
+| Review or test a pull request branch locally | Worktrees | Keeps multiple branches available without stashing |
+
+## When to Use Launchpad `PRO`
To use Launchpad:
-1. Connect your [GitHub Integration](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
+1. Connect your GitHub Integration (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
2. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
3. Run: `GitLens: Open Launchpad`.
@@ -224,11 +224,9 @@ To start reviewing:
- Select a PR.
- Choose **Open in Worktree** or **Switch to Branch or Worktree**.
-[Open the Launchpad in GitLens](vscode://eamodio.gitlens/link/command/launchpad)
+Open the Launchpad in GitLens (vscode://eamodio.gitlens/link/command/launchpad)
-This feature is available with a GitLens Pro subscription or higher.
-
-## Worktrees
+## When to Use 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.
@@ -238,9 +236,7 @@ After opening a worktree, use the Pull Request sidebar to:
- Explore changed files
- View diffs and inspect updates line by line
-[Open the Worktree View in GitLens](vscode://eamodio.gitlens/link/command/worktrees)
-
-The Community plan supports only public and local repositories.
+Open the Worktree View in GitLens (vscode://eamodio.gitlens/link/command/worktrees)
---
@@ -252,6 +248,19 @@ Description: Use Git intelligence to transform iterative work into clean, review
**Level:** Intermediate Developers
**Primary Goal:** Use Git intelligence to transform iterative work into clean, reviewable history
+**Requirements:**
+- **Audience:** Developers preparing a branch for review
+- **GitLens features used:** Commit Graph, Commit Composer, Launchpad, Worktrees
+- **Plan requirements:** Some referenced features may require Pro, Advanced, Business, or Enterprise
+- **Best for:** Cleaning up noisy history before opening or updating a pull request
+
+| Task | GitLens feature | Why it helps |
+|---|---|---|
+| Review branch structure | Commit Graph | Shows divergence, commit order, and related branch context |
+| Rewrite noisy commits | Commit Composer | Recompose commits into cleaner review units |
+| Check review status | Launchpad | Surfaces pull request state and related follow-up |
+| Handle interruptions | Worktrees | Lets you switch to urgent work without disturbing your branch |
+
## When to use this workflow
Use this workflow when you are:
@@ -272,38 +281,21 @@ You have finished implementing a feature, but your branch contains several explo
You begin by opening the **Commit Graph** from the GitLens sidebar, which gives you a visual view of your branch history and how your work diverges from main. From there, you select the commits related to the feature and open **Commit Composer** directly from the graph.
-
-Recompose Selected Commits
-
-
-Recompose Selected Commits
-
--->
-
Commit Composer uses Git intelligence to understand the structure of your changes and allows you to recompose them into clearer, more intentional commits. With **Selective Recomposition**, you can choose only the relevant commits, rewrite their messages, split changes, or combine related work, all before anything is rewritten on disk.
-
-Commit Composer with Selective Recomposition
-
As you review your branch, you open **Launchpad** to check for open pull requests, review feedback, or dependencies that might affect your changes, keeping everything in one place instead of jumping between tools.
-
-Launchpad
-
When an urgent fix on another branch comes up, you create a **Worktree** from GitLens, which lets you check out another branch in a separate folder without stashing or disturbing your current work. Throughout the process, you rely on advanced **Commit Graph context menu actions**, accessed by right-clicking commits, to compare branches, inspect diffs, and validate that your history tells a clear story.
-
-Commit Graph Context Menu
-
GitLens uses Git intelligence to help you ship work that is easier to review, reason about, and maintain.
## Key GitLens features used
-- [Commit Graph (visual branch and commit context)](https://help.gitkraken.com/gitlens/gitlens-features/#commit-graph-pro)
+- Commit Graph (visual branch and commit context) (https://help.gitkraken.com/gitlens/gitlens-features/#commit-graph-pro)
-- [Commit Composer with Selective Recomposition](https://help.gitkraken.com/gitlens/gitlens-features/###Commit-composer:-Selective-Recomposition)
+- Commit Composer with Selective Recomposition (https://help.gitkraken.com/gitlens/gitlens-features/###Commit-composer:-Selective-Recomposition)
-- [Launchpad (PR and review awareness)](https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro)
+- Launchpad (PR and review awareness) (https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro)
- Worktrees (parallel branch workflows)
@@ -319,19 +311,15 @@ You submit a pull request with a clean, intentional commit history that reviewer
URL: https://help.gitkraken.com/gitlens/gl-gk-account/
Description: Learn how to create and manage your GitKraken account for GitLens features.
+Last updated: March 2026
-Last updated: July 2025
-
-Your GitKraken account is your key to unlocking the most personal experience across GitKraken products.
-
-Note: GitKraken accounts are not compatible with Git Integration for Jira.
-We recommend creating and using a single GitKraken account per person. Avoid creating duplicate accounts or sharing your account with others.
+This page explains how GitLens users create, sign in to, personalize, and delete a GitKraken account for GitLens features that require authentication. Use it when GitLens prompts for a GitKraken account or when you need to update account settings used across GitKraken products.
***
## Sign In or Create an Account
-You can create a GitKraken account at [gitkraken.dev](https://gitkraken.dev/register?source=help_center&product=gitkraken_dot_dev) or directly within GitLens.
+You can create a GitKraken account at gitkraken.dev (https://gitkraken.dev/register?source=help_center&product=gitkraken_dot_dev) or directly within GitLens.
When prompted with the login screen, select **Create an account** to begin. Choose one of the following seven identity providers:
@@ -341,10 +329,7 @@ When prompted with the login screen, select **Create an account** to begin. Choo
- Azure DevOps
- Email
- Google
-- [Single Sign-On (SSO)](/gk-dev/gk-dev-single-sign-on/)
-
-
-Select a login method to create your GitKraken account
+- Single Sign-On (SSO) (/gk-dev/gk-dev-single-sign-on/)
Once your account is created, it is linked to the primary email associated with your selected login method. If you choose **Sign up with Email**, check your inbox for a verification link to complete the process.
@@ -352,26 +337,23 @@ Once your account is created, it is linked to the primary email associated with
## Personalize Your Account
-You can personalize your GitKraken account to control how your profile appears to other users within any associated [organization](/gk-dev/gk-dev-organization/). Visit [gitkraken.dev/account](https://gitkraken.dev/?source=help_center&product=gitkraken_dot_dev) after logging in to:
+You can personalize your GitKraken account to control how your profile appears to other users within any associated organization (/gk-dev/gk-dev-organization/). Visit gitkraken.dev/account (https://gitkraken.dev/?source=help_center&product=gitkraken_dot_dev) after logging in to:
- Update your avatar
- Edit your name, username, and email
- Change your password
-To change your avatar, click your profile picture. This will redirect you to [Gravatar](https://gravatar.com), where you can manage the avatar linked to your email address. GitKraken retrieves your avatar from Gravatar based on the shared email between accounts.
+To change your avatar, click your profile picture. This will redirect you to Gravatar (https://gravatar.com), where you can manage the avatar linked to your email address. GitKraken retrieves your avatar from Gravatar based on the shared email between accounts.
Note: It may take several hours for avatar changes to appear in GitKraken or GitLens.
-
-Customize your name, email, avatar, and password
-
***
## Delete Your Account
To delete your GitKraken account:
-1. Go to [gitkraken.dev/account](https://gitkraken.dev/account?source=help_center&product=gitkraken_dot_dev).
+1. Go to gitkraken.dev/account (https://gitkraken.dev/account?source=help_center&product=gitkraken_dot_dev).
2. Select **Delete my Account** (highlighted in red).
3. Follow the on-screen confirmation steps.
4. Select **Delete your Account** to confirm deletion.
@@ -385,9 +367,9 @@ GitKraken complies with GDPR. Once deleted, your account cannot be restored. Thi
## GitKraken AI Features in GitLens
URL: https://help.gitkraken.com/gitlens/gl-gk-ai/
-Description: Learn more about the use of Gitkraken AI in Gitlens!
+Description: Learn how to use GitKraken AI features in GitLens.
-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.
+This page explains GitLens AI features for Visual Studio Code users, including commit generation, explanations, changelog creation, and pull request workflows. Use it to identify which GitLens AI features are available on your plan and which provider settings or token limits apply before enabling them.
---
@@ -460,7 +442,7 @@ Open Pull Requests: Automatically generate clear PR titles and descriptions dire
---
## AI Token Allocation by Plan
-GitKraken AI features operate on a token-based system, with different allocations based on your subscription. For more information about Gitkraken AI allocations, please see our [Gitkraken AI FAQ](https://help.gitkraken.com/general/gitkraken-ai-faq) page.
+GitKraken AI features operate on a token-based system, with different allocations based on your subscription. For more information about Gitkraken AI allocations, please see our Gitkraken AI FAQ (https://help.gitkraken.com/general/gitkraken-ai-faq) page.
Tokens refresh weekly and are shared across all AI features. More complex operations like changelog generation typically use more tokens than simpler ones like commit messages.
@@ -506,7 +488,7 @@ To configure your AI provider:
---
-More questions about Gitkraken AI? Please see our GitKraken AI FAQ page for more details. For additional questions or support regarding GitKraken AI features, please contact our support team or visit the GitKraken Community forum.
+More questions about Gitkraken AI? Please see our GitKraken AI FAQ page (https://help.gitkraken.com/general/gitkraken-ai-faq/) for more details. For additional questions or support regarding GitKraken AI features, please contact our support team or visit the GitKraken Community forum (https://forum.gitkraken.com/).
---
@@ -514,19 +496,15 @@ More questions about Gitkraken AI? Please see our GitKraken AI FAQ page for more
URL: https://help.gitkraken.com/gitlens/gl-cloud-patches/
Description: Use GitLens Cloud Patches to securely share work-in-progress changes across GitKraken tools for early collaboration.
-
-Last updated: August 2025
+Last updated: March 2026
## What Are Cloud Patches?
-A **Cloud Patch** is a Git patch securely stored by GitKraken so it can be easily shared across **GitLens**, **GitKraken Desktop**, and the **GitKraken CLI**.
-The patch is transferred directly from your machine into secure storage.
-
-Cloud Patches let you collaborate with your team **before creating a pull request**. You can share work in progress, gather feedback early, and minimize delays in pull request reviews.
+GitLens Cloud Patches let GitLens users securely share uncommitted or in-progress changes across **GitLens**, **GitKraken Desktop**, and the **GitKraken CLI** before opening a pull request. Use this feature when you need early feedback on work in progress and have a GitKraken account with Cloud Patch access.
---
-## Set Up Cloud Patches
+## How to Set Up GitLens Cloud Patches
To enable or disable Cloud Patches per client:
@@ -540,56 +518,47 @@ To enable or disable Cloud Patches per client:
---
-## Create and Share Cloud Patches
+## How to Create and Share a Cloud Patch
You can manage Cloud Patches from the **Cloud Patches view** in the GitLens sidebar.
-
-Creating a Cloud Patch
-
A Cloud Patch can be created from **Working Changes, Commits, Stashes, or Comparisons** by selecting **Share as Cloud Patch** from either:
- The Command Palette
- The **Share** submenu in applicable GitLens views
-
-Example of creating a Cloud Patch
-
### Sharing Options
When creating a Cloud Patch, choose one of the following:
+| Sharing option | Requires account | Best for | Limitation |
+|---|---|---|---|
+| Anyone with the link | No | Fast sharing outside your organization | Anyone with the link can access it |
+| Anyone in my org | Yes | Broad sharing within a GitKraken organization | Limited to organization members |
+| Only collaborators | Yes | Restricted review with named teammates | Requires selecting collaborators |
+
- **Anyone with the link**: Public access for anyone with the link.
- **Anyone in my org**: Accessible to members of your GitKraken Organization (authentication required).
- **Only collaborators**: Restricted to selected GitKraken Organization members (authentication required). Use **Invite** to select members.
Cloud Patches shared with you appear under **Shared with Me** in the Cloud Patches section.
-
-Cloud Patch sharing options
-
---
-## Apply and Manage Cloud Patches
+## How to Apply or Delete a Cloud Patch
- Open a Cloud Patch from a shared URL to view it in GitLens.
- Apply it to your **working tree** or to a **new/existing branch** by following the prompts in GitLens.
-
-Applying a Cloud Patch
-
### Delete a Cloud Patch
1. Right-click the patch in the Cloud Patches view.
2. Select **Delete Cloud Patch…**
-
-Deleting a Cloud Patch
-
---
## Self-Host Cloud Patch Data
If you do not want Cloud Patch data stored on GitKraken servers, you can host Cloud Patches on your own **AWS S3 storage instance**.
-For configuration instructions, see [Self-Hosted Documentation](/gk-dev/gk-dev-home/#self-hosted).
+For configuration instructions, see Self-Hosted Documentation (/gk-dev/gk-dev-home/#self-hosted).
Note: If you belong to multiple organizations, you can switch between them from the GitKraken Account view.
@@ -599,54 +568,44 @@ Note: If you belong to multiple organizations, you can switch between them from
URL: https://help.gitkraken.com/gitlens/gl-code-suggest/
Description: Use GitLens Code Suggest to propose edits and code review suggestions across entire projects in GitHub repositories.
-
-Last updated: August 2025
+Last updated: March 2026
## What Is Code Suggest?
-**GitLens Code Suggest** simplifies code review by allowing you to make suggestions and edits across the entire project, not just on changed lines.
-Suggestions can be created within **GitLens**, **GitKraken Desktop**, or **gitkraken.dev** and attached to pull requests.
-
-Reviewers can then view, accept, and apply these suggestions directly to the pull request branch.
-
+GitLens Code Suggest lets GitLens users propose project-wide edits and review suggestions for GitHub pull requests from **GitLens**, **GitKraken Desktop**, or **gitkraken.dev**. Use it when review feedback spans files beyond changed-line comments and your repository supports Code Suggest workflows.
-GitLens Code Suggest view
+**Requirements:**
+- **Supported host:** GitHub.com repositories
+- **Requires:** An open pull request on the branch you are reviewing
+- **Review surfaces:** GitLens, GitKraken Desktop, or gitkraken.dev
+- **Best for:** Multi-file or project-wide pull request suggestions
---
-## Start a Code Suggestion
+## How to Start a Code Suggestion
-1. Open the [GitLens Inspect Overview](/gitlens/side-bar/#overview) for your repository.
+1. Open the GitLens Inspect Overview (/gitlens/side-bar/#overview) for your repository.
2. Check out a branch with an open pull request.
3. Select **Start Review for PR #PR**.
4. Modify and save any files you want to include in the suggestion.
5. When ready, select **Suggest Changes for PR** → provide a title → **Create Code Suggestion**.
-
-Creating a Code Suggestion
-
This action adds a comment on the pull request with two options:
- **Code Suggestion for #PR** → review in **gitkraken.dev**
- **Locally on your machine** → review in **GitLens** or **GitKraken Desktop**
-
-Pull request with Code Suggestion comment
-
---
-## Review and Apply Suggestions Locally
+## How to Review and Apply Suggestions Locally
1. Select **Locally on your machine**.
-2. Open the suggestion in GitLens or [GitKraken Desktop](/gitkraken-client/pull-requests/#review-code-and-suggest-changes).
+2. Open the suggestion in GitLens or GitKraken Desktop (/gitkraken-client/pull-requests/#review-code-and-suggest-changes).
3. Review changes file by file.
4. Choose **Apply** to apply to your current branch, or select **Apply to a Branch** to apply to a new or existing branch.
-
-Applying a Code Suggestion locally
-
---
-## Review and Commit Suggestions in gitkraken.dev
+## How to Review and Commit Suggestions in gitkraken.dev
1. Select **Code Suggestion for #PR** to open the suggestion in **gitkraken.dev**.
2. Review each file and its proposed changes.
@@ -654,9 +613,6 @@ Applying a Code Suggestion locally
This creates a new commit on the remote branch (shown under **COMMIT SUGGESTIONS TO**).
-
-Committing suggestions in gitkraken.dev
-
---
## Availability
@@ -668,20 +624,22 @@ Note: Code Suggest is currently supported only for repositories on GitHub.com.
## GitLens Commit Graph
URL: https://help.gitkraken.com/gitlens/gl-commit-graph/
-Description: Visualize your repository history, branches, and collaborators with the GitLens Commit Graph in VS Code.
-
-Last updated: August 2025
+Description: Visualize your repository history, branches, and collaborators with GitLens Commit Graph across supported GitLens IDEs.
+Last updated: March 2026
## Commit Graph PRO
-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.
+GitLens Commit Graph gives GitLens users an interactive repository history view for branches, commits, and collaborators. Use it when you need branch-level context or commit relationships that are harder to see in file history, line history, or the standard Source Control view.
-
-Commit Graph overview in GitLens
+| View | Best for | Scope | Access |
+|---|---|---|---|
+| Commit Graph | Branch relationships, rebases, and repository-wide history | Entire repository | Public and local repos for all users; private repos require paid access |
+| Visual File History | Understanding how one file evolved | Single file | Available in GitLens |
+| Line History / Inline Blame | Tracing one line or code region | Single line or selection | Available in GitLens |
---
-### Open the Commit Graph
+### How to Open the Commit Graph
1. Open the Command Palette:
- macOS: Cmd + Shift + P
@@ -690,12 +648,9 @@ Commit Graph overview in GitLens
The Commit Graph opens in a new tab, where you can scroll through history and resize column widths.
-
-Opening the Commit Graph from the Command Palette
-
---
-### Repository Information
+### How to Read Repository Information
At the top of the Commit Graph, you’ll see:
@@ -703,9 +658,6 @@ At the top of the Commit Graph, you’ll see:
- **Checked-out branch** (click to switch branches)
- **Last fetched time** (click **Fetch** to update)
-
-Repository details in the Commit Graph toolbar
-
---
### Availability
@@ -717,9 +669,9 @@ Repository details in the Commit Graph toolbar
### Feedback
-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).
+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).
-### Configuration and Layout
+### How to Configure the Commit Graph Layout
You can configure the Commit Graph to control what information is shown and how it is displayed.
@@ -728,9 +680,6 @@ You can configure the Commit Graph to control what information is shown and how
- Right-click a column header to toggle columns on or off.
- The **Changes** column shows added lines in green and deleted lines in red.
-
-Commit Graph column settings
-
#### Layout Options
- **Panel Layout**: Displays the Commit Graph in the bottom panel (near the Terminal) with a details view alongside it.
- **Editor Layout**: Opens the Commit Graph in an editor tab.
@@ -740,31 +689,22 @@ 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**.
-
-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.
- 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 Graph and Author column with avatars
-
#### Scroll Markers
Scroll markers highlight key points in the Commit Graph, including:
- Checked-out branches
- Selected rows
- Search results
-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).
-
-
-Scroll markers in the Commit Graph
+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).
---
-### Settings
+### How to Open Commit Graph Settings
Adjust Commit Graph settings from the Command Palette:
- macOS: Cmd + Shift + P
@@ -772,12 +712,9 @@ Adjust Commit Graph settings from the Command Palette:
Search for **GitLens: Open Settings**.
-
-Opening Commit Graph settings
-
---
-### Rich Commit Search
+### How to Search Commits in the Commit Graph
The Commit Graph supports rich search across your entire repository. You can search by commit, message, author, file, or even specific code changes.
@@ -787,15 +724,9 @@ The Commit Graph supports rich search across your entire repository. You can sea
- Next result: F3 (Windows/Linux) or Cmd + G (macOS)
- Previous result: Shift + F3 (Windows/Linux) or Shift + Cmd + G (macOS)
-
-Searching commits in the Commit Graph
-
You can also:
- Jump to the **first or last result** by holding Shift while clicking the arrow icons.
-
-Navigating commit search results
-
#### Search Filters
Use these filters in the search bar:
- `Commit:`
@@ -810,16 +741,10 @@ Additional options:
- Match case
- Use regular expressions
-
-Commit Graph search options
-
### Full Context Menu Support
You can right-click a branch, commit, tag, author, or column header (Author, Commit Date/Time, or SHA) to access context menu actions.
-
-Commit Graph context menu options
-
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.
@@ -829,10 +754,7 @@ Helpful context menu actions include:
### Pull Request Information
-For GitHub and GitLab, the Commit Graph displays a Pull Request icon for any branch with an open pull request. To enable this, connect a [rich integration](/gitlens/settings/#remote-provider-integration-settings).
-
-
-Pull request icon in Commit Graph
+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).
---
@@ -842,9 +764,6 @@ The Commit Graph shows refs to your remotes, branches, and tags.
- Hover over any ref to use the **Hide** option.
- To show them again, hover over the **Hide** option at the top of the Commit Graph and select the desired refs.
-
-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.
@@ -857,9 +776,6 @@ Additional options let you hide or show:
You can also dim merge commit rows for clarity.
-
-Commit Graph filter options
-
---
### Minimap (Experimental)
@@ -870,12 +786,6 @@ The Minimap provides a high-level overview of repository activity. It shows comm
- Use the graph icon dropdown to switch between **Commits** or **Lines Changed** views.
- Toggle markers on or off from the same menu.
-
-Commit Graph Minimap
-
-
-Minimap settings and options
-
#### Minimap Overview
- **Reads left to right**: Left = most recent, right = older.
- **Highlighted region**: Area currently in view.
@@ -896,17 +806,20 @@ Note: We’d love your feedback on the Minimap. Please share it on the GitHub Di
URL: https://help.gitkraken.com/gitlens/gitlens-community-vs-gitlens-pro/
Description: Learn the differences between GitLens Community and GitLens Pro
+Last updated: March 2026
-Last updated: July 2025
-
-
-
-
-
-Whether you're reviewing code, managing pull requests, or exploring your project history, GitLens enhances your Git experience—directly inside Visual Studio Code.
+This page compares GitLens Community and GitLens Pro for GitLens users choosing between free and paid GitLens capabilities across supported IDEs. Use it to decide whether your repository type, collaboration needs, and advanced history or review workflows require GitLens Pro.
Let’s explore the key differences between the **Community** and **Pro** editions to help you choose the version that fits your workflow.
+| Capability | GitLens Community | GitLens Pro | Best for |
+|---|---|---|---|
+| Blame, hovers, and CodeLens | Yes | Yes | Everyday authorship and file history |
+| Revision navigation | Yes | Yes | Inspecting prior file versions |
+| Launchpad and advanced PR review workflows | No | Yes | Teams reviewing pull requests in VS Code |
+| Advanced collaboration and integrations | Limited | Yes | Multi-repository and team workflows |
+| Advanced Git operations and AI workflows | Limited | Yes | Power users and collaborative teams |
+
## GitLens Community (Free)
The GitLens Community edition is **free** and offers powerful tools to help you understand code history and authorship:
@@ -926,7 +839,7 @@ GitLens Pro takes your development workflow to the next level with advanced feat
- **Streamline collaboration** by integrating with GitHub, GitLab, and Bitbucket. View and manage pull requests directly within VS Code.
_Perfect for: Professional developers, collaborative teams, and organizations optimizing for productivity._
-[Start your free 14-day trial](https://gitkraken.dev/register?product=gitlens&source=marketing_page&redirect_uri=vscode%3A%2F%2Feamodio.gitlens%2Flogin&flow=gitlens_web&utm_source=website&utm_medium=help-center&utm_campaign=pro-vs-community-pg&utm_content=button) of GitLens Pro today.
+Start your free 14-day trial (https://gitkraken.dev/register?product=gitlens&source=marketing_page&redirect_uri=vscode%3A%2F%2Feamodio.gitlens%2Flogin&flow=gitlens_web&utm_source=website&utm_medium=help-center&utm_campaign=pro-vs-community-pg&utm_content=button) of GitLens Pro today.
***
@@ -956,9 +869,9 @@ _Both editions are built to enhance your Git experience. Start with Community an
## Get Started with GitLens Pro Today
-Try GitLens Pro for free
+Try GitLens Pro for free (https://gitkraken.dev/register?source=help_center&product=gitlens&redirect_uri=vscode%3A%2F%2Feamodio.gitlens%2Flogin&flow=gitlens_web&utm_source=website&utm_medium=help-center&utm_campaign=pro-vs-community-pg&utm_content=button)
-Enjoy GitLens Pro free for 14 days. When you're ready, [upgrade your plan](https://gitkraken.dev/purchase/checkout?planType=PRO&planQuantity=1&?source=help_center&product=gitlens) to keep Pro features.
+Enjoy GitLens Pro free for 14 days. When you're ready, upgrade your plan (https://gitkraken.dev/purchase/checkout?planType=PRO&planQuantity=1&?source=help_center&product=gitlens) to keep Pro features.
---
@@ -966,8 +879,7 @@ Enjoy GitLens Pro free for 14 days. When you're ready, [upgrade your plan](https
URL: https://help.gitkraken.com/gitlens/gitlens-faq/
Description: Frequently asked questions about GitLens and GitKraken account integration.
-
-Last updated: July 2025
+Last updated: March 2026
Get answers to frequently asked questions about GitLens features, sign-in options, and GitKraken account integration.
@@ -975,7 +887,7 @@ Get answers to frequently asked questions about GitLens features, sign-in option
## What is GitLens Community vs GitLens Pro?
-Learn about the differences between the two versions on the [GitLens Community vs GitLens Pro](/gitlens/gitlens-community-vs-gitlens-pro) page.
+Learn about the differences between the two versions on the GitLens Community vs GitLens Pro (/gitlens/gitlens-community-vs-gitlens-pro) page.
***
@@ -988,17 +900,11 @@ To sign in with your GitKraken account:
- Click the GitLens icon in the sidebar.
- Under **GITKRAKEN ACCOUNT**, select `Sign In`.
-
-Sign in from the GitLens sidebar
-
You can also sign in via the VS Code Command Palette:
- Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
- Type and select `GitLens: Sign In to GitKraken...`.
-
-Sign in using the command palette
-
### Sign Out of GitLens
To sign out:
@@ -1006,17 +912,11 @@ To sign out:
- Click the GitLens icon in the sidebar.
- Under **GITKRAKEN ACCOUNT**, select `Sign Out`.
-
-Sign out from the GitLens sidebar
-
Or use the VS Code Command Palette:
- Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P`).
- Type and select `GitLens: Sign Out of GitKraken`.
-
-Sign out using the command palette
-
***
## How do I enable debug logging?
@@ -1049,19 +949,22 @@ Yes. Your GitLens Pro license is tied to your email address, not a specific devi
URL: https://help.gitkraken.com/gitlens/gitlens-features/
Description: Learn how to use GitLens autolinks, terminal links, powerful Git commands, remote provider integrations, and UI customizations to enhance your Git workflow in VS Code.
+Last updated: March 2026
-Last updated: June 2025
+Features marked with `PRO` require a Pro, Advanced, Business, or Enterprise plan (https://www.gitkraken.com/gitlens/pricing?source=help_center&product=gitlens) for use on privately hosted repositories.
-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.
+Features marked with `PREVIEW` require a GitKraken Account, with access based on your plan level (https://www.gitkraken.com/gitlens/pricing?source=help_center&product=gitlens) (Community, Pro, etc).
-Features marked with `PREVIEW` require a GitKraken Account, with access based on your [plan level](https://www.gitkraken.com/gitlens/pricing?source=help_center&product=gitlens) (Community, Pro, etc).
+| Feature area | What it helps you do | Access notes |
+|---|---|---|
+| Revision Navigation | Compare file revisions and line changes | Available in GitLens |
+| Current Line Blame | See who changed the current line and when | Available in GitLens |
+| Git CodeLens | Inspect commit context from the editor | Available in GitLens |
+| Remote integrations | Open files, commits, and branches on connected hosts | Some actions require connected providers |
***
-## Revision Navigation
-
-
-Step through revisions using built-in navigation commands
+## How to Navigate Revisions
Revision Navigation allows you to quickly compare different versions of a file or specific lines.
@@ -1090,12 +993,9 @@ Compare the current file with any revision of the same file.
***
-## Current Line Blame
-
-
-Blame annotation showing author, date, and commit message
+## How to Use Current Line Blame
-Current Line Blame adds a subtle, [customizable](/gitlens/settings/#current-line-blame-settings), and [themable](/gitlens/settings/#themable-colors) annotation at the end of the active line.
+Current Line Blame adds a subtle, customizable (/gitlens/settings/#current-line-blame-settings), and themable (/gitlens/settings/#themable-colors) annotation at the end of the active line.
By default, the annotation displays:
@@ -1111,10 +1011,7 @@ You can control visibility with the command:
## Git CodeLens
-
-Inline Git insights for authorship and history
-
-Git CodeLens displays inline Git insights at the top of each file and above code blocks (enabled by [default](/gitlens/settings/#git-codelens-settings), and [customizable](/gitlens/settings/#git-codelens-settings)).
+Git CodeLens displays inline Git insights at the top of each file and above code blocks (enabled by default (/gitlens/settings/#git-codelens-settings), and customizable (/gitlens/settings/#git-codelens-settings)).
### CodeLens Types
@@ -1129,7 +1026,7 @@ Displays the number of contributors and the most prominent author.
### CodeLens Behavior
-Click behavior for each CodeLens is fully [customizable](/gitlens/settings/#git-codelens-settings). You can choose from:
+Click behavior for each CodeLens is fully customizable (/gitlens/settings/#git-codelens-settings). You can choose from:
- Toggle file blame annotations
- Compare the current commit to the previous one
@@ -1145,9 +1042,6 @@ Shortcut: `Shift+Alt+B`
## Status Bar Blame
-
-Quick access to blame details in the VS Code status bar
-
The **Status Bar Blame** displays Git blame details for the current line directly in the VS Code status bar. This feature is enabled by default and fully customizable.
### Default Behavior
@@ -1173,18 +1067,12 @@ You can configure what happens when the status bar item is clicked:
## Hovers
-GitLens provides rich, [customizable](/gitlens/settings/#hover-settings) hover annotations to surface Git information directly in your editor. These hovers are enabled by default and support both blame and diff insights.
+GitLens provides rich, customizable (/gitlens/settings/#hover-settings) hover annotations to surface Git information directly in your editor. These hovers are enabled by default and support both blame and diff insights.
### Current Line Hovers
-
-Git blame hover shown over the current line
-
#### Details Hover
-
-Expanded commit info and quick actions
-
Displays detailed commit information for the current line.
Features:
@@ -1196,9 +1084,6 @@ _Open Changes_, _Blame Previous Revision_, _Open on Remote_, _Invite to Live Sha
#### Changes (Diff) Hover
-
-View the previous version of a changed line
-
Displays the previous version of the current line.
- Click **Changes** to run the _Open Changes_ command.
@@ -1206,16 +1091,10 @@ Displays the previous version of the current line.
### Annotation Hovers
-
-Hover insights while annotating with blame
-
Accessible when blame annotations are active, these hovers provide the same detail and diff options.
#### Details Hover
-
-Commit metadata and action menu per line
-
Shows rich commit details per line with:
- Automatic issue linking
@@ -1224,9 +1103,6 @@ Shows rich commit details per line with:
#### Changes (Diff) Hover
-
-Inline diff hover showing previous line content
-
Reveals the previous version of each annotated line.
- Click **Changes** to run _Open Changes_.
@@ -1236,16 +1112,13 @@ Reveals the previous version of each annotated line.
## File Blame
-
-View who last modified each line and when
-
-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.
+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.
### Features
-- Displays **commit message** and **commit date** per line (enabled by [default](/gitlens/settings/#file-blame-settings)).
+- Displays **commit message** and **commit date** per line (enabled by default (/gitlens/settings/#file-blame-settings)).
- Adds a **heatmap (age) indicator** along the right edge to show how recently each line was changed.
-_(See [File Heatmap](/gitlens/gitlens-features/#file-heatmap) for more info.)_
+_(See File Heatmap (/gitlens/gitlens-features/#file-heatmap) for more info.)_
- Easily toggle annotations with:
- **Command**: `gitlens.toggleFileBlame`
@@ -1256,12 +1129,9 @@ _(See [File Heatmap](/gitlens/gitlens-features/#file-heatmap) for more info.)_
## File Changes
-
-Highlight unpublished or most recent changes
-
The File Changes annotation highlights lines that have been changed either locally (unpublished) or by the most recent commit.
-This feature is [customizable](/gitlens/settings/#file-changes-settings) and [themable](/gitlens/settings/#themable-colors), and is designed for quick visual inspection of file updates.
+This feature is customizable (/gitlens/settings/#file-changes-settings) and themable (/gitlens/settings/#themable-colors), and is designed for quick visual inspection of file updates.
### Features
@@ -1273,14 +1143,11 @@ This feature is [customizable](/gitlens/settings/#file-changes-settings) and [th
## File Heatmap
-
-Visualize how recently each line was modified
-
The File Heatmap adds a color-coded bar to the edge of your file, helping you quickly spot older versus more recent changes.
### Features
-- Heatmap colors are [customizable](/gitlens/settings/#file-heatmap-settings) and reflect line age:
+- Heatmap colors are customizable (/gitlens/settings/#file-heatmap-settings) and reflect line age:
- **Hot (bright)** for recent changes
- **Cold (dim)** for older changes
_(Lines default to “cold” after 90 days.)_
@@ -1292,33 +1159,22 @@ _(Lines default to “cold” after 90 days.)_
## Code Suggest `PREVIEW`
-GitKraken Code Suggest simplifies code review by enabling you to propose edits across an entire project—not just the lines changed—in GitLens, GitKraken Desktop, or [gitkraken.dev](https://gitkraken.dev).
+GitKraken Code Suggest simplifies code review by enabling you to propose edits across an entire project—not just the lines changed—in GitLens, GitKraken Desktop, or gitkraken.dev (https://gitkraken.dev).
When a pull request is open, you can make suggestions that collaborators can review and apply directly to the PR.
-Note: Code Suggest is currently supported only for repositories hosted on github.com.
-
-
-Suggest changes beyond just modified lines
-
### How to Create a Code Suggestion
-1. Open the [GitLens Inspect Overview](/gitlens/side-bar/#overview) for the repository.
+1. Open the GitLens Inspect Overview (/gitlens/side-bar/#overview) for the repository.
2. Check out a branch that has an open pull request.
3. Click **Start Review for PR #PR**.
4. Modify and save any files to include in the suggestion.
5. When ready, select **Suggest Changes for PR**, add a title, and click **Create Code Suggestion**.
-
-Create a suggestion from your local changes
-
Once submitted, the pull request will receive a comment with two options:
- **Code Suggestion for #PR** — opens in gitkraken.dev
-- **Locally on your machine** — opens in GitLens or [GitKraken Desktop](/gitkraken-client/pull-requests/#review-code-and-suggest-changes)
-
-
-Collaborators can choose where to review and apply suggestions
+- **Locally on your machine** — opens in GitLens or GitKraken Desktop (/gitkraken-client/pull-requests/#review-code-and-suggest-changes)
### Accepting a Suggestion Locally
@@ -1327,18 +1183,12 @@ Collaborators can choose where to review and apply suggestions
3. Select **Apply** to apply the patch to your current branch.
Or use the dropdown to **Apply to a Branch**.
-
-Apply suggestions directly to a local or new branch
-
### Accepting a Suggestion on gitkraken.dev
1. Select **Code Suggestion for #PR** in the PR comment.
2. Review the changes on gitkraken.dev.
3. Click **Commit Suggestions** to commit the patch directly to the PR’s branch.
-
-Accept changes and push them to the remote branch
-
***
## Cloud Patches `PREVIEW`
@@ -1368,9 +1218,6 @@ To disable Cloud Patches, change the value to `false`.
Cloud Patches are accessible from the **Cloud Patches** view in the GitLens sidebar.
-
-Create a patch directly from your sidebar
-
You can create a Cloud Patch from:
- Working Changes
@@ -1380,9 +1227,6 @@ You can create a Cloud Patch from:
To create one, use **Share as Cloud Patch** from the command palette or the **Share** submenu in applicable GitLens views.
-
-Share patches from a variety of Git sources
-
#### Sharing Options
Choose how your patch can be accessed:
@@ -1393,26 +1237,15 @@ Choose how your patch can be accessed:
Cloud Patches shared with you appear under the **Shared with Me** section.
-Note: If you're a member of multiple organizations, you can switch organizations from the GitKraken Account view.
-
-
-Control access to shared patches by role
-
You can also apply Cloud Patches directly from a shared URL. Simply click or paste the link, then follow GitLens prompts to apply it to your working directory or to a new/existing branch.
-
-Apply patches seamlessly to your current repo
-
To delete a Cloud Patch, right-click it and choose **Delete Cloud Patch...**.
-
-Remove unused patches with one click
-
### Self-Hosting Cloud Patch Data
If you prefer not to store Cloud Patch data on GitKraken servers, you can configure GitLens to use your own AWS S3 storage.
-Learn how to configure this in our [Self-Hosting Guide](/gk-dev/gk-dev-home/#self-hosted).
+Learn how to configure this in our Self-Hosting Guide (/gk-dev/gk-dev-home/#self-hosted).
***
@@ -1420,9 +1253,6 @@ Learn how to configure this in our [Self-Hosting Guide](/gk-dev/gk-dev-home/#sel
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.
-
-Explore your full Git history at a glance
-
---
### How to Open the Commit Graph
@@ -1437,9 +1267,6 @@ Cmd/Ctrl + Shift + P
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.
-
-Launch the graph directly from the Command Palette
-
---
### Commit Graph Header
@@ -1455,13 +1282,6 @@ From here, you can:
- Click the branch name to switch branches
- Click **Fetch** to update commit data
-
-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.
-We welcome your input—join the discussion on GitHub.
-
### Configuration and Layout
The Commit Graph offers extensive layout and configuration options so you can tailor the view to fit your workflow.
@@ -1476,9 +1296,6 @@ All columns in the Commit Graph are fully customizable:
- 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.
-
-Customize visible columns with right-click options
-
---
#### Panel vs. Editor Layout
@@ -1495,9 +1312,6 @@ To switch layouts:
You can even open both layouts simultaneously.
-
-Choose where the graph displays: Panel or Editor
-
---
#### Compact Layout
@@ -1510,9 +1324,6 @@ For smaller screens or simplified views:
To enable the compact graph layout, right-click the **Graph** column header and select **Compact Graph Column Layout**.
-
-Enable compact mode for cleaner visuals
-
---
#### Scroll Markers
@@ -1525,10 +1336,7 @@ Scroll markers appear alongside the Commit Graph scrollbar to highlight:
They provide quick navigation to key locations like `HEAD` or specific refs.
-You can toggle scroll markers in [Commit Graph settings](/gitlens/gitlens-features/#settings).
-
-
-Navigate instantly using visual markers
+You can toggle scroll markers in Commit Graph settings (/gitlens/gitlens-features/#settings).
### Settings
@@ -1540,9 +1348,6 @@ Cmd/Ctrl + Shift + P
2. Search for:
`GitLens: Open Settings`
-
-Access GitLens settings from the Command Palette
-
---
### Rich Commit Search
@@ -1558,36 +1363,24 @@ Use the following search prefixes:
- `Change:`
- `@me` (to filter commits made by your user)
-
-Search commit history with advanced filtering
-
Use keyboard shortcuts to navigate results:
- F3 / Cmd+G — next result
- Shift+F3 / Shift+Cmd+G — previous result
- Hold Shift and click arrows to jump to first or last match
-
-Jump through results using keyboard or search controls
-
You can also refine results with:
- **Match all**
- **Match case**
- **Regular expression**
-
-Adjust search filters for more precision
-
---
### Full Context Menu Support
The Commit Graph supports right-click actions on branches, commits, tags, authors, and column headers.
-
-Use context menus for advanced Git actions
-
Popular options include:
- **Compare with Common Base** — View changes between the current and selected branches based on their shared ancestor.
@@ -1596,12 +1389,9 @@ Popular options include:
For GitHub and GitLab, GitLens displays a **Pull Request icon** on branches with active pull requests. To enable this:
-1. Connect your account using [rich integration settings](/gitlens/settings/#remote-provider-integration-settings).
+1. Connect your account using rich integration settings (/gitlens/settings/#remote-provider-integration-settings).
2. The icon will appear next to branches in the graph once linked.
-
-Active pull requests are shown with branch-level icons
-
---
### Hiding Remotes, Branches, or Tags
@@ -1611,9 +1401,6 @@ You can hide individual remotes, branches, or tags from the Commit Graph to redu
- **To hide**: Hover over any ref and click **Hide**.
- **To show again**: Use the **Hide** panel at the top of the graph and reselect the ref.
-
-Use the “Hide” option to declutter the graph
-
#### Filtering Options
You can further control what is shown using the filter dropdown:
@@ -1626,9 +1413,6 @@ You can further control what is shown using the filter dropdown:
- Stashes
- Option to **dim merge commits**
-
-Customize your view with filter presets
-
---
### Minimap (Experimental)
@@ -1639,9 +1423,6 @@ The **Minimap** gives you a visual summary of repository activity at a glance:
- Jump to any region in the graph using visual cues
- Toggle it via the **Minimap icon** in the top right
-
-Quickly navigate with the Commit Graph Minimap
-
#### Minimap Settings
Customize the Minimap via the **graph icon dropdown**:
@@ -1652,9 +1433,6 @@ Customize the Minimap via the **graph icon dropdown**:
- Show or hide:
- Markers for branches, tags, stashes, search results
-
-Choose your preferred Minimap display and markers
-
#### Minimap Legend
| Element | Description |
@@ -1675,10 +1453,7 @@ Note: We welcome your feedback on the Minimap. Share your thoughts on the GitLen
Launchpad organizes pull requests (PRs) by status to help you identify bottlenecks and take prioritized actions. This streamlined view allows you to manage PRs quickly, directly within VS Code.
-
-View and act on PRs based on current status
-
-Launchpad currently supports GitHub.com and GitLab.com repositories. To use it, connect your Git provider using the GitHub or GitLab Integration.
+Launchpad currently supports GitHub.com and GitLab.com repositories. To use it, connect your Git provider using the GitHub or GitLab Integration (https://help.gitkraken.com/gitlens/gitlens-features/#connecting-the-github-and-gitlab-integration).
---
@@ -1687,9 +1462,6 @@ Launchpad currently supports GitHub.com and GitLab.com repositories. To use it,
- From the **Command Palette**: `Command/Ctrl + Shift + P` → `GitLens: Open Launchpad`
- Or select the **Pull Request status bar item** in VS Code
-
-Open Launchpad from the status bar or Command Palette
-
---
### Using Launchpad
@@ -1709,15 +1481,9 @@ Click a PR to:
- Merge (if eligible)
- Switch to the branch or open in a worktree
+You can also start or review Code Suggestions (/gitlens/gitlens-features/#code-suggest-preview) directly from the PR action menu.
-Interact with pull requests directly in VS Code
-
-You can also start or review [Code Suggestions](/gitlens/gitlens-features/#code-suggest-preview) directly from the PR action menu.
-
-
-Suggest code edits from within the Launchpad
-
-*This feature is available through the [Gitkraken MCP](https://help.gitkraken.com/mcp/mcp-tools-reference/)*
+*This feature is available through the Gitkraken MCP (https://help.gitkraken.com/mcp/mcp-tools-reference/)*
---
@@ -1729,12 +1495,9 @@ Use the snooze icon to move less urgent PRs into the **Snoozed** group.
Click the icon again to unpin or unsnooze as needed.
-
-Pin or snooze PRs to manage your workflow
-
Note: Launchpad prioritizes items requiring action by elevating them to the top of the list. This behavior may change in future updates.
-This feature is only available on GitLens Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
***
@@ -1746,9 +1509,6 @@ To open Visual File History:
- Use the GitLens **Inspect Sidebar**, or
- From the **Command Palette**: `Cmd/Ctrl + Shift + P` → `GitLens: Show Visual File History View`
-
-Track authorship, size, and timing of file changes
-
---
### How to Read the Graph
@@ -1760,9 +1520,6 @@ Track authorship, size, and timing of file changes
Hover over a bubble or bar for detailed insights.
-
-View commit size, author, and message on hover
-
The Community plan supports Visual File History only on public and local repositories.
***
@@ -1777,9 +1534,6 @@ GitKraken AI enhances your development workflow with automated commit messages,
Automatically generate descriptive commit messages based on staged changes.
-
-AI-generated commit messages from staged changes
-
To use:
- Stage your changes.
- Open the **Home View** and click **Generate Commit Message**, or
@@ -1789,7 +1543,7 @@ GitKraken AI will analyze the diff of staged changes to generate a message. You
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
+- Additional `gitlens.ai` settings (/gitlens/gitlens-settings/#misc-settings) for provider and model 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.
@@ -1812,9 +1566,6 @@ Automatically generate meaningful stash descriptions to make your stashes easier
Let GitKraken AI help explain complex changes across your repo with natural language summaries.
-
-AI summaries in rendered markdown for improved clarity
-
✨**Explain** functionality provides markdown summaries for:
- Branches — ✨**Explain Branch**
- Working changes — ✨**Explain Working Changes**
@@ -1854,14 +1605,14 @@ Automatically generate detailed and structured changelogs from a set of selected
- **Commit Graph**: Select multiple commits, right-click, then choose **Generate Changelog**
- **Command Palette**: `GitLens: Generate Changelog from Commits`
-More questions about GitKraken AI? See the GitKraken AI FAQ for additional details.
+More questions about GitKraken AI? See the GitKraken AI FAQ (https://help.gitkraken.com/general/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.
-*This feature is available through the [Gitkraken MCP](https://help.gitkraken.com/mcp/mcp-tools-reference/)*
+*This feature is available through the Gitkraken MCP (https://help.gitkraken.com/mcp/mcp-tools-reference/)*
-Join the [Commit Composer discussion](https://github.com/gitkraken/vscode-gitlens/discussions/4530) and provide feedback.
+Join the Commit Composer discussion (https://github.com/gitkraken/vscode-gitlens/discussions/4530) and provide feedback.
#### Interactive Draft Commits
@@ -1919,7 +1670,7 @@ Commit Composer is also more discoverable, with a new button on the WIP row in t
## Git 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.
+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.
---
@@ -1944,7 +1695,7 @@ Adds a [customizable](/gitlens/settings/#git-command-palette-settings) Git Comma
-Refer to the [Git log documentation](https://git-scm.com/docs/git-log) for advanced usage.
+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.
@@ -1956,10 +1707,6 @@ Refer to the [Git log documentation](https://git-scm.com/docs/git-log) for advan
### Quick Stash Access
-
-
-
-
- Adds a _Show Stashes_ command (`gitlens.showQuickStashList`) to show a quick pick menu to explore your stashes.
---
@@ -1968,14 +1715,10 @@ Refer to the [Git log documentation](https://git-scm.com/docs/git-log) for advan
- Adds a _Show Repository Status_ command (`gitlens.showQuickRepoStatus`) to show a quick pick menu for visualizing the current repository status.
-
-
---
## Interactive Rebase Editor
-
-
Adds a user-friendly interactive rebase editor to easily configure an interactive rebase session:
- Quickly re-order, edit, squash, and drop commits.
@@ -2001,24 +1744,18 @@ git config --global sequence.editor "code --wait"
Use autolinks to convert external references—such as Jira issues or Zendesk tickets—into clickable links directly from commit messages.
-
-Example of autolinks in commit messages
-
## Terminal Links
-
-Autolinks in the integrated terminal
-
Terminal links optionally provide clickable references in the integrated terminal:
-- [Branches, tags, and commit ranges](/gitlens/settings/#terminal-links-settings): Quickly explore their commit history.
-- [Individual commits](/gitlens/settings/#terminal-links-settings): Review commit details and take further action.
+- Branches, tags, and commit ranges (/gitlens/settings/#terminal-links-settings): Quickly explore their commit history.
+- Individual commits (/gitlens/settings/#terminal-links-settings): Review commit details and take further action.
***
## Remote Provider Integrations
-GitLens provides rich integrations with many remote providers, including GitHub, GitHub Enterprise, GitLab, Gitea, Gerrit, Bitbucket, Bitbucket Server, and Azure DevOps. You can also define [custom remote providers](/gitlens/settings/#remote-provider-integration-settings) or [remote providers with custom domains](/gitlens/settings/#remote-provider-integration-settings).
+GitLens provides rich integrations with many remote providers, including GitHub, GitHub Enterprise, GitLab, Gitea, Gerrit, Bitbucket, Bitbucket Server, and Azure DevOps. You can also define custom remote providers (/gitlens/settings/#remote-provider-integration-settings) or remote providers with custom domains (/gitlens/settings/#remote-provider-integration-settings).
Basic integrations offer issue and pull request autolinking. Richer integrations, like GitHub or GitLab, include:
@@ -2049,7 +1786,7 @@ These integrations also support various commands to open or copy URLs for files,
### Connecting the GitHub and GitLab Integration
-The GitHub and GitLab integrations connect through your GitKraken account at [gitkraken.dev](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
+The GitHub and GitLab integrations connect through your GitKraken account at gitkraken.dev (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
To connect an integration:
@@ -2057,16 +1794,10 @@ To connect an integration:
2. Run `GitLens: Manage Integrations`.
3. Alternatively, open **GitKraken Account** from the GitLens Activity Bar and select **Integrations**.
-
-Connect integrations from the GitKraken dashboard
-
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.
Finish the process by selecting **Complete Setup** to return to VS Code and begin using the integrations.
-
-Manage your connected integrations
-
Community users are limited to basic functionality only.
## GitHub Enterprise Server and GitLab Self-Managed Integration `PRO`
@@ -2075,9 +1806,6 @@ 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.
-
-Enhanced hover integration with GitHub Enterprise and GitLab Self-Managed
-
### Connecting GitHub Enterprise Server or GitLab Self-Managed
To connect either integration:
@@ -2098,35 +1826,26 @@ Or
```
3. Open a repository from GitHub Enterprise Server or GitLab Self-Managed in VS Code.
-4. Go to the [Remotes View](/gitlens/side-bar/#remotes-view).
+4. Go to the Remotes View (/gitlens/side-bar/#remotes-view).
5. Select **Connect to Remote**.
- If this option is missing, verify the format in your `settings.json` matches the example above.
-
-Connect to a GitHub Enterprise or GitLab Self-Managed instance
-
6. Provide a Personal Access Token (PAT) with the required scopes when prompted, and press **Enter** to complete the connection.
***
## Jira Integration `PRO`
-The Jira Integration, connected through your GitKraken Account, enables Jira [Autolinks](/gitlens/gitlens-features#autolinks) wherever autolinks are supported in GitLens. Once connected, GitLens automatically converts Jira issue keys (e.g., `ABC-123`) in commit messages into clickable links.
-
-
-Jira autolinks in commit messages
+The Jira Integration, connected through your GitKraken Account, enables Jira Autolinks (/gitlens/gitlens-features#autolinks) wherever autolinks are supported in GitLens. Once connected, GitLens automatically converts Jira issue keys (e.g., `ABC-123`) in commit messages into clickable links.
-This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
To connect the integration:
1. Open the GitLens Sidebar.
2. From the GitKraken Account view, select **Cloud Integrations**.
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
+4. Alternatively, visit your Integration Settings (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens) in a browser.
***
@@ -2163,38 +1882,29 @@ GitLens provides powerful commands to improve your workflow:
Deep Links are URLs that open specific GitLens resources, improving collaboration by sharing direct links to repositories, files, comparisons, and more. Resources that support Deep Linking include:
-- **Search & Compare** — Link to comparisons in the [Search & Compare view](/gitlens/side-bar/#search-compare-view). Right-click a comparison, hover over _Share_, and select _Copy Link to Comparison_.
-- **GitKraken Workspaces** — Link to a [GitKraken Workspace](/gitlens/side-bar/#workspaces-☁%ef%b8%8f). Right-click a Workspace, hover over _Share_, and select _Copy Link to Workspace_.
-- **Commit Graph** — Link to remote repositories, commits, branches, and tags in the [Commit Graph](gitlens/gitlens-features/#commit-graph-%60pro%60). Right-click the resource, hover over _Share_, and select _Copy Link to _.
+- **Search & Compare** — Link to comparisons in the Search & Compare view (/gitlens/side-bar/#search-compare-view). Right-click a comparison, hover over _Share_, and select _Copy Link to Comparison_.
+- **GitKraken Workspaces** — Link to a GitKraken Workspace (/gitlens/side-bar/#workspaces-☁%ef%b8%8f). Right-click a Workspace, hover over _Share_, and select _Copy Link to Workspace_.
+- **Commit Graph** — Link to remote repositories, commits, branches, and tags in the Commit Graph (gitlens/gitlens-features/#commit-graph-%60pro%60). Right-click the resource, hover over _Share_, and select _Copy Link to _.
- **Files or Lines** — Link to specific files or lines of code. Right-click highlighted lines or a file, hover over _Share_, and select _Copy vscode.dev Link_.
-- **Cloud Patches** — Link to a [Cloud Patch](/gitlens/gitlens-features/#cloud-patches-preview-%e2%98%81%ef%b8%8f). After generating a Cloud Patch, click _Copy Link_ from the success prompt.
-
-
-Example of generating and using Deep Links
+- **Cloud Patches** — Link to a Cloud Patch (/gitlens/gitlens-features/#cloud-patches-preview-%e2%98%81%ef%b8%8f). After generating a Cloud Patch, click _Copy Link_ from the success prompt.
***
## Menus & Toolbars
-
-GitLens menu and toolbar options
-
-GitLens provides [customizable](/gitlens/gitlens-settings/#elementor-toc__heading-anchor-16) menu and toolbar contributions to let you control where GitLens commands appear. You can easily manage these settings via the [interactive settings editor](/gitlens/gitlens-settings/).
+GitLens provides customizable (/gitlens/gitlens-settings/#elementor-toc__heading-anchor-16) menu and toolbar contributions to let you control where GitLens commands appear. You can easily manage these settings via the interactive settings editor (/gitlens/gitlens-settings/).
For example, disabling **Add to the editor group toolbar** removes those items from the toolbar:
-
-Editor group toolbar items removed
-
You can also expand each section to customize visibility and placement more granularly.
***
## Modes
-GitLens supports [user-defined](#modes-settings- 'Jump to the Modes settings') modes for quickly toggling between sets of settings.
+GitLens supports user-defined (#modes-settings- 'Jump to the Modes settings') modes for quickly toggling between sets of settings.
-- Shows the active mode in the **status bar** ([optional](#modes-settings- 'Jump to the Modes settings'), enabled by default)
+- Shows the active mode in the **status bar** (optional (#modes-settings- 'Jump to the Modes settings'), enabled by default)
- **Toggle Review Mode** (`gitlens.toggleReviewMode`) — Quickly toggle Review mode.
- **Switch Mode** (`gitlens.switchMode`) — Quickly switch between modes.
- **Zen Mode** — Disables many visual elements for a focused experience.
@@ -2218,36 +1928,38 @@ VS Code 1.86 or later is required for these capabilities.
URL: https://help.gitkraken.com/gitlens/home-view/
Description: Learn how the GitLens Home View helps you track current work, plan next steps, and review recent activity
+Last updated: March 2026
+
+**Requirements:**
+- **Requires GitLens:** GitLens installed in VS Code, Cursor, Windsurf, Trae, or Kiro
+- **Works best with:** Connected GitHub, GitLab, or Jira integrations
+- **Plan notes:** Some Home View actions, including Launchpad-related features, may require Pro, Advanced, Business, or Enterprise
-Last updated: July 2025
+| Home View section | Purpose | Requires |
+|---|---|---|
+| Repository and branch | Shows current repo state, branch, and sync actions | An open repository |
+| Launchpad | Highlights pull requests and assigned issues | Connected integrations; some actions require paid access |
+| Recent | Returns to recent branches, worktrees, and pull requests | GitLens activity history |
## Overview
-Open the Home View in GitLens
+Open the Home View in GitLens (vscode://eamodio.gitlens/link/command/home)
The GitLens Home View helps you stay focused by organizing your work around three key questions:
-1. [What am I actively working on now?](/gitlens/home-view/#View-Your-Active-Repository-and-Branch)
-2. [What should I work on next?](/gitlens/home-view/#launchpad-section)
-3. [What have I worked on recently?](/gitlens/home-view/#recent-section)
+1. What am I actively working on now? (/gitlens/home-view/#View-Your-Active-Repository-and-Branch)
+2. What should I work on next? (/gitlens/home-view/#launchpad-section)
+3. What have I worked on recently? (/gitlens/home-view/#recent-section)
Each section in the Home View offers direct insights and actionable links to help you manage tasks efficiently across your repositories.
-
-
-
-Video overview: Introducing the GitLens Home View
-
## Connect to GitHub, GitLab, and Jira
GitLens integrates with popular code hosting and issue tracking services—including GitHub, GitLab, and Jira—to help you monitor branches, track issues, and manage pull requests.
You can connect integrations directly from the top of the Home View.
-Some advanced integration features are available with GitLens Pro features.
-
-
-GitLens Home View integration panel
+Some advanced integration features are available with GitLens Pro features (https://help.gitkraken.com/gitlens/gitlens-community-vs-gitlens-pro/).
## View Your Active Repository and Branch
@@ -2257,10 +1969,7 @@ This section gives you quick access to:
- Sync actions (push, pull, fetch)
- Switch active repositories
- View working directory changes
-- Launch the GitLens Commit Graph
-
-
-GitLens Home View active repository section
+- Launch the GitLens Commit Graph (https://help.gitkraken.com/gitlens/gitlens-home/#commit-graph)
When you connect integrations and associate issues or pull requests with your current branch, GitLens Pro groups them for streamlined access. You can check pull request statuses, resume reviews, or revisit linked issue details—all from within this view.
@@ -2268,16 +1977,13 @@ If a pull request isn’t open or your branch isn't yet linked to an issue, GitL
## Plan Next Steps with Launchpad Pro
-This feature is available with GitLens Pro or higher subscription tiers.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
The Launchpad section highlights upcoming priorities to help you decide what to work on next. It surfaces pull requests needing your review and lets you start new work by creating branches and worktrees for issues assigned to you.
-
-GitLens Home View Launchpad section
-
### Review Pull Request Statuses
-The Launchpad Summary shows how many pull requests are blocking your team and provides reasons for each. With GitLens Pro, you can click a status to open the related pull request in Launchpad. You can then take actions like checking out the PR in a worktree, enabling fast reviews without changing your main branch.
+The Launchpad Summary shows how many pull requests are blocking your team and provides reasons for each. With GitLens Pro, you can click a status to open the related pull request in Launchpad (https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro). You can then take actions like checking out the PR in a worktree, enabling fast reviews without changing your main branch.
### Start Work on an Issue
@@ -2289,19 +1995,17 @@ The Recent section minimizes context switching by showing your recent branches,
By default, the section collapses details like associated issues and branches to reduce clutter. Click any item to expand it for more context.
-
-GitLens Home View recent activity section
-
---
## GitLens Integrations
URL: https://help.gitkraken.com/gitlens/gl-integrations/
Description: Explore GitLens integrations with remote providers
+Last updated: March 2026
-Last updated: July 2025
+This page explains which remote services GitLens integrates with across supported GitLens IDEs, what each integration enables, and how to connect supported providers. Use it when you need pull request, issue, repository, or Launchpad features that depend on an authenticated Git host or Jira connection.
-GitLens supports a wide range of remote providers to enhance your Git workflow inside Visual Studio Code. Supported platforms include:
+Supported platforms include:
- GitHub (including GitHub Enterprise)
- GitLab
@@ -2310,7 +2014,7 @@ GitLens supports a wide range of remote providers to enhance your Git workflow i
- Bitbucket (Cloud and Server)
- Azure DevOps
-You can also define [custom remote providers or providers with custom domains](/gitlens/settings/#remote-provider-integration-settings).
+You can also define custom remote providers or providers with custom domains (/gitlens/settings/#remote-provider-integration-settings).
## Integration Capabilities
@@ -2370,25 +2074,19 @@ You can use the following GitLens commands to interact with files, commits, and
### Connect GitHub or GitLab Integration
-To connect GitHub or GitLab to GitLens, you'll use your GitKraken account via the [GitLens integrations dashboard](https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
+To connect GitHub or GitLab to GitLens, you'll use your GitKraken account via the GitLens integrations dashboard (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens).
#### 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**.
-
-Navigate to Integrations in the GitKraken Account menu
-
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.
-
-Select the service you want to integrate and finish setup
-
Community users are limited to basic functionality only.
## GitHub Enterprise Server and GitLab Self-Managed Integration `PRO`
@@ -2401,9 +2099,6 @@ Once authenticated, GitLens enhances autolinks for these services in hover cards
- Links to related pull requests and issues
- Pull request and issue details directly in the Sidebar views
-
-Enhanced hover cards with issue and PR metadata
-
### Connect GitHub Enterprise Server or GitLab Self-Managed
To connect a self-hosted GitHub or GitLab instance:
@@ -2422,12 +2117,9 @@ Or for GitLab:
```
3. Open the self-hosted repository in Visual Studio Code
-4. Open the [Remotes View](/gitlens/side-bar/#remotes-view)
+4. Open the Remotes View (/gitlens/side-bar/#remotes-view)
5. Click **Connect to Remote**
-
-Use the plug icon to connect a self-managed remote
-
> If the **Connect to Remote** option doesn't appear, double-check that your JSON entry matches the example format.
6. When prompted, provide a Personal Access Token (PAT) with the required scopes and press **Enter** to complete setup
@@ -2438,10 +2130,7 @@ Use the plug icon to connect a self-managed remote
GitLens Pro supports integration with Jira Cloud via your GitKraken Account. This allows GitLens to automatically link Jira issue keys (e.g., `ABC-123`) in commit messages and views wherever autolinks are supported.
-
-Jira issues auto-linked in GitLens hovers and views
-
-This feature is only available for Pro subscription tiers or higher.
+This feature is available on Pro, Advanced, Business, and Enterprise plans.
### Connect the Jira Integration
@@ -2450,10 +2139,7 @@ This feature is only available for Pro subscription tiers or higher.
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
+You can also configure this via the Integration Settings (https://gitkraken.dev/settings/integrations?source=help_center&product=gitlens) in a browser.
---
@@ -2461,14 +2147,11 @@ Jira integration via GitLens Cloud Integrations panel
URL: https://help.gitkraken.com/gitlens/gl-interactive-code-history/
Description: Learn how GitLens helps you explore and understand your repository’s commit history.
+Last updated: March 2026
-Last updated: July 2025
-
+GitLens helps users understand code history through Commit Graph, GitLens Inspect, inline blame, and hovers across supported GitLens IDEs. Use this overview when you need to choose the right GitLens history view before investigating authorship, prior changes, or repository context.
-
-
-
-Understanding code history in large repositories can be challenging, especially with multiple branches and contributors. GitLens helps simplify this process by providing tools that surface meaningful context:
+Understanding code history in large repositories can be challenging, especially with multiple branches and contributors. GitLens provides tools that surface meaningful context:
- **Commit Graph** – Visualize the structure of your repository.
- **GitLens Inspect** – Drill into file and line-level history.
@@ -2476,6 +2159,18 @@ Understanding code history in large repositories can be challenging, especially
These features make it easier to navigate your repository, understand changes, and make informed decisions about your code.
+## When to Use Commit Graph
+
+Use Commit Graph when you need repository-wide history, branch relationships, merge context, or a visual view of how work diverged over time.
+
+## When to Use GitLens Inspect
+
+Use GitLens Inspect when you want commit, file, or line details for the code currently in front of you without switching to a repository-wide history view.
+
+## When Inline Blame and Hovers Are Enough
+
+Use Inline Blame and hovers when you only need quick authorship, timing, or commit context for the current line before deciding whether to open a deeper history view.
+
---
## GitLens Release Notes
@@ -2483,14 +2178,14 @@ These features make it easier to navigate your repository, understand changes, a
URL: https://help.gitkraken.com/gitlens/gitlens-release-notes-current/
Description: GitLens Release Notes
-Find out what’s new, what’s fixed, or just take a trip down memory lane remembering those bugs of yesterday.
+This page lists the current GitLens release notes, including new features, changes, fixes, and removals for each released version. Use it when you need to confirm when a GitLens capability shipped, changed behavior, or became available in a specific release.
-Check out our [Changelog](https://github.com/gitkraken/vscode-gitlens/blob/main/CHANGELOG.md) to see linked issues and past changes.
+Check out our Changelog (https://github.com/gitkraken/vscode-gitlens/blob/main/CHANGELOG.md) to see linked issues and past changes.
-Install Current Version Now
+Install Current Version Now (https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens)
-Features marked with `PRO` require a [trial or paid plan](https://www.gitkraken.com/gitlens/pricing) for use on privately hosted repos \
-Features marked with `PREVIEW` require a GitKraken Account, with access level based on your [plan](https://www.gitkraken.com/gitlens/pricing), e.g. Community, Pro, etc
+Features marked with `PRO` require a trial or paid plan (https://www.gitkraken.com/gitlens/pricing) for use on privately hosted repos \
+Features marked with `PREVIEW` require a GitKraken Account, with access level based on your plan (https://www.gitkraken.com/gitlens/pricing), e.g. Community, Pro, etc
---
@@ -2524,27 +2219,27 @@ The Welcome view is now its own standalone view, separate from Home, so it won't
### Added
-- Adds support for Claude Sonnet 4.6, Claude Opus 4.6, Gemini 3.1 Pro Preview, and Gemini 3.1 Flash-Lite Preview AI models ([#4991](https://github.com/gitkraken/vscode-gitlens/issues/4991))
-- Adds basic support for Git submodules — including repository discovery, tracking, and UI icons and tooltips to distinguish submodules in views and quick picks ([#1048](https://github.com/gitkraken/vscode-gitlens/issues/1048), [#1803](https://github.com/gitkraken/vscode-gitlens/issues/1803))
+- Adds support for Claude Sonnet 4.6, Claude Opus 4.6, Gemini 3.1 Pro Preview, and Gemini 3.1 Flash-Lite Preview AI models (#4991 (https://github.com/gitkraken/vscode-gitlens/issues/4991))
+- Adds basic support for Git submodules — including repository discovery, tracking, and UI icons and tooltips to distinguish submodules in views and quick picks (#1048 (https://github.com/gitkraken/vscode-gitlens/issues/1048), #1803 (https://github.com/gitkraken/vscode-gitlens/issues/1803))
### Changed
-- Improves tracking for connecting flow actions by adding ide attributes to gk.dev links ([#4905](https://github.com/gitkraken/vscode-gitlens/issues/4905))
-- Refactors the Welcome view to be a standalone view separate from the _Home_ view, improving modularity and allowing the Welcome walkthrough to be displayed independently without requiring the Welcome Overlay ([#4970](https://github.com/gitkraken/vscode-gitlens/issues/4970))
-- Improves the quality of output when recomposing branches in the _Commit Composer_ by including commit messages of the previous commits as context ([#4874](https://github.com/gitkraken/vscode-gitlens/issues/4874))
-- Changes logging to use VS Code's native LogOutputChannel — the custom output level setting has been deprecated in favor of native VS Code log level controls
-- Switches out deprecated Bitbucket provider API method ([#4967](https://github.com/gitkraken/vscode-gitlens/issues/4967))
+- Improves tracking for connecting flow actions by adding ide attributes to gk.dev links (#4905 (https://github.com/gitkraken/vscode-gitlens/issues/4905))
+- Refactors the Welcome view to be a standalone view separate from the _Home_ view, improving modularity and allowing the Welcome walkthrough to be displayed independently without requiring the Welcome Overlay (#4970 (https://github.com/gitkraken/vscode-gitlens/issues/4970))
+- Improves the quality of output when recomposing branches in the _Commit Composer_ by including commit messages of the previous commits as context (#4874 (https://github.com/gitkraken/vscode-gitlens/issues/4874))
+- Changes logging to use VS Code's native LogOutputChannel — the custom output level setting has been deprecated in favor of native VS Code log level controls
+- Switches out deprecated Bitbucket provider API method (#4967 (https://github.com/gitkraken/vscode-gitlens/issues/4967))
- Improves performance of the file system provider by adding an LRU cache to the search tree
- Improves Git shell operations by converting synchronous file system calls to async
### Fixed
-- Fixes an issue in the _Start Review_ command where it opens the wrong branch with GitLab repos ([#4975](https://github.com/gitkraken/vscode-gitlens/issues/4975))
-- Fixes an issue where authentication errors were not properly displayed in _Launchpad_ when GitLab integration credentials were revoked ([#4944](https://github.com/gitkraken/vscode-gitlens/issues/4944))
-- Fixes an issue where stashing only unstaged changes could incorrectly stash everything ([#4503](https://github.com/gitkraken/vscode-gitlens/issues/4503))
-- Fixes an issue where Jira and Linear issues were not shown on the _Commit Graph_ unless a Git hosting integration (e.g. GitHub) was also connected ([#4640](https://github.com/gitkraken/vscode-gitlens/issues/4640))
-- Fixes highlighting delays that can occur in _Commit Composer_ when selecting large commits ([#4872](https://github.com/gitkraken/vscode-gitlens/issues/4872))
-- Fixes repeated warnings about large token usage in the same session in _Commit Composer_ ([#4800](https://github.com/gitkraken/vscode-gitlens/issues/4800))
+- Fixes an issue in the _Start Review_ command where it opens the wrong branch with GitLab repos (#4975 (https://github.com/gitkraken/vscode-gitlens/issues/4975))
+- Fixes an issue where authentication errors were not properly displayed in _Launchpad_ when GitLab integration credentials were revoked (#4944 (https://github.com/gitkraken/vscode-gitlens/issues/4944))
+- Fixes an issue where stashing only unstaged changes could incorrectly stash everything (#4503 (https://github.com/gitkraken/vscode-gitlens/issues/4503))
+- Fixes an issue where Jira and Linear issues were not shown on the _Commit Graph_ unless a Git hosting integration (e.g. GitHub) was also connected (#4640 (https://github.com/gitkraken/vscode-gitlens/issues/4640))
+- Fixes highlighting delays that can occur in _Commit Composer_ when selecting large commits (#4872 (https://github.com/gitkraken/vscode-gitlens/issues/4872))
+- Fixes repeated warnings about large token usage in the same session in _Commit Composer_ (#4800 (https://github.com/gitkraken/vscode-gitlens/issues/4800))
- Fixes an issue where MCP registration can stop working if CLI binary goes missing after the CLI was successfully installed
- Fixes an issue where continuing a paused revert operation would incorrectly abort instead of continuing
- Fixes an issue with rebase todo parsing when using newer Git versions that use `#` prefixes in commit messages
@@ -2617,10 +2312,10 @@ Sidebar views like Commits, Branches, and Stashes have been optimized by reducin
### Added
-- Adds support for AI ignore files (`.aiignore`, `.cursorignore`, `.aiexclude`) and `gitlens.ai.exclude.files` setting to filter sensitive data from AI prompts, and smart diff truncation that prioritizes dropping low-value files when prompts exceed token limits ([#4916](https://github.com/gitkraken/vscode-gitlens/issues/4916))
-- Adds conversation threading to _Commit Composer_ auto-compose for improved outcomes ([PR #4900](https://github.com/gitkraken/vscode-gitlens/pull/4900))
-- Adds an option to filter tree views to exclude worktrees, allowing users to show all repositories except worktrees whose main repository is also open ([#4952](https://github.com/gitkraken/vscode-gitlens/issues/4952))
-- Adds commit signature verification with support for GPG, SSH, and X.509 formats ([#4552](https://github.com/gitkraken/vscode-gitlens/issues/4552), [#2363](https://github.com/gitkraken/vscode-gitlens/issues/2363))
+- Adds support for AI ignore files (`.aiignore`, `.cursorignore`, `.aiexclude`) and `gitlens.ai.exclude.files` setting to filter sensitive data from AI prompts, and smart diff truncation that prioritizes dropping low-value files when prompts exceed token limits (#4916 (https://github.com/gitkraken/vscode-gitlens/issues/4916))
+- Adds conversation threading to _Commit Composer_ auto-compose for improved outcomes (PR #4900 (https://github.com/gitkraken/vscode-gitlens/pull/4900))
+- Adds an option to filter tree views to exclude worktrees, allowing users to show all repositories except worktrees whose main repository is also open (#4952 (https://github.com/gitkraken/vscode-gitlens/issues/4952))
+- Adds commit signature verification with support for GPG, SSH, and X.509 formats (#4552 (https://github.com/gitkraken/vscode-gitlens/issues/4552), #2363 (https://github.com/gitkraken/vscode-gitlens/issues/2363))
- Adds verification badges and detailed tooltips to the _Commit Details_ and _Graph Details_ views
- Adds signature indicator icon to inline blame hovers
- Adds `${signature}` token to default commit and status tooltip formats in views and the _Commit Graph_
@@ -2630,37 +2325,37 @@ Sidebar views like Commits, Branches, and Stashes have been optimized by reducin
### Changed
- Significantly improves performance and reduces overhead, especially with worktrees
-- Improves performance when opening repositories with worktrees by sharing cached Git data across them ([#4929](https://github.com/gitkraken/vscode-gitlens/issues/4929))
-- Improves responsiveness by adding priority-based Git process scheduling and smarter repository discovery ([#4930](https://github.com/gitkraken/vscode-gitlens/issues/4930))
+- Improves performance when opening repositories with worktrees by sharing cached Git data across them (#4929 (https://github.com/gitkraken/vscode-gitlens/issues/4929))
+- Improves responsiveness by adding priority-based Git process scheduling and smarter repository discovery (#4930 (https://github.com/gitkraken/vscode-gitlens/issues/4930))
- Adds a `gitlens.advanced.git.maxConcurrentProcesses` setting to specify the maximum number of background Git processes that can run concurrently
-- Improves file system event handling performance by optimizing Git ignore rule processing ([#4919](https://github.com/gitkraken/vscode-gitlens/issues/4919))
-- Improves view update performance by skipping refreshes for hidden views and preventing unnecessary auto-expand with multiple repositories ([#4928](https://github.com/gitkraken/vscode-gitlens/issues/4928))
-- Moves GitLens-specific metadata (merge targets, issues, activity) to a dedicated `.git/gk/config` file to avoid modifying `.git/config` ([#4968](https://github.com/gitkraken/vscode-gitlens/issues/4968))
+- Improves file system event handling performance by optimizing Git ignore rule processing (#4919 (https://github.com/gitkraken/vscode-gitlens/issues/4919))
+- Improves view update performance by skipping refreshes for hidden views and preventing unnecessary auto-expand with multiple repositories (#4928 (https://github.com/gitkraken/vscode-gitlens/issues/4928))
+- Moves GitLens-specific metadata (merge targets, issues, activity) to a dedicated `.git/gk/config` file to avoid modifying `.git/config` (#4968 (https://github.com/gitkraken/vscode-gitlens/issues/4968))
- Eliminates unnecessary Git repository change events previously triggered by metadata updates
- Improves stash loading performance by deferring file detail loading (requires the `gitlens.advanced.commits.delayLoadingFileDetails` setting to be enabled)
-- Improves commit message instructions in _Commit Composer_ auto-compose for better consistency ([PR #4888](https://github.com/gitkraken/vscode-gitlens/pull/4888))
-- Overhauls _Git Command Palette_ quick wizards with scope-based progress tracking and modular sub-commands for branch, stash, remote, tag, and worktree operations ([#4927](https://github.com/gitkraken/vscode-gitlens/issues/4927))
+- Improves commit message instructions in _Commit Composer_ auto-compose for better consistency (PR #4888 (https://github.com/gitkraken/vscode-gitlens/pull/4888))
+- Overhauls _Git Command Palette_ quick wizards with scope-based progress tracking and modular sub-commands for branch, stash, remote, tag, and worktree operations (#4927 (https://github.com/gitkraken/vscode-gitlens/issues/4927))
- Improves worktree naming for detached states by including the folder name for better context
-- Excludes worktrees from repository pickers in commands where selecting a worktree would be inappropriate ([#4931](https://github.com/gitkraken/vscode-gitlens/issues/4931))
+- Excludes worktrees from repository pickers in commands where selecting a worktree would be inappropriate (#4931 (https://github.com/gitkraken/vscode-gitlens/issues/4931))
- Prevents repositories from automatically opening when an opened file is git-ignored
-- Stops creating new GitHub sessions via VS Code built-in authentication; new connections now always use the GKDev flow, while existing built-in sessions are still used if available ([#4881](https://github.com/gitkraken/vscode-gitlens/issues/4881))
+- Stops creating new GitHub sessions via VS Code built-in authentication; new connections now always use the GKDev flow, while existing built-in sessions are still used if available (#4881 (https://github.com/gitkraken/vscode-gitlens/issues/4881))
### Fixed
-- Fixes potential deadlocks during node loading in views ([#4928](https://github.com/gitkraken/vscode-gitlens/issues/4928))
-- Fixes an issue where the GitKraken MCP installation could fail or conflict across remote environments like WSL, SSH, or containers ([#4918](https://github.com/gitkraken/vscode-gitlens/issues/4918))
-- Fixes an issue where diffing untracked files in the _Commit Composer_ could trigger unwanted file system events ([#4917](https://github.com/gitkraken/vscode-gitlens/issues/4917))
-- Fixes an issue where a single-selected commit in the _Commit Composer_ would not get proper highlighting ([#4899](https://github.com/gitkraken/vscode-gitlens/issues/4899))
-- Fixes an issue where the collapsed state of diffs in the _Commit Composer_ would get reset when scrolling ([#4898](https://github.com/gitkraken/vscode-gitlens/issues/4898))
-- Fixes an issue where commit messages become invisible during interactive rebase in some themes ([#4886](https://github.com/gitkraken/vscode-gitlens/issues/4886))
-- Fixes issue in the _Commit Graph_ minimap where it only shows a spinner when the repo has no commits ([#4741](https://github.com/gitkraken/vscode-gitlens/issues/4741))
-- Fixes an inline markdown rendering issue in the _Interactive Rebase Editor_ ([#4914](https://github.com/gitkraken/vscode-gitlens/issues/4914))
-- Fixes an issue where opening a deep link to create a PR worktree would incorrectly prompt to add a remote that already exists ([#4926](https://github.com/gitkraken/vscode-gitlens/issues/4926))
-- Fixes an issue where a repository might not be discovered when opening files in parent directories of the repository ([#4932](https://github.com/gitkraken/vscode-gitlens/issues/4932))
-- Fixes an issue where popovers would appear in drag images when dragging commits in the _Interactive Rebase Editor_ ([#4933](https://github.com/gitkraken/vscode-gitlens/issues/4933))
-- Fixes issues with the "Reauthenticate" flow not taking effect ([#4881](https://github.com/gitkraken/vscode-gitlens/issues/4881))
-- Fixes an issue where clicking on the repository filter header in the _Branches_, _Worktrees_, _Tags_, _Remotes_, _Stashes_, and _Contributors_ views would do nothing when only 1 grouped repository exists ([#4947](https://github.com/gitkraken/vscode-gitlens/issues/4947))
-- Fixes issue in webview file trees where same named folders are highlighted when one is selected [#4801](https://github.com/gitkraken/vscode-gitlens/issues/4801)
+- Fixes potential deadlocks during node loading in views (#4928 (https://github.com/gitkraken/vscode-gitlens/issues/4928))
+- Fixes an issue where the GitKraken MCP installation could fail or conflict across remote environments like WSL, SSH, or containers (#4918 (https://github.com/gitkraken/vscode-gitlens/issues/4918))
+- Fixes an issue where diffing untracked files in the _Commit Composer_ could trigger unwanted file system events (#4917 (https://github.com/gitkraken/vscode-gitlens/issues/4917))
+- Fixes an issue where a single-selected commit in the _Commit Composer_ would not get proper highlighting (#4899 (https://github.com/gitkraken/vscode-gitlens/issues/4899))
+- Fixes an issue where the collapsed state of diffs in the _Commit Composer_ would get reset when scrolling (#4898 (https://github.com/gitkraken/vscode-gitlens/issues/4898))
+- Fixes an issue where commit messages become invisible during interactive rebase in some themes (#4886 (https://github.com/gitkraken/vscode-gitlens/issues/4886))
+- Fixes issue in the _Commit Graph_ minimap where it only shows a spinner when the repo has no commits (#4741 (https://github.com/gitkraken/vscode-gitlens/issues/4741))
+- Fixes an inline markdown rendering issue in the _Interactive Rebase Editor_ (#4914 (https://github.com/gitkraken/vscode-gitlens/issues/4914))
+- Fixes an issue where opening a deep link to create a PR worktree would incorrectly prompt to add a remote that already exists (#4926 (https://github.com/gitkraken/vscode-gitlens/issues/4926))
+- Fixes an issue where a repository might not be discovered when opening files in parent directories of the repository (#4932 (https://github.com/gitkraken/vscode-gitlens/issues/4932))
+- Fixes an issue where popovers would appear in drag images when dragging commits in the _Interactive Rebase Editor_ (#4933 (https://github.com/gitkraken/vscode-gitlens/issues/4933))
+- Fixes issues with the "Reauthenticate" flow not taking effect (#4881 (https://github.com/gitkraken/vscode-gitlens/issues/4881))
+- Fixes an issue where clicking on the repository filter header in the _Branches_, _Worktrees_, _Tags_, _Remotes_, _Stashes_, and _Contributors_ views would do nothing when only 1 grouped repository exists (#4947 (https://github.com/gitkraken/vscode-gitlens/issues/4947))
+- Fixes issue in webview file trees where same named folders are highlighted when one is selected #4801 (https://github.com/gitkraken/vscode-gitlens/issues/4801)
- Fixes potential quick pick hung state when cancelling wizards in quick commands
- Fixes an issue where the _Interactive Rebase Editor_ could open in the wrong window for workspace files
- Fixes issues where the GitLens grouped views would not refresh, tree items could not be resolved, or loading state would get stuck when switching views
@@ -2680,23 +2375,23 @@ Additionally, cherry-picking multiple commits now applies them in the correct to
### Added
-- Adds a welcome page webview for first-time installs to highlight Pro benefits for users in IDEs that do not support the standard VS Code walkthrough ([#4769](https://github.com/gitkraken/vscode-gitlens/issues/4769)
+- Adds a welcome page webview for first-time installs to highlight Pro benefits for users in IDEs that do not support the standard VS Code walkthrough (#4769 (https://github.com/gitkraken/vscode-gitlens/issues/4769)
### Changed
-- Improves the _Interactive Rebase Editor_ to fully support `--rebase-merges` on linear history while preventing unsafe reordering when merge commits are present ([#1238](https://github.com/gitkraken/vscode-gitlens/issues/1238))
-- Improves cherry-pick apply order to use topological sort for correct commit sequence ([#4863](https://github.com/gitkraken/vscode-gitlens/issues/4863))
-- Changes AI features to require GitLens Pro instead of GitLens Advanced — all AI features now consistently lead to Pro plan checkout ([#4843](https://github.com/gitkraken/vscode-gitlens/issues/4843))
-- Updates the Welcome walkthrough to streamline onboarding and highlight core GitLens features ([#4842](https://github.com/gitkraken/vscode-gitlens/issues/4842))
+- Improves the _Interactive Rebase Editor_ to fully support `--rebase-merges` on linear history while preventing unsafe reordering when merge commits are present (#1238 (https://github.com/gitkraken/vscode-gitlens/issues/1238))
+- Improves cherry-pick apply order to use topological sort for correct commit sequence (#4863 (https://github.com/gitkraken/vscode-gitlens/issues/4863))
+- Changes AI features to require GitLens Pro instead of GitLens Advanced — all AI features now consistently lead to Pro plan checkout (#4843 (https://github.com/gitkraken/vscode-gitlens/issues/4843))
+- Updates the Welcome walkthrough to streamline onboarding and highlight core GitLens features (#4842 (https://github.com/gitkraken/vscode-gitlens/issues/4842))
### Fixed
-- Fixes issue where the button text on feature gates would blend into the background ([#4833](https://github.com/gitkraken/vscode-gitlens/issues/4833))
-- Fixes issue where codicon would render as text in comparison picker title ([#4866](https://github.com/gitkraken/vscode-gitlens/issues/4866))
-- Fixes issue where Interactive Rebase elements overlap when using keyboard and mouse navigation simultaneously ([#4816](https://github.com/gitkraken/vscode-gitlens/issues/4816))
-- Fixes issue where _Home_ view could crash when state fails to load ([#4766](https://github.com/gitkraken/vscode-gitlens/issues/4766))
-- Fixes [#4776](https://github.com/gitkraken/vscode-gitlens/issues/4776) Azure DevOps Work Item autolinks pointing to wrong project when the Work Item belongs to a different project in the same organization — thanks to [PR #4777](https://github.com/gitkraken/vscode-gitlens/pull/4777) by Daniel Asher ([@danielasher115](https://github.com/danielasher115))
-- Fixes issue where _Load more_ in the _Commits_ view would not correctly load if the last item was a stash ([#4865](https://github.com/gitkraken/vscode-gitlens/issues/4865))
+- Fixes issue where the button text on feature gates would blend into the background (#4833 (https://github.com/gitkraken/vscode-gitlens/issues/4833))
+- Fixes issue where codicon would render as text in comparison picker title (#4866 (https://github.com/gitkraken/vscode-gitlens/issues/4866))
+- Fixes issue where Interactive Rebase elements overlap when using keyboard and mouse navigation simultaneously (#4816 (https://github.com/gitkraken/vscode-gitlens/issues/4816))
+- Fixes issue where _Home_ view could crash when state fails to load (#4766 (https://github.com/gitkraken/vscode-gitlens/issues/4766))
+- Fixes #4776 (https://github.com/gitkraken/vscode-gitlens/issues/4776) Azure DevOps Work Item autolinks pointing to wrong project when the Work Item belongs to a different project in the same organization — thanks to PR #4777 (https://github.com/gitkraken/vscode-gitlens/pull/4777) by Daniel Asher (@danielasher115 (https://github.com/danielasher115))
+- Fixes issue where _Load more_ in the _Commits_ view would not correctly load if the last item was a stash (#4865 (https://github.com/gitkraken/vscode-gitlens/issues/4865))
## Version 17.8
@@ -2755,14 +2450,14 @@ GitLens continues to stay current with AI capabilities, now supporting Claude Op
- Enhances the _Commit Graph_ experience with several new features
- Improves rendering, scrolling, keyboard navigation, and first load performance
- Eliminates flickering of branch metadata (upstream status, PRs, and issues) when the repository changes
-- Adds real-time streaming of search results with pause, resume, and cancel support ([#4782](https://github.com/gitkraken/vscode-gitlens/issues/4782), [#4526](https://github.com/gitkraken/vscode-gitlens/issues/4526), [#3963](https://github.com/gitkraken/vscode-gitlens/issues/3963))
+- Adds real-time streaming of search results with pause, resume, and cancel support (#4782 (https://github.com/gitkraken/vscode-gitlens/issues/4782), #4526 (https://github.com/gitkraken/vscode-gitlens/issues/4526), #3963 (https://github.com/gitkraken/vscode-gitlens/issues/3963))
- Changes the default of the `gitlens.graph.searchItemLimit` setting to `0` (no limit)
-- Adds autocomplete suggestions and interactive filter pickers (for authors, references, and files/folders) to _Commit Graph_ search ([#4780](https://github.com/gitkraken/vscode-gitlens/issues/4780))
+- Adds autocomplete suggestions and interactive filter pickers (for authors, references, and files/folders) to _Commit Graph_ search (#4780 (https://github.com/gitkraken/vscode-gitlens/issues/4780))
- Adds quick pick menus for picking authors, branches or tags, comparison ranges, and files or folders
-- Adds _Compose Commits..._, _Generate Commit Message..._, and _Stash All Changes..._ inline actions to the "work in progress" (WIP) row in the _Commit Graph_ ([#4790](https://github.com/gitkraken/vscode-gitlens/issues/4790))
-- Adds support for recomposing selected commits in graph and composer ([#4600](https://github.com/gitkraken/vscode-gitlens/issues/4600))
-- Adds sticky timeline support to the _Commit Graph_ ([#4781](https://github.com/gitkraken/vscode-gitlens/issues/4781))
-- Adds _Select for Compare_ and _Compare with Selected_ commands to the _Commit Graph_ context menu for commits, stashes, branches, and tags ([#4779](https://github.com/gitkraken/vscode-gitlens/issues/4779))
+- Adds _Compose Commits..._, _Generate Commit Message..._, and _Stash All Changes..._ inline actions to the "work in progress" (WIP) row in the _Commit Graph_ (#4790 (https://github.com/gitkraken/vscode-gitlens/issues/4790))
+- Adds support for recomposing selected commits in graph and composer (#4600 (https://github.com/gitkraken/vscode-gitlens/issues/4600))
+- Adds sticky timeline support to the _Commit Graph_ (#4781 (https://github.com/gitkraken/vscode-gitlens/issues/4781))
+- Adds _Select for Compare_ and _Compare with Selected_ commands to the _Commit Graph_ context menu for commits, stashes, branches, and tags (#4779 (https://github.com/gitkraken/vscode-gitlens/issues/4779))
- Enhances multiselect behavior with improved keyboard and mouse support
- Keyboard navigation
- Arrow[Up|Down] — Moves focus/selection to previous/next row
@@ -2783,9 +2478,9 @@ GitLens continues to stay current with AI capabilities, now supporting Claude Op
- Ctrl+Shift+[Up|Down] (Cmd+Shift+[Up|Down] on macOS) — Topologically extends the selection, and sticks to current branch if possible
- Shift+Home, Shift+End — Extends the selection to first or last commit
- Shift+Page[Up|Down] — Extends the selection by one page
-- Adds an all-new, highly performant, _Interactive Rebase Editor_ with support for `update-ref` other rebase operations ([#4813](https://github.com/gitkraken/vscode-gitlens/issues/4813), [#4405](https://github.com/gitkraken/vscode-gitlens/issues/4405), [#4383](https://github.com/gitkraken/vscode-gitlens/issues/4383), [#4160](https://github.com/gitkraken/vscode-gitlens/issues/4160), [#4148](https://github.com/gitkraken/vscode-gitlens/issues/4148), [#4032](https://github.com/gitkraken/vscode-gitlens/issues/4032), [#3897](https://github.com/gitkraken/vscode-gitlens/issues/3897), [#3866](https://github.com/gitkraken/vscode-gitlens/issues/3866), [#3815](https://github.com/gitkraken/vscode-gitlens/issues/3815), [#3393](https://github.com/gitkraken/vscode-gitlens/issues/3393), [#3337](https://github.com/gitkraken/vscode-gitlens/issues/3337), [#3310](https://github.com/gitkraken/vscode-gitlens/issues/3310))
+- Adds an all-new, highly performant, _Interactive Rebase Editor_ with support for `update-ref` other rebase operations (#4813 (https://github.com/gitkraken/vscode-gitlens/issues/4813), #4405 (https://github.com/gitkraken/vscode-gitlens/issues/4405), #4383 (https://github.com/gitkraken/vscode-gitlens/issues/4383), #4160 (https://github.com/gitkraken/vscode-gitlens/issues/4160), #4148 (https://github.com/gitkraken/vscode-gitlens/issues/4148), #4032 (https://github.com/gitkraken/vscode-gitlens/issues/4032), #3897 (https://github.com/gitkraken/vscode-gitlens/issues/3897), #3866 (https://github.com/gitkraken/vscode-gitlens/issues/3866), #3815 (https://github.com/gitkraken/vscode-gitlens/issues/3815), #3393 (https://github.com/gitkraken/vscode-gitlens/issues/3393), #3337 (https://github.com/gitkraken/vscode-gitlens/issues/3337), #3310 (https://github.com/gitkraken/vscode-gitlens/issues/3310))
- Optimizes performance with virtualization for large rebase operations and lazy-loading of commit metadata
-- Adds ability to recompose commits using AI ([#4796](https://github.com/gitkraken/vscode-gitlens/issues/4796), [#4775](https://github.com/gitkraken/vscode-gitlens/issues/4775))
+- Adds ability to recompose commits using AI (#4796 (https://github.com/gitkraken/vscode-gitlens/issues/4796), #4775 (https://github.com/gitkraken/vscode-gitlens/issues/4775))
- Adds potential conflict detection with visual indicators for commits that will conflict during rebase
- Adds ability to apply bulk actions (pick, squash, fixup, etc.) to multiple selected commits simultaneously
- Improves drag-and-drop experience with multiselect support
@@ -2793,24 +2488,24 @@ GitLens continues to stay current with AI capabilities, now supporting Claude Op
- Mouse: Click to select single, Ctrl+Click (Cmd+Click on macOS) to toggle, Shift+Click for range selection
- Keyboard: Shift+Arrow[Up|Down] for range selection, Ctrl+A (Cmd+A on macOS) to select all entries
- Adds a `gitlens.rebaseEditor.openOnPausedRebase` setting to control whether the _Interactive Rebase Editor_ opens automatically when a rebase is paused
-- Adds a new _Rebase & Update Branches_ and _Interactive Rebase & Update Branches_ confirmation option to the _Git Command Palette_'s _rebase_ command — closes [#4818](https://github.com/gitkraken/vscode-gitlens/issues/4818)
-- Adds Claude Opus 4.5, Gemini 3 Pro, and GPT-5.1 and GPT-5.2 model support for AI features ([#4785](https://github.com/gitkraken/vscode-gitlens/issues/4785))
-- Adds multi-repository support to repository filtering in GitLens views ([#4815](https://github.com/gitkraken/vscode-gitlens/issues/4815))
+- Adds a new _Rebase & Update Branches_ and _Interactive Rebase & Update Branches_ confirmation option to the _Git Command Palette_'s _rebase_ command — closes #4818 (https://github.com/gitkraken/vscode-gitlens/issues/4818)
+- Adds Claude Opus 4.5, Gemini 3 Pro, and GPT-5.1 and GPT-5.2 model support for AI features (#4785 (https://github.com/gitkraken/vscode-gitlens/issues/4785))
+- Adds multi-repository support to repository filtering in GitLens views (#4815 (https://github.com/gitkraken/vscode-gitlens/issues/4815))
- Adds new _Set Upstream..._ and _Change Upstream..._ context menu items to branch status (_Up to date_, _Outgoing_, _Incoming_) in GitLens views
-- Adds new advanced date formatting tokens (`agoAndDate`, `agoAndDateShort`, `agoAndDateBothSources`) and updates default tooltip and status bar formats ([#4783](https://github.com/gitkraken/vscode-gitlens/issues/4783))
-- Adds an experimental `gitlens.advanced.resolveSymlinks` setting to resolve symbolic links when determining file paths for Git operations ([#1328](https://github.com/gitkraken/vscode-gitlens/issues/1328))
-- Adds a `gitlens.advanced.skipOnboarding` setting to prevent onboarding prompts ([#4751](https://github.com/gitkraken/vscode-gitlens/issues/4751))
+- Adds new advanced date formatting tokens (`agoAndDate`, `agoAndDateShort`, `agoAndDateBothSources`) and updates default tooltip and status bar formats (#4783 (https://github.com/gitkraken/vscode-gitlens/issues/4783))
+- Adds an experimental `gitlens.advanced.resolveSymlinks` setting to resolve symbolic links when determining file paths for Git operations (#1328 (https://github.com/gitkraken/vscode-gitlens/issues/1328))
+- Adds a `gitlens.advanced.skipOnboarding` setting to prevent onboarding prompts (#4751 (https://github.com/gitkraken/vscode-gitlens/issues/4751))
- Adds a `gitlens.advanced.git.timeout` setting to configure the Git command timeout
### Changed
-- Improves _Commit Composer_ user experience with maximize command, improved commit message editing, and sticky positioning for commit messages ([#4759](https://github.com/gitkraken/vscode-gitlens/issues/4759))
-- Changes _rebase_, _merge_, _revert_, and _branch delete_ commands to no longer use/open a terminal ([#3527](https://github.com/gitkraken/vscode-gitlens/issues/3527), [#3530](https://github.com/gitkraken/vscode-gitlens/issues/3530), [#3532](https://github.com/gitkraken/vscode-gitlens/issues/3532), [#3534](https://github.com/gitkraken/vscode-gitlens/issues/3534))
-- Improves ignored file checking performance ([#4814](https://github.com/gitkraken/vscode-gitlens/issues/4814))
-- Enhances paused operation status UI with clickable references that jump to commits/branches in the _Commit Graph_ ([#4786](https://github.com/gitkraken/vscode-gitlens/issues/4786))
-- Improves reference selection in views with a unified comparison picker dialog ([#4778](https://github.com/gitkraken/vscode-gitlens/issues/4778))
-- Simplifies remote provider connection flow by directly using the remote name and repository path ([#4411](https://github.com/gitkraken/vscode-gitlens/issues/4411))
-- Improves tracking for hover actions by adding source and detail attributes to events from editor hovers ([#4764](https://github.com/gitkraken/vscode-gitlens/issues/4764))
+- Improves _Commit Composer_ user experience with maximize command, improved commit message editing, and sticky positioning for commit messages (#4759 (https://github.com/gitkraken/vscode-gitlens/issues/4759))
+- Changes _rebase_, _merge_, _revert_, and _branch delete_ commands to no longer use/open a terminal (#3527 (https://github.com/gitkraken/vscode-gitlens/issues/3527), #3530 (https://github.com/gitkraken/vscode-gitlens/issues/3530), #3532 (https://github.com/gitkraken/vscode-gitlens/issues/3532), #3534 (https://github.com/gitkraken/vscode-gitlens/issues/3534))
+- Improves ignored file checking performance (#4814 (https://github.com/gitkraken/vscode-gitlens/issues/4814))
+- Enhances paused operation status UI with clickable references that jump to commits/branches in the _Commit Graph_ (#4786 (https://github.com/gitkraken/vscode-gitlens/issues/4786))
+- Improves reference selection in views with a unified comparison picker dialog (#4778 (https://github.com/gitkraken/vscode-gitlens/issues/4778))
+- Simplifies remote provider connection flow by directly using the remote name and repository path (#4411 (https://github.com/gitkraken/vscode-gitlens/issues/4411))
+- Improves tracking for hover actions by adding source and detail attributes to events from editor hovers (#4764 (https://github.com/gitkraken/vscode-gitlens/issues/4764))
### Removed
@@ -2818,7 +2513,7 @@ GitLens continues to stay current with AI capabilities, now supporting Claude Op
### Fixed
-- Fixes issue where the _Commit Details_ file tree rendering would fail intermittently ([#4784](https://github.com/gitkraken/vscode-gitlens/issues/4784))
+- Fixes issue where the _Commit Details_ file tree rendering would fail intermittently (#4784 (https://github.com/gitkraken/vscode-gitlens/issues/4784))
- Fixes issue where the _Commit Graph_ would load data twice on initial load
- Fixes issue where paused operations would not show on the _Commit Graph_ without working changes
- Fixes issue where onboarding would interrupt error popovers in the _Commit Composer_
@@ -2894,45 +2589,45 @@ Focus on a single branch or tag with the new "Solo" action, which automatically
### Added
- Adds new _Commit Composer_ features and improvements
-- Adds ability to recompose existing branches via the _Recompose Commits (Preview)_ command in the context menu of branches and from the Command Palette ([#4598](https://github.com/gitkraken/vscode-gitlens/issues/4598), [#4599](https://github.com/gitkraken/vscode-gitlens/issues/4599))
-- Adds drag and drop support to reorder auto-composed commits in the commit list ([#4433](https://github.com/gitkraken/vscode-gitlens/issues/4433))
-- Adds support for untracked files ([#4636](https://github.com/gitkraken/vscode-gitlens/issues/4636))
-- Adds support for composing without a base commit ([#4637](https://github.com/gitkraken/vscode-gitlens/issues/4637))
-- Greatly improves performance by virtualizing file diffs ([#4675](https://github.com/gitkraken/vscode-gitlens/issues/4675))
-- Improves some cases where staging or working tree changes are incorrectly detected ([#4667](https://github.com/gitkraken/vscode-gitlens/issues/4667))
+- Adds ability to recompose existing branches via the _Recompose Commits (Preview)_ command in the context menu of branches and from the Command Palette (#4598 (https://github.com/gitkraken/vscode-gitlens/issues/4598), #4599 (https://github.com/gitkraken/vscode-gitlens/issues/4599))
+- Adds drag and drop support to reorder auto-composed commits in the commit list (#4433 (https://github.com/gitkraken/vscode-gitlens/issues/4433))
+- Adds support for untracked files (#4636 (https://github.com/gitkraken/vscode-gitlens/issues/4636))
+- Adds support for composing without a base commit (#4637 (https://github.com/gitkraken/vscode-gitlens/issues/4637))
+- Greatly improves performance by virtualizing file diffs (#4675 (https://github.com/gitkraken/vscode-gitlens/issues/4675))
+- Improves some cases where staging or working tree changes are incorrectly detected (#4667 (https://github.com/gitkraken/vscode-gitlens/issues/4667))
- Adds a link to the custom instructions setting in the _Commit Composer_ view
-- Adds ability to explain unpushed changes via the _Explain Unpushed Changes_ command in the context menu of branches in the _Commit Graph_ and views ([#4443](https://github.com/gitkraken/vscode-gitlens/issues/4443))
+- Adds ability to explain unpushed changes via the _Explain Unpushed Changes_ command in the context menu of branches in the _Commit Graph_ and views (#4443 (https://github.com/gitkraken/vscode-gitlens/issues/4443))
- Adds improved experience to the _Commit Graph_
- Improves rendering, scrolling, and selection performance and stability
- Adds "pill-style" stats to the "Work in Progress" (WIP) row in the _Commit Graph_
- Adds new keyboard navigation support: Home/End to navigate to the first/last row, Page Up/Page Down to navigate by page
-- Adds ability to show file or folder histories on the _Commit Graph_ ([#4725](https://github.com/gitkraken/vscode-gitlens/issues/4725))
+- Adds ability to show file or folder histories on the _Commit Graph_ (#4725 (https://github.com/gitkraken/vscode-gitlens/issues/4725))
- Adds _Open File History in Commit Graph_ command to files in views
- Adds _Open Folder History in Commit Graph_ command to folders in the Explorer view
-- Adds new _Solo Branch_ and _Solo Tag_ commands to quickly filter the _Commit Graph_ view to a specific branch or tag ([#4739](https://github.com/gitkraken/vscode-gitlens/issues/4739))
+- Adds new _Solo Branch_ and _Solo Tag_ commands to quickly filter the _Commit Graph_ view to a specific branch or tag (#4739 (https://github.com/gitkraken/vscode-gitlens/issues/4739))
- Adds _Solo Branch in Commit Graph_ and _Solo Tag in Commit Graph_ commands to the context menu of branches and tags in views
if there are uncommitted changes
-- Changes to select the "Work in progress" (WIP) row in the _Commit Graph_ by default if there are uncommitted changes ([#4716](https://github.com/gitkraken/vscode-gitlens/issues/4716))
+- Changes to select the "Work in progress" (WIP) row in the _Commit Graph_ by default if there are uncommitted changes (#4716 (https://github.com/gitkraken/vscode-gitlens/issues/4716))
- Adds `gitlens.graph.initialRowSelection` setting to specify whether to select the "Work in progress" (WIP) row instead of HEAD
- Adds improved search experience on the _Commit Graph_, _Search & Compare_ view, and in the _Search Commits_ command
-- Adds support for reference or range commit searches ([#4723](https://github.com/gitkraken/vscode-gitlens/issues/4723))
+- Adds support for reference or range commit searches (#4723 (https://github.com/gitkraken/vscode-gitlens/issues/4723))
- Adds `ref:` search operator to filter commits by specific references (branches, tags, SHAs) or commit ranges
- Adds natural language support to allow for more powerful queries
- e.g. "show me all commits on `feature-branch` that aren't on `main`
- e.g. "show me all commits after tag v17.6.0"
-- Adds ability to filter/search to branch & tag tips ([#4726](https://github.com/gitkraken/vscode-gitlens/issues/4726))
+- Adds ability to filter/search to branch & tag tips (#4726 (https://github.com/gitkraken/vscode-gitlens/issues/4726))
- Adds `is:tip` search operator to filter to only commits directly pointed to by a branch or tag
-- Adds a navigable search history to the search box on the _Commit Graph_ ([#4724](https://github.com/gitkraken/vscode-gitlens/issues/4724))
+- Adds a navigable search history to the search box on the _Commit Graph_ (#4724 (https://github.com/gitkraken/vscode-gitlens/issues/4724))
- Allows navigation with arrow keys and deletion of history items
- Adds a _No Results_ message to the _Commit Graph_ when there are no search results
- Adds new experience improvements to the _Commit Details_ and _Graph Details_ views
- Adds "pill-style" file changed stats
- Adds rich context menus to files, similar to the tree views
-- Adds the ability to see which branches and tags contain a specific commit([#4737](https://github.com/gitkraken/vscode-gitlens/issues/4737))
+- Adds the ability to see which branches and tags contain a specific commit(#4737 (https://github.com/gitkraken/vscode-gitlens/issues/4737))
- Adds the ability to see which files are matched by a search on the _Commit Graph_
- Adds a filter toggle button to switch between showing all files, highlighting matched files, and only showing matched files
-- Adds a new _Safe Hard Reset_ (`--keep`) option to Git _reset_ command ([#4720](https://github.com/gitkraken/vscode-gitlens/issues/4720))
-- Adds sort context menu toggles for _Branches_, _Contributors_, _Remotes_, _Repositories_, _Tags_, and _Worktrees_ views ([#4738](https://github.com/gitkraken/vscode-gitlens/issues/4738))
+- Adds a new _Safe Hard Reset_ (`--keep`) option to Git _reset_ command (#4720 (https://github.com/gitkraken/vscode-gitlens/issues/4720))
+- Adds sort context menu toggles for _Branches_, _Contributors_, _Remotes_, _Repositories_, _Tags_, and _Worktrees_ views (#4738 (https://github.com/gitkraken/vscode-gitlens/issues/4738))
- Adds a new `gitlens.sortWorktreesBy` setting to specify the sort order for worktrees
- Adds support for Claude 4.5 Haiku model and hides older Claude models for GitLens' AI features
- Adds "Copy Changes (Patch)" to uncommitted files in the _Worktrees_, _Commit Details_, and _Graph Details_ views
@@ -2948,22 +2643,22 @@ if there are uncommitted changes
- Faster/less intensive conflict file detection
- Greatly improves performance providing the status of worktrees
- Reduces view refresh frequency related to fetch times to avoid extra processing and re-rendering
-- Changes to use the "merge target" when we are creating pull requests ([#4709](https://github.com/gitkraken/vscode-gitlens/issues/4709), [#4734](https://github.com/gitkraken/vscode-gitlens/issues/4734))
-- Changes the minimum VS Code version to 1.95.0 ([#4690](https://github.com/gitkraken/vscode-gitlens/issues/4690), [#4691](https://github.com/gitkraken/vscode-gitlens/issues/4691))
-- Improves MCP checks and adds offline detection ([#4687](https://github.com/gitkraken/vscode-gitlens/issues/4687))
+- Changes to use the "merge target" when we are creating pull requests (#4709 (https://github.com/gitkraken/vscode-gitlens/issues/4709), #4734 (https://github.com/gitkraken/vscode-gitlens/issues/4734))
+- Changes the minimum VS Code version to 1.95.0 (#4690 (https://github.com/gitkraken/vscode-gitlens/issues/4690), #4691 (https://github.com/gitkraken/vscode-gitlens/issues/4691))
+- Improves MCP checks and adds offline detection (#4687 (https://github.com/gitkraken/vscode-gitlens/issues/4687))
- Improves reference/revision range entry in reference pickers
- Consolidates (and fixes missing) progress indicators and spinners on the _Commit Graph_
### Fixed
-- Fixes an issue where the _Home_ view would not update when switching repositories ([#4717](https://github.com/gitkraken/vscode-gitlens/issues/4717))
-- Fixes intermittent stuck loading state on the _Commit Graph_ ([#4669](https://github.com/gitkraken/vscode-gitlens/issues/4669))
-- Fixes underlines showing on home branch actions ([#4703](https://github.com/gitkraken/vscode-gitlens/issues/4703))
-- Fixes _Inspect_ view not showing uncommitted files on the Inspect tab ([#4714](https://github.com/gitkraken/vscode-gitlens/issues/4714))
-- Fixes _Commit Graph_ losing row selection when graph updates ([#4544](https://github.com/gitkraken/vscode-gitlens/issues/4544))
-- Fixes "Element with id already registered" error on comparison w/ multiple repos ([#4521](https://github.com/gitkraken/vscode-gitlens/issues/4521))
-- Fixes _Commit Composer_ diffs misaligned with large editor font sizes ([#4573](https://github.com/gitkraken/vscode-gitlens/issues/4573))
-- Fixes MCP installation flow from proceeding in cases where it shouldn't ([#4672](https://github.com/gitkraken/vscode-gitlens/issues/4672), [#4673](https://github.com/gitkraken/vscode-gitlens/issues/4673), [#4674](https://github.com/gitkraken/vscode-gitlens/issues/4674))
+- Fixes an issue where the _Home_ view would not update when switching repositories (#4717 (https://github.com/gitkraken/vscode-gitlens/issues/4717))
+- Fixes intermittent stuck loading state on the _Commit Graph_ (#4669 (https://github.com/gitkraken/vscode-gitlens/issues/4669))
+- Fixes underlines showing on home branch actions (#4703 (https://github.com/gitkraken/vscode-gitlens/issues/4703))
+- Fixes _Inspect_ view not showing uncommitted files on the Inspect tab (#4714 (https://github.com/gitkraken/vscode-gitlens/issues/4714))
+- Fixes _Commit Graph_ losing row selection when graph updates (#4544 (https://github.com/gitkraken/vscode-gitlens/issues/4544))
+- Fixes "Element with id already registered" error on comparison w/ multiple repos (#4521 (https://github.com/gitkraken/vscode-gitlens/issues/4521))
+- Fixes _Commit Composer_ diffs misaligned with large editor font sizes (#4573 (https://github.com/gitkraken/vscode-gitlens/issues/4573))
+- Fixes MCP installation flow from proceeding in cases where it shouldn't (#4672 (https://github.com/gitkraken/vscode-gitlens/issues/4672), #4673 (https://github.com/gitkraken/vscode-gitlens/issues/4673), #4674 (https://github.com/gitkraken/vscode-gitlens/issues/4674))
- Fixes missing layout commands in view menus
- Fixes stage/unstage failures with large file set by adding batching
- Fixes copying untracked files as a patch
@@ -3024,7 +2719,7 @@ Introduced in GitLens 17.5, Linear issue trackering continues to evolve with aut
Shout-out to our awesome contributors for this release!
-- Noritaka Kobayashi ([@noritaka1166](https://github.com/noritaka1166))
+- Noritaka Kobayashi (@noritaka1166 (https://github.com/noritaka1166))
---
@@ -3034,23 +2729,23 @@ Shout-out to our awesome contributors for this release!
### Changed
-- Greatly improves performance of the _Inspect_ and \_Graph Details views by virtualizing the tree rendering ([#3470](https://github.com/gitkraken/vscode-gitlens/issues/3470))
+- Greatly improves performance of the _Inspect_ and \_Graph Details views by virtualizing the tree rendering (#3470 (https://github.com/gitkraken/vscode-gitlens/issues/3470))
- Improved keyboard navigation support including arrow keys, Home/End, Enter/Space, Tab, and added type-ahead search functionality
-- Improves Linear issue tracker support ([#4605](https://github.com/gitkraken/vscode-gitlens/issues/4605), [#4615](https://github.com/gitkraken/vscode-gitlens/issues/4615), [#4620](https://github.com/gitkraken/vscode-gitlens/issues/4620), [#4621](https://github.com/gitkraken/vscode-gitlens/issues/4621), [#4622](https://github.com/gitkraken/vscode-gitlens/issues/4622))
+- Improves Linear issue tracker support (#4605 (https://github.com/gitkraken/vscode-gitlens/issues/4605), #4615 (https://github.com/gitkraken/vscode-gitlens/issues/4615), #4620 (https://github.com/gitkraken/vscode-gitlens/issues/4620), #4621 (https://github.com/gitkraken/vscode-gitlens/issues/4621), #4622 (https://github.com/gitkraken/vscode-gitlens/issues/4622))
### Fixed
-- Fixes _Commit Composer_ rendering performance when working changes contain large file diffs ([#4661](https://github.com/gitkraken/vscode-gitlens/issues/4661))
-- Fixes AI cancellation cases being treated as errors ([#4609](https://github.com/gitkraken/vscode-gitlens/issues/4609))
-- Fixes MCP banner not being clickable on Commit graph view ([#4630](https://github.com/gitkraken/vscode-gitlens/issues/4630))
-- Fixes Git diff of a renamed file is shown as a new file ([#4246](https://github.com/gitkraken/vscode-gitlens/issues/4246))
-- Fixes typos ([#4345](https://github.com/gitkraken/vscode-gitlens/issues/4345) — thanks to [PR #4346](https://github.com/gitkraken/vscode-gitlens/pull/4346) by Noritaka Kobayashi ([@noritaka1166](https://github.com/noritaka1166)))
+- Fixes _Commit Composer_ rendering performance when working changes contain large file diffs (#4661 (https://github.com/gitkraken/vscode-gitlens/issues/4661))
+- Fixes AI cancellation cases being treated as errors (#4609 (https://github.com/gitkraken/vscode-gitlens/issues/4609))
+- Fixes MCP banner not being clickable on Commit graph view (#4630 (https://github.com/gitkraken/vscode-gitlens/issues/4630))
+- Fixes Git diff of a renamed file is shown as a new file (#4246 (https://github.com/gitkraken/vscode-gitlens/issues/4246))
+- Fixes typos (#4345 (https://github.com/gitkraken/vscode-gitlens/issues/4345) — thanks to PR #4346 (https://github.com/gitkraken/vscode-gitlens/pull/4346) by Noritaka Kobayashi (@noritaka1166 (https://github.com/noritaka1166)))
- Fixes an issue where the _Commit Graph_ hover would not hide when going from the hover to the graph background (not another row)
- Fixes an issue where clicking _Open Changes_ on commit files in the views would error
### Removed
-- Removes " (bundled with GitLens)" text from GK MCP server name ([#4664](https://github.com/gitkraken/vscode-gitlens/issues/4664))
+- Removes " (bundled with GitLens)" text from GK MCP server name (#4664 (https://github.com/gitkraken/vscode-gitlens/issues/4664))
## Version 17.5
@@ -3082,13 +2777,13 @@ The MCP enables powerful use cases through AI chat:
- Get detailed blame info: *"Who last modified the function `calculateTotal` in `utils.js` and why?"*
- GitKraken MCP retrieves precise blame data, including commit details and linked issues & PRs
-See more examples and use cases at [help.gitkraken.com/mcp](https://help.gitkraken.com/mcp/mcp-example-workflows/).
+See more examples and use cases at help.gitkraken.com/mcp (https://help.gitkraken.com/mcp/mcp-example-workflows/).
#### IDE Support and Setup
The MCP works seamlessly in VS Code with built-in configuration, while other IDEs like Cursor, Windsurf, and Trae require manual setup. The MCP leverages GitKraken CLI's unified authentication system, so you authenticate once and gain access to all your connected Git providers (GitHub, GitLab, Azure DevOps, Bitbucket) and issue trackers (Jira, GitHub Issues, Linear).
-Configuration setup and documentation can be found at [help.gitkraken.com/mcp](https://help.gitkraken.com/mcp/mcp-getting-started/).
+Configuration setup and documentation can be found at help.gitkraken.com/mcp (https://help.gitkraken.com/mcp/mcp-getting-started/).
We're just scratching the surface of what's possible with the GitKraken MCP. Future releases will expand capabilities, integrations, and IDE support.
@@ -3109,16 +2804,16 @@ GitKraken now offers a Student Plan for members of the GitHub Student Developer
- **AI token allocation**: Access to powerful AI features including commit composition, branch explanations, PR generation, and changelog creation
- **Includes the entire GitKraken Platform**: Including GitKraken Client, GitKraken CLI, GitKraken.dev and Browser Extension
-Students can learn more and sign up at [gitkraken.com/github-student-developer-pack-bundle](https://www.gitkraken.com/github-student-developer-pack-bundle).
+Students can learn more and sign up at gitkraken.com/github-student-developer-pack-bundle (https://www.gitkraken.com/github-student-developer-pack-bundle).
---
### Added
-- Adds the GitKraken MCP for Git and integration enhanced AI chat workflows — [learn more](https://help.gitkraken.com/mcp/mcp-getting-started/)
+- Adds the GitKraken MCP for Git and integration enhanced AI chat workflows — learn more (https://help.gitkraken.com/mcp/mcp-getting-started/)
- Leverage Git and your integrations (issues, PRs, etc) to provide context and perform actions in AI chat
-- Adds rich Linear integration with autolinks, start work, Launchpad, and more ([#4543](https://github.com/gitkraken/vscode-gitlens/issues/4543), [#4579](https://github.com/gitkraken/vscode-gitlens/issues/4579))
-- Adds support for the [GitKraken Student plan](https://www.gitkraken.com/github-student-developer-pack-bundle)
+- Adds rich Linear integration with autolinks, start work, Launchpad, and more (#4543 (https://github.com/gitkraken/vscode-gitlens/issues/4543), #4579 (https://github.com/gitkraken/vscode-gitlens/issues/4579))
+- Adds support for the GitKraken Student plan (https://www.gitkraken.com/github-student-developer-pack-bundle)
### Changed
@@ -3138,7 +2833,7 @@ GitLens 17.4 transforms the Commit Composer experience with a powerful new compo
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.
-Join the [Commit Composer discussion](https://github.com/gitkraken/vscode-gitlens/discussions/4530) and provide feedback.
+Join the Commit Composer discussion (https://github.com/gitkraken/vscode-gitlens/discussions/4530) and provide feedback.
#### Interactive Draft Commits
@@ -3189,7 +2884,7 @@ You can now easily modify the upstream for local branches in GitLens from places
### Enhanced Worktree Support
-The [17.3.4](https://github.com/gitkraken/vscode-gitlens/releases/tag/v17.3.4) patch release brought significant multi-repo and worktree improvements to VS Code. These enhancements include:
+The 17.3.4 (https://github.com/gitkraken/vscode-gitlens/releases/tag/v17.3.4) patch release brought significant multi-repo and worktree improvements to VS Code. These enhancements include:
- **Repository filtering** - New header controls let you focus on specific repositories or worktrees
- **Visual differentiation** - Improved icons help distinguish between repositories and worktrees
@@ -3202,7 +2897,7 @@ These enhancements work seamlessly with VS Code's native worktree support, provi
### Added
-- Adds new [_Commit Composer_ view experience](https://github.com/gitkraken/vscode-gitlens/discussions/4530 'Learn more') — the next evolution of the [initial Commit Composer preview](https://github.com/gitkraken/vscode-gitlens/discussions/4408)
+- Adds new _Commit Composer_ view experience (https://github.com/gitkraken/vscode-gitlens/discussions/4530 'Learn more') — the next evolution of the initial Commit Composer preview (https://github.com/gitkraken/vscode-gitlens/discussions/4408)
- Transforms the automatic commit process into a comprehensive drafting and review experience
- Adds ability to preview changes before committing and iterate by regenerating individual messages or entire commit compositions
- Adds support for switching between different AI models during composition
@@ -3212,35 +2907,35 @@ These enhancements work seamlessly with VS Code's native worktree support, provi
- Adds _Compose Commits (Preview)_ commands accessible from multiple locations: _Home_ view, _Commit Graph_ WIP row, Inspect/Graph Details views, SCM view, and Command Palette
- Adds updated AI model support for GitLens' AI features
- Adds GPT-5 family (GPT-5, GPT-5 Mini, GPT-5 Nano), and Claude 4.1 Opus models
-- Add Azure DevOps Server integration support ([#4478](https://github.com/gitkraken/vscode-gitlens/issues/4478))
-- Adds expanded and improved branch favoriting ([#4497](https://github.com/gitkraken/vscode-gitlens/issues/4497))
+- Add Azure DevOps Server integration support (#4478 (https://github.com/gitkraken/vscode-gitlens/issues/4478))
+- Adds expanded and improved branch favoriting (#4497 (https://github.com/gitkraken/vscode-gitlens/issues/4497))
- Adds a new "Favorited Branches" option to the branches visibility dropdown on the _Commit Graph_
- Adds _Add to Favorites_ or _Remove from Favorites_ context menu items to branches in the _Commit Graph_
- Adds _Add to Favorites_ or _Remove from Favorites_ context menu items to worktrees in the views
-- Adds 👍 "Helpful" and 👎 "Unhelpful" feedback buttons to AI-generated Changelog ([#4449](https://github.com/gitkraken/vscode-gitlens/issues/4449))
-- Adds ability to set or change the upstream branch for branches in the _Commit Graph_ and other GitLens views ([#4498](https://github.com/gitkraken/vscode-gitlens/issues/4498))
+- Adds 👍 "Helpful" and 👎 "Unhelpful" feedback buttons to AI-generated Changelog (#4449 (https://github.com/gitkraken/vscode-gitlens/issues/4449))
+- Adds ability to set or change the upstream branch for branches in the _Commit Graph_ and other GitLens views (#4498 (https://github.com/gitkraken/vscode-gitlens/issues/4498))
- Adds new _Set Upstream..._ and _Change Upstream..._ context menu items to branches in the _Commit Graph_ and other GitLens views
- Adds a new _upstream_ sub-command to the _branch_ Git Command Palette
- Adds new default topological selection mode to the _Commit Graph_
- Updates `gitlens.graph.multiselect` setting to default to `topological`; set to `true` to allow selecting multiple commits without restriction
- Adds ability to switch between open repositories on the _Visual History_
- Adds _Visualize Repository History_ commands to the SCM menus
-- Adds _Restore Previous Changes_ command to files in the views ([#4542](https://github.com/gitkraken/vscode-gitlens/issues/4542))
+- Adds _Restore Previous Changes_ command to files in the views (#4542 (https://github.com/gitkraken/vscode-gitlens/issues/4542))
### Changed
-- Changes branch favoriting to apply to both local and remote branch pairs ([#4497](https://github.com/gitkraken/vscode-gitlens/issues/4497))
-- Improves experience by opening an explain summary document before summary content is generated ([#4328](https://github.com/gitkraken/vscode-gitlens/issues/4328))
+- Changes branch favoriting to apply to both local and remote branch pairs (#4497 (https://github.com/gitkraken/vscode-gitlens/issues/4497))
+- Improves experience by opening an explain summary document before summary content is generated (#4328 (https://github.com/gitkraken/vscode-gitlens/issues/4328))
- Improves login handling when user copies authentication URL instead of opening it
-- Improves Inspect/Details view button overload ([#4488](https://github.com/gitkraken/vscode-gitlens/issues/4488))
+- Improves Inspect/Details view button overload (#4488 (https://github.com/gitkraken/vscode-gitlens/issues/4488))
### Fixed
- Fixes _Copy Changes (Patch)_ command not working from the _Commit Graph_
-- Fixes issues with handling token limits when using Copilot models ([#4529](https://github.com/gitkraken/vscode-gitlens/issues/4529))
-- Fixes continuous refreshing when gitkraken.dev cannot renew an expired session ([#4324](https://github.com/gitkraken/vscode-gitlens/issues/4324))
-- Fixes some _Commit Graph_ issues because of reference to previous state context ([#4513](https://github.com/gitkraken/vscode-gitlens/issues/4513))
-- Fixes 'generate-rebase' feedback submissions having undefined "type" ([#4502](https://github.com/gitkraken/vscode-gitlens/issues/4502))
+- Fixes issues with handling token limits when using Copilot models (#4529 (https://github.com/gitkraken/vscode-gitlens/issues/4529))
+- Fixes continuous refreshing when gitkraken.dev cannot renew an expired session (#4324 (https://github.com/gitkraken/vscode-gitlens/issues/4324))
+- Fixes some _Commit Graph_ issues because of reference to previous state context (#4513 (https://github.com/gitkraken/vscode-gitlens/issues/4513))
+- Fixes 'generate-rebase' feedback submissions having undefined "type" (#4502 (https://github.com/gitkraken/vscode-gitlens/issues/4502))
## Version 17.3
@@ -3288,19 +2983,19 @@ This feedback helps us understand how well our AI results meet your needs and al
### Added
-- Adds support for using natural language to search for commits on the _Commit Graph_, _Search & Compare_ view, and in the _Search Commits_ command using AI ([#4471](https://github.com/gitkraken/vscode-gitlens/issues/4471))
+- Adds support for using natural language to search for commits on the _Commit Graph_, _Search & Compare_ view, and in the _Search Commits_ command using AI (#4471 (https://github.com/gitkraken/vscode-gitlens/issues/4471))
- Adds support for time-based commit searches on the _Commit Graph_, _Search & Compare_ view, and in the _Search Commits_ command
-- Adds 👍 "Helpful" and 👎 "Unhelpful" feedback buttons to AI-generated markdown previews such as Commit Composer and Explain Changes ([#4449](https://github.com/gitkraken/vscode-gitlens/issues/4449))
+- Adds 👍 "Helpful" and 👎 "Unhelpful" feedback buttons to AI-generated markdown previews such as Commit Composer and Explain Changes (#4449 (https://github.com/gitkraken/vscode-gitlens/issues/4449))
- Adds a _Commit with AI (Preview)_ button to the _Inspect Overview_ tab of the _Commit Graph_ and _Inspect_ views
### Changed
-- Improves experience for invalid AI rebase responses by implementing conversational retry logic that provides specific feedback to the AI about missing, extra, or duplicate hunks and automatically retries up to 3 times ([#4395](https://github.com/gitkraken/vscode-gitlens/issues/4395))
+- Improves experience for invalid AI rebase responses by implementing conversational retry logic that provides specific feedback to the AI about missing, extra, or duplicate hunks and automatically retries up to 3 times (#4395 (https://github.com/gitkraken/vscode-gitlens/issues/4395))
### Fixed
-- Fixes stashes with parent commits older than the oldest stash not being visible on branches ([#4401](https://github.com/gitkraken/vscode-gitlens/issues/4401))
-- Fixes editing search result in Search & Compare view failure ([#4431](https://github.com/gitkraken/vscode-gitlens/issues/4431))
+- Fixes stashes with parent commits older than the oldest stash not being visible on branches (#4401 (https://github.com/gitkraken/vscode-gitlens/issues/4401))
+- Fixes editing search result in Search & Compare view failure (#4431 (https://github.com/gitkraken/vscode-gitlens/issues/4431))
- Fixes search results not paging properly on the _Commit Graph_ when the first page of results is contained within the already loaded commits
## Version 17.2
@@ -3321,7 +3016,7 @@ There are two main operations available in this early preview:
1. **Generate commits from working directory changes**
2. **Generate new commits from existing changes on a branch**
-Read more about how to use these preview features and join the [Commit Composer Discussion](https://github.com/gitkraken/vscode-gitlens/discussions/4408).
+Read more about how to use these preview features and join the Commit Composer Discussion (https://github.com/gitkraken/vscode-gitlens/discussions/4408).
### Work Item UX Improvements in Home View
We're refining the GitLens Home view based on user feedback. In this release, we're focused on improving clarity around the three key components of the current work item: the active branch, the linked issue, and the related pull request.
@@ -3352,15 +3047,15 @@ AI explanations now open in a single rendered markdown file instead of showing b
### Added
-- Adds new AI commands (in preview) which can generate (and rebase) commits from working tree changes or from commits in an existing branch ([#4301](https://github.com/gitkraken/vscode-gitlens/issues/4301)):
+- Adds new AI commands (in preview) which can generate (and rebase) commits from working tree changes or from commits in an existing branch (#4301 (https://github.com/gitkraken/vscode-gitlens/issues/4301)):
- Adds the _Generate Commits with AI (Preview)_ command to the command palette, and to the context menu or working tree changes in views and the _Commit Graph_. This command stashes working tree changes, generates a set of commits from those changes, and commits them to the current branch.
- Adds the _Rebase with AI (Preview)_ command to the command palette and _AI Rebase Current Branch onto Commit (Preview)_ command to the context menu of commits in views and the _Commit Graph_. This command takes the commits on a branch, reorganizes them into a new set of AI-generated commits, creates a branch at the chosen commit and commits them to the new branch
- These commands also generate a document to explain each generated commit and its contents
-- Adds messaging and confirmation on first-time use of the commands to explain how they work ([#4367](https://github.com/gitkraken/vscode-gitlens/issues/4367))
-- Adds an _Undo_ button to the success notification of the commands which attempts to revert the generated commits/branch ([#4366](https://github.com/gitkraken/vscode-gitlens/issues/4366))
-- Adds contributors to _File History_ view ([#4356](https://github.com/gitkraken/vscode-gitlens/issues/4356))
-- Adds support for AI controls from the active organization's security settings on the current account ([#4300](https://github.com/gitkraken/vscode-gitlens/issues/4300))
-- Adds o3 Pro model and latest Gemini 2.5 Pro preview support to GitLens AI features ([#4388](https://github.com/gitkraken/vscode-gitlens/issues/4388))
+- Adds messaging and confirmation on first-time use of the commands to explain how they work (#4367 (https://github.com/gitkraken/vscode-gitlens/issues/4367))
+- Adds an _Undo_ button to the success notification of the commands which attempts to revert the generated commits/branch (#4366 (https://github.com/gitkraken/vscode-gitlens/issues/4366))
+- Adds contributors to _File History_ view (#4356 (https://github.com/gitkraken/vscode-gitlens/issues/4356))
+- Adds support for AI controls from the active organization's security settings on the current account (#4300 (https://github.com/gitkraken/vscode-gitlens/issues/4300))
+- Adds o3 Pro model and latest Gemini 2.5 Pro preview support to GitLens AI features (#4388 (https://github.com/gitkraken/vscode-gitlens/issues/4388))
- Adds Anthropic Claude 4 Opus and Claude 4 Sonnet support to GitLens AI features
- Adds support for Mistral models to GitLens AI features
- Adds a loading message to several GitLens views when the content of the view is still loading
@@ -3369,16 +3064,16 @@ AI explanations now open in a single rendered markdown file instead of showing b
### Changed
-- Automatically stashes (and pops) uncommitted changes on Pull ([#4296](https://github.com/gitkraken/vscode-gitlens/issues/4296))
-- Improves the interaction experience with _Home_ view ([#4302](https://github.com/gitkraken/vscode-gitlens/issues/4302)):
-- Simplifies the "work item" section ([#4332](https://github.com/gitkraken/vscode-gitlens/issues/4332))
-- Removes the option to associate an issue from cards in the "recent" section ([#4333](https://github.com/gitkraken/vscode-gitlens/issues/4333))
-- Combines the "Create Pull Request" and "Create with AI" buttons into a split button ([#4330](https://github.com/gitkraken/vscode-gitlens/issues/4330))
-- On the _Home_ view in the active branch card replaces repository with a breadcrumb that has both the repository and current branch, where the repository is collapsible and is hidden by default ([#4332](https://github.com/gitkraken/vscode-gitlens/issues/4332))
-- Hides Walkthrough links and buttons in _Cursor_ because they are not applicable ([#3837](https://github.com/gitkraken/vscode-gitlens/issues/3837))
-- Changes _Delete Branch_ commands to no longer use/open a terminal ([#3528](https://github.com/gitkraken/vscode-gitlens/issues/3528))
-- Improves the appearance of view headings when collapsed into the grouped view ([#4355](https://github.com/gitkraken/vscode-gitlens/issues/4355))
-- Uses virtual documents instead of untitled documents for summaries generated by GitLens AI commands, and adds a "regenerate" option to most summaries ([#4326](https://github.com/gitkraken/vscode-gitlens/issues/4326))
+- Automatically stashes (and pops) uncommitted changes on Pull (#4296 (https://github.com/gitkraken/vscode-gitlens/issues/4296))
+- Improves the interaction experience with _Home_ view (#4302 (https://github.com/gitkraken/vscode-gitlens/issues/4302)):
+- Simplifies the "work item" section (#4332 (https://github.com/gitkraken/vscode-gitlens/issues/4332))
+- Removes the option to associate an issue from cards in the "recent" section (#4333 (https://github.com/gitkraken/vscode-gitlens/issues/4333))
+- Combines the "Create Pull Request" and "Create with AI" buttons into a split button (#4330 (https://github.com/gitkraken/vscode-gitlens/issues/4330))
+- On the _Home_ view in the active branch card replaces repository with a breadcrumb that has both the repository and current branch, where the repository is collapsible and is hidden by default (#4332 (https://github.com/gitkraken/vscode-gitlens/issues/4332))
+- Hides Walkthrough links and buttons in _Cursor_ because they are not applicable (#3837 (https://github.com/gitkraken/vscode-gitlens/issues/3837))
+- Changes _Delete Branch_ commands to no longer use/open a terminal (#3528 (https://github.com/gitkraken/vscode-gitlens/issues/3528))
+- Improves the appearance of view headings when collapsed into the grouped view (#4355 (https://github.com/gitkraken/vscode-gitlens/issues/4355))
+- Uses virtual documents instead of untitled documents for summaries generated by GitLens AI commands, and adds a "regenerate" option to most summaries (#4326 (https://github.com/gitkraken/vscode-gitlens/issues/4326))
- Updates search results in some views to update dynamically with a count
- Improves the loading performance of the _Worktrees_ view
- Remembers selected nodes in certain views when they lose and regain focus
@@ -3386,13 +3081,13 @@ AI explanations now open in a single rendered markdown file instead of showing b
### Fixed
-- Fixes some cases where "element with id is already registered" errors occur across several GitLens views ([#3341](https://github.com/gitkraken/vscode-gitlens/issues/3341), [#3442](https://github.com/gitkraken/vscode-gitlens/issues/3442), [#3862](https://github.com/gitkraken/vscode-gitlens/issues/3862))
-- Fixes the _Visual File History_ view from refreshing needlessly when the active editor changes between revisions ([#4325](https://github.com/gitkraken/vscode-gitlens/issues/4325))
-- Fixes cancellation of prompts on certain AI commands causing an error notification ([#4354](https://github.com/gitkraken/vscode-gitlens/issues/4354))
-- Fixes files missing in the Repositories view when the "Use compact file layout" option is disabled ([#4307](https://github.com/gitkraken/vscode-gitlens/issues/4307))
-- Fixes "path is already registered" error after git pull ([#922](https://github.com/gitkraken/vscode-gitlens/issues/922))
-- Fixes GitLens file watchers causing high CPU usage in some cases ([#4335](https://github.com/gitkraken/vscode-gitlens/issues/4335))
-- Fixes some cases where stashes and commits incorrectly appear on branches in the _Repositories_ view ([#4353](https://github.com/gitkraken/vscode-gitlens/issues/4353))
+- Fixes some cases where "element with id is already registered" errors occur across several GitLens views (#3341 (https://github.com/gitkraken/vscode-gitlens/issues/3341), #3442 (https://github.com/gitkraken/vscode-gitlens/issues/3442), #3862 (https://github.com/gitkraken/vscode-gitlens/issues/3862))
+- Fixes the _Visual File History_ view from refreshing needlessly when the active editor changes between revisions (#4325 (https://github.com/gitkraken/vscode-gitlens/issues/4325))
+- Fixes cancellation of prompts on certain AI commands causing an error notification (#4354 (https://github.com/gitkraken/vscode-gitlens/issues/4354))
+- Fixes files missing in the Repositories view when the "Use compact file layout" option is disabled (#4307 (https://github.com/gitkraken/vscode-gitlens/issues/4307))
+- Fixes "path is already registered" error after git pull (#922 (https://github.com/gitkraken/vscode-gitlens/issues/922))
+- Fixes GitLens file watchers causing high CPU usage in some cases (#4335 (https://github.com/gitkraken/vscode-gitlens/issues/4335))
+- Fixes some cases where stashes and commits incorrectly appear on branches in the _Repositories_ view (#4353 (https://github.com/gitkraken/vscode-gitlens/issues/4353))
## Version 17.1
@@ -3478,16 +3173,16 @@ These enhancements ensure GitLens continues to scale with your codebase — help
- Adds _Explain Branch Changes (Preview)_ and _Explain Working Changes (Preview)_ (when applicable) actions to the `...` menu on the _Home_ view
- Adds _Explain Branch Changes (Preview)_, _Explain Commit Changes (Preview)_, _Explain Stash Changes (Preview)_, and _Explain Working Changes (Preview)_ actions to the Command Palette
- Adds updated AI provider and model support for GitLens' AI features
-- Adds Ollama and OpenRouter support ([#3311](https://github.com/gitkraken/vscode-gitlens/issues/3311), [#3906](https://github.com/gitkraken/vscode-gitlens/issues/3906))
-- Adds Google Gemini 2.5 Flash (Preview) model, and OpenAI GPT-4.1, GPT-4.1 mini, GPT-4.1 nano, o4 mini, and o3 models ([#4235](https://github.com/gitkraken/vscode-gitlens/issues/4235))
+- Adds Ollama and OpenRouter support (#3311 (https://github.com/gitkraken/vscode-gitlens/issues/3311), #3906 (https://github.com/gitkraken/vscode-gitlens/issues/3906))
+- Adds Google Gemini 2.5 Flash (Preview) model, and OpenAI GPT-4.1, GPT-4.1 mini, GPT-4.1 nano, o4 mini, and o3 models (#4235 (https://github.com/gitkraken/vscode-gitlens/issues/4235))
- Adds support for Azure AI (OpenAI-compatible) models
-- Adds support for custom OpenAI-compatible providers ([#4263](https://github.com/gitkraken/vscode-gitlens/issues/4263))
+- Adds support for custom OpenAI-compatible providers (#4263 (https://github.com/gitkraken/vscode-gitlens/issues/4263))
- Adds `gitlens.ai.enabled` setting to disable all AI-powered features
- Adds a walkthrough for AI features
- Adds an all-new _Visual History_, a powerful evolution of the _Visual File History_, providing a dynamic and insightful visualization of your repository's history, offering flexibility to explore changes across files, folders, branches, and your entire project
- Visualize the history sliced by author (the default) or by branch (when applicable), providing different perspectives on contributions and development lines
- Slicing by author allows you to see the contributions of each author over time
-- Slicing by branch allows you to see unmerged commits on parallel development lines — only available when viewing the history of all branches of a file or folder
+- Slicing by branch allows you to see unmerged commits on parallel development lines — only available when viewing the history of all branches of a file or folder
- Use the zoom/pan functionality to focus on specific timeframes or areas of interest via mouse wheel or zoom buttons
- Adds a breadcrumb navigation bar, with branch switcher and file/folder picker, allowing you to easily navigate the history of files, folders, branches, or the entire repository
- Hold `Alt` or `Shift` when clicking on the breadcrumbs to open the repository or folder in a new tab
@@ -3495,10 +3190,10 @@ These enhancements ensure GitLens continues to scale with your codebase — help
- Adds a scrubber bar to provide an almost time-lapse view for navigating through the changes introduced with each commit in history
- Adds _Visualize Repo History_ and _Visualize Branch History_ actions to the _Home_ view
- Adds _Show Visual History_ command to the Command Palette
-- Adds the ability to change a branch's merge target in Home view. ([#4224](https://github.com/gitkraken/vscode-gitlens/issues/4224))
-- Adds enhanced integration with Azure DevOps, Bitbucket, and Bitbucket Data Center to support associated accounts and pull requests on commits ([#4192](https://github.com/gitkraken/vscode-gitlens/issues/4192))
+- Adds the ability to change a branch's merge target in Home view. (#4224 (https://github.com/gitkraken/vscode-gitlens/issues/4224))
+- Adds enhanced integration with Azure DevOps, Bitbucket, and Bitbucket Data Center to support associated accounts and pull requests on commits (#4192 (https://github.com/gitkraken/vscode-gitlens/issues/4192))
- Adds the ability to search for GitHub Enterprise and GitLab Self-Managed pull requests by URL in Launchpad
-- Adds enhanced and improved accuracy and performance of the revision navigation ([#4200](https://github.com/gitkraken/vscode-gitlens/issues/4200))
+- Adds enhanced and improved accuracy and performance of the revision navigation (#4200 (https://github.com/gitkraken/vscode-gitlens/issues/4200))
- Adds support for navigating line ranges in addition to individual lines
- Adds "changes" statistics for stashes in the _Commit Graph_
- Adds _Open File at Revision from Remote_ command to open the specific file revision from a remote file URL
@@ -3507,7 +3202,7 @@ These enhancements ensure GitLens continues to scale with your codebase — help
### Changed
-- Changes the display of autolinks in the _Inspect_ and _Commit Graph Inspect_ views ([#4286](https://github.com/gitkraken/vscode-gitlens/issues/4286)).
+- Changes the display of autolinks in the _Inspect_ and _Commit Graph Inspect_ views (#4286 (https://github.com/gitkraken/vscode-gitlens/issues/4286)).
- Replaces the autolinks panel with a new compact "footer" bar below the commit message
- Optimizes (rewrote) Git execution and parsing for significantly improved performance, especially with large repositories, and reliability
- Improves contributor fetching performance, especially for large repositories, and adds more advanced data for contributor statistics
@@ -3515,30 +3210,30 @@ These enhancements ensure GitLens continues to scale with your codebase — help
- Improves cancellation support in many Git operations for better responsiveness and system resource usage
- Adds `gitlens.advanced.commits.delayLoadingFileDetails` setting to delay loading full commit file details until required to improve performance even more for large repositories
- Improves _Commit Graph_ rendering performance, re-rendering avoidance, and selection responsiveness
-- Switches the _Commit Graph_ webview to use [Lit](https://lit.dev/) and upgraded to React 19 for the graph component
+- Switches the _Commit Graph_ webview to use Lit (https://lit.dev/) and upgraded to React 19 for the graph component
- Improves commit search performance and reliability, epecially when paging in new results
-- Improves branch name autolink matching logic for better accuracy and fewer false positives ([#3894](https://github.com/gitkraken/vscode-gitlens/issues/3894))
+- Improves branch name autolink matching logic for better accuracy and fewer false positives (#3894 (https://github.com/gitkraken/vscode-gitlens/issues/3894))
- Improves commit search accuracy and performance both in the _Search & Compare_ view and the _Commit Graph_
- Improves commit searches in the _Search & Compare_ view to show only the matching files for file or change-based searches
- Improves commit searches in the _Search & Compare_ view to show matching stashes
- Improves accuracy and performance of the _File History_ and _Line History_ views
- Improves performance of the _Contributors_ view, especially with large repositories
- Adds a configurable `gitlens.views.contributors.maxWait` timeout setting for fetching contributors to avoid potentially long waits
-- Improves GitHub integration authentication check performance, when the authentication extension is disabled or unavailable (Cursor, Windsurf, etc) ([#4065](https://github.com/gitkraken/vscode-gitlens/issues/4065))
-- Improves AI model adherence to provided custom instructions ([#4267](https://github.com/gitkraken/vscode-gitlens/issues/4267))
-- Changes cherry-pick command no longer use/open a terminal ([#3531](https://github.com/gitkraken/vscode-gitlens/issues/3531))
-- Improves date setting descriptions ([#3953](https://github.com/gitkraken/vscode-gitlens/issues/3953))
+- Improves GitHub integration authentication check performance, when the authentication extension is disabled or unavailable (Cursor, Windsurf, etc) (#4065 (https://github.com/gitkraken/vscode-gitlens/issues/4065))
+- Improves AI model adherence to provided custom instructions (#4267 (https://github.com/gitkraken/vscode-gitlens/issues/4267))
+- Changes cherry-pick command no longer use/open a terminal (#3531 (https://github.com/gitkraken/vscode-gitlens/issues/3531))
+- Improves date setting descriptions (#3953 (https://github.com/gitkraken/vscode-gitlens/issues/3953))
### Fixed
- Fixes an error that can occur when retrieving the active repository, such as when the current file is not part of a repository.
-- Fixes cache collision between issues and PRs in autolinks ([#4193](https://github.com/gitkraken/vscode-gitlens/issues/4193))
-- Fixes incorrect PR Link Across Azure DevOps Projects ([#4207](https://github.com/gitkraken/vscode-gitlens/issues/4207))
-- Fixes detail view incorrectly parses GitHub account in commit message ([#3246](https://github.com/gitkraken/vscode-gitlens/issues/3246))
-- Fixes timed out waiting for authentication provider to register in GitLens after update to version 16.3 ([#4065](https://github.com/gitkraken/vscode-gitlens/issues/4065))
-- Fixes cloud integration sessions not refreshing when they expire mid-session ([#4240](https://github.com/gitkraken/vscode-gitlens/issues/4240))
-- Fixes "Delete Worktree" doing nothing when the default worktree is already open in another window ([#4232](https://github.com/gitkraken/vscode-gitlens/issues/4232))
-- Fixes some cases in which Azure DevOps queries fail or return unexpected results ([#4271](https://github.com/gitkraken/vscode-gitlens/issues/4271))
+- Fixes cache collision between issues and PRs in autolinks (#4193 (https://github.com/gitkraken/vscode-gitlens/issues/4193))
+- Fixes incorrect PR Link Across Azure DevOps Projects (#4207 (https://github.com/gitkraken/vscode-gitlens/issues/4207))
+- Fixes detail view incorrectly parses GitHub account in commit message (#3246 (https://github.com/gitkraken/vscode-gitlens/issues/3246))
+- Fixes timed out waiting for authentication provider to register in GitLens after update to version 16.3 (#4065 (https://github.com/gitkraken/vscode-gitlens/issues/4065))
+- Fixes cloud integration sessions not refreshing when they expire mid-session (#4240 (https://github.com/gitkraken/vscode-gitlens/issues/4240))
+- Fixes "Delete Worktree" doing nothing when the default worktree is already open in another window (#4232 (https://github.com/gitkraken/vscode-gitlens/issues/4232))
+- Fixes some cases in which Azure DevOps queries fail or return unexpected results (#4271 (https://github.com/gitkraken/vscode-gitlens/issues/4271))
- Fixes element with id is already registered for commit searches in the _Search & Compare_ view
- Fixes hierarchical compaction in file trees (e.g., a parent folder disappearing if a subfolder with a similar name exists)
- Fixes cherry-pick commit ordering by falling back to author date if committer date matches
@@ -3551,7 +3246,7 @@ These enhancements ensure GitLens continues to scale with your codebase — help
### Engineering
-- Bumps `eslint-plugin-import-x` to v4.10.5 — thanks to [PR #4236](https://github.com/gitkraken/vscode-gitlens/pull/4236) by JounQin ([@JounQin](https://github.com/JounQin))
+- Bumps `eslint-plugin-import-x` to v4.10.5 — thanks to PR #4236 (https://github.com/gitkraken/vscode-gitlens/pull/4236) by JounQin (@JounQin (https://github.com/JounQin))
## Version 17.0
@@ -3561,7 +3256,7 @@ GitLens 17 brings powerful new integrations, enhanced AI capabilities, and workf
### GitKraken AI Preview
-We're excited to introduce [GitKraken AI](https://www.gitkraken.com/solutions/gitkraken-ai?source=gitlens), a preview of our official AI provider for GitLens' AI-powered features. Now users with a paid subscription can leverage powerful AI capabilities without needing to configure external API keys.
+We're excited to introduce GitKraken AI (https://www.gitkraken.com/solutions/gitkraken-ai?source=gitlens), a preview of our official AI provider for GitLens' AI-powered features. Now users with a paid subscription can leverage powerful AI capabilities without needing to configure external API keys.
- Two model options available in this release:
- Google Gemini 2.0 Flash
@@ -3610,30 +3305,30 @@ We've refreshed GitKraken plans to better reflect how devs and teams work:
- A new "Advanced" plan is available with more AI features and controls for small teams of up to 10
- Teams plan is now "Business"
-[Read more](https://www.gitkraken.com/blog/smarter-workflows-built-in-ai-better-developer-experience?source=gitlens) about the new GitKraken plans.
+Read more (https://www.gitkraken.com/blog/smarter-workflows-built-in-ai-better-developer-experience?source=gitlens) about the new GitKraken plans.
### Referral Program
Pro subscribers can now refer colleagues and friends to GitLens through the new referral program and earn $.
-- Access the referral program [here](https://gitkraken.dev/?referral_portal=true&?source=help_center&product=gitlens), or through the account menu in GitLens Home
+- Access the referral program here (https://gitkraken.dev/?referral_portal=true&?source=help_center&product=gitlens), or through the account menu in GitLens Home
### Added
- Adds support for GitKraken AI (Preview), powered by Google Gemini, included with all GitLens Pro subscriptions
- Adds expanded support for GitHub Copilot-provided AI models
- Adds an AI-powered "Create with AI" button to assist with creating pull requests for GitHub and GitLab
-- Adds AI-powered changelog generation between two references ([#4189](https://github.com/gitkraken/vscode-gitlens/issues/4189))
+- Adds AI-powered changelog generation between two references (#4189 (https://github.com/gitkraken/vscode-gitlens/issues/4189))
- Adds a _Generate Changelog (Preview)..._ command to the Command Palette
- Adds a _Generate Changelog (Preview)..._ context menu item to branches and tags in the _Commit Graph_ and in GitLens views
- Adds a _Generate Changelog (Preview)_ context menu item to Behind/Ahead comparison results in Gitlens views
-- Adds AI model status and model switcher to the _Home_ view ([#4064](https://github.com/gitkraken/vscode-gitlens/issues/4064))
-- Adds Anthropic Claude 3.7 Sonnet model for GitLens' AI features ([#4101](https://github.com/gitkraken/vscode-gitlens/issues/4101))
-- Adds Google Gemini 2.5 Pro (Experimental) and Gemini 2.0 Flash-Lite model for GitLens' AI features ([#4104](https://github.com/gitkraken/vscode-gitlens/issues/4104))
-- Adds new Bitbucket Cloud and Data Center integration ([#3916](https://github.com/gitkraken/vscode-gitlens/issues/3916))
-- Adds enriched links to PRs and issues ([#4045](https://github.com/gitkraken/vscode-gitlens/issues/4045))
-- Adds Bitbucket Cloud and Data Center PRs in _Launchpad_ ([#4046](https://github.com/gitkraken/vscode-gitlens/issues/4046))
-- Adds support for Bitbucket issues in _Start Work_ and allows associating issues with branches ([#4047](https://github.com/gitkraken/vscode-gitlens/issues/4047), [#4107](https://github.com/gitkraken/vscode-gitlens/issues/4107))
+- Adds AI model status and model switcher to the _Home_ view (#4064 (https://github.com/gitkraken/vscode-gitlens/issues/4064))
+- Adds Anthropic Claude 3.7 Sonnet model for GitLens' AI features (#4101 (https://github.com/gitkraken/vscode-gitlens/issues/4101))
+- Adds Google Gemini 2.5 Pro (Experimental) and Gemini 2.0 Flash-Lite model for GitLens' AI features (#4104 (https://github.com/gitkraken/vscode-gitlens/issues/4104))
+- Adds new Bitbucket Cloud and Data Center integration (#3916 (https://github.com/gitkraken/vscode-gitlens/issues/3916))
+- Adds enriched links to PRs and issues (#4045 (https://github.com/gitkraken/vscode-gitlens/issues/4045))
+- Adds Bitbucket Cloud and Data Center PRs in _Launchpad_ (#4046 (https://github.com/gitkraken/vscode-gitlens/issues/4046))
+- Adds support for Bitbucket issues in _Start Work_ and allows associating issues with branches (#4047 (https://github.com/gitkraken/vscode-gitlens/issues/4047), #4107 (https://github.com/gitkraken/vscode-gitlens/issues/4107))
- Adds support for multi-select in GitLens views, enabled by default
- Adds _Cherry Pick Commits..._, _Copy Remote Commit URLs_ , and _Open Commits on Remote_ actions to multi-selected commits in the _Commit Graph_ and GitLens views
- Adds _Add as Co-authors_ action to multi-selected contributors in GitLens views
@@ -3644,14 +3339,14 @@ Pro subscribers can now refer colleagues and friends to GitLens through the new
- Adds ability to control how worktrees are displayed in the views
- Adds a `gitlens.views.worktrees.worktrees.viewAs` setting to specify whether to show worktrees by name, path, or relative path
- Adds a `gitlens.views.worktrees.branches.layout` setting to specify whether to show branch worktrees as a list or tree, similar to branches
-- Improves detection in the merge target hover on _Home_ for other cases where a branch was merged and adds other actions for the branch and its merge target ([#4124](https://github.com/gitkraken/vscode-gitlens/issues/4124))
-- Adds expanded support for creating pull requests to all supported providers ([#4142](https://github.com/gitkraken/vscode-gitlens/issues/4142))
+- Improves detection in the merge target hover on _Home_ for other cases where a branch was merged and adds other actions for the branch and its merge target (#4124 (https://github.com/gitkraken/vscode-gitlens/issues/4124))
+- Adds expanded support for creating pull requests to all supported providers (#4142 (https://github.com/gitkraken/vscode-gitlens/issues/4142))
- Adds a _Merge Changes (Manually)..._ action to files in GitLens view to merge changes in those files into the working tree
- Adds an _Open Changes with Common Base_ action to comparison results files
### Changed
-- Improves performance by avoiding eager loading of full commit details for inline blame ([#4115](https://github.com/gitkraken/vscode-gitlens/issues/4115))
+- Improves performance by avoiding eager loading of full commit details for inline blame (#4115 (https://github.com/gitkraken/vscode-gitlens/issues/4115))
- Improves performance by removing `--full-history` flag usage in git commands
- Updates the _Switch AI Model_ command and flow
- Renames the _Switch AI Model_ command to _Switch AI Provider/Model_
@@ -3664,16 +3359,16 @@ Pro subscribers can now refer colleagues and friends to GitLens through the new
### Fixed
-- Fixes Bitbucket Server remote - "scm/" path prefix not removed (regression) ([#3218](https://github.com/gitkraken/vscode-gitlens/issues/3218))
-- Fixes large commit messages work poorly on Commit Graph ([#4100](https://github.com/gitkraken/vscode-gitlens/issues/4100))
-- Fixes _Show \* View_ commands fail intermittently ([#4127](https://github.com/gitkraken/vscode-gitlens/issues/4127))
-- Fixes _Load more_ action not working on incoming changes in Commits/Repositories views ([#4154](https://github.com/gitkraken/vscode-gitlens/issues/4154))
-- Fixes incorrect settings.json entry for Google Gemini 2.0 Flash Thinking causes linter warning ([#4168](https://github.com/gitkraken/vscode-gitlens/issues/4168))
-- Fixes multiple autolinks in commit message are broken when enriched ([#4069](https://github.com/gitkraken/vscode-gitlens/issues/4069))
-- Fixes `gitlens.hovers.autolinks.enhanced` setting is not respected ([#4174](https://github.com/gitkraken/vscode-gitlens/issues/4174))
-- Fixes sign out action on Account popover is actually sign in ([#4182](https://github.com/gitkraken/vscode-gitlens/issues/4182))
-- Fixes Launchpad view causing an "add remote" prompt on load ([#4039](https://github.com/gitkraken/vscode-gitlens/issues/4039))
-- Fixes Launchpad indicator not updating when an item is snoozed ([#4103](https://github.com/gitkraken/vscode-gitlens/issues/4103))
+- Fixes Bitbucket Server remote - "scm/" path prefix not removed (regression) (#3218 (https://github.com/gitkraken/vscode-gitlens/issues/3218))
+- Fixes large commit messages work poorly on Commit Graph (#4100 (https://github.com/gitkraken/vscode-gitlens/issues/4100))
+- Fixes _Show \* View_ commands fail intermittently (#4127 (https://github.com/gitkraken/vscode-gitlens/issues/4127))
+- Fixes _Load more_ action not working on incoming changes in Commits/Repositories views (#4154 (https://github.com/gitkraken/vscode-gitlens/issues/4154))
+- Fixes incorrect settings.json entry for Google Gemini 2.0 Flash Thinking causes linter warning (#4168 (https://github.com/gitkraken/vscode-gitlens/issues/4168))
+- Fixes multiple autolinks in commit message are broken when enriched (#4069 (https://github.com/gitkraken/vscode-gitlens/issues/4069))
+- Fixes `gitlens.hovers.autolinks.enhanced` setting is not respected (#4174 (https://github.com/gitkraken/vscode-gitlens/issues/4174))
+- Fixes sign out action on Account popover is actually sign in (#4182 (https://github.com/gitkraken/vscode-gitlens/issues/4182))
+- Fixes Launchpad view causing an "add remote" prompt on load (#4039 (https://github.com/gitkraken/vscode-gitlens/issues/4039))
+- Fixes Launchpad indicator not updating when an item is snoozed (#4103 (https://github.com/gitkraken/vscode-gitlens/issues/4103))
- Fixes autolinks sometimes not shown in the Inspect view when integrations were disconnected
- Fixes an issue with overlapping popover UI elements
@@ -3701,21 +3396,21 @@ GitLens AI features now include support for the latest AI models from OpenAI, Ge
### Added
-- Adds rich support for Azure DevOps — closes [#3902](https://github.com/gitkraken/vscode-gitlens/issues/3902)
-- Adds integration status and connection flows to the _Home_ view; closes [#3976](https://github.com/gitkraken/vscode-gitlens/issues/3976)
-- Adds autolinks, issues and pull requests in the _Commit Graph_ and _Home_ view; closes [#3977](https://github.com/gitkraken/vscode-gitlens/issues/3977)
-- Adds pull request support in _Launchpad_ — closes [#3978](https://github.com/gitkraken/vscode-gitlens/issues/3978)
-- Adds issue support to _Start Work_; closes [#3979](https://github.com/gitkraken/vscode-gitlens/issues/3979)
+- Adds rich support for Azure DevOps — closes #3902 (https://github.com/gitkraken/vscode-gitlens/issues/3902)
+- Adds integration status and connection flows to the _Home_ view; closes #3976 (https://github.com/gitkraken/vscode-gitlens/issues/3976)
+- Adds autolinks, issues and pull requests in the _Commit Graph_ and _Home_ view; closes #3977 (https://github.com/gitkraken/vscode-gitlens/issues/3977)
+- Adds pull request support in _Launchpad_ — closes #3978 (https://github.com/gitkraken/vscode-gitlens/issues/3978)
+- Adds issue support to _Start Work_; closes #3979 (https://github.com/gitkraken/vscode-gitlens/issues/3979)
- Adds new AI-powered ability to generate a stash message from the changes in the _Stash_ commands
- Adds and expands AI model support for GitLens' AI features
-- Adds DeepSeek V3 and R1 models — closes [#3943](https://github.com/gitkraken/vscode-gitlens/issues/3943)
+- Adds DeepSeek V3 and R1 models — closes #3943 (https://github.com/gitkraken/vscode-gitlens/issues/3943)
- Adds o3-mini and o1 OpenAI models
- Adds Gemini 2.0 Flash, Gemini 2.0 Flash-Lite, Gemini 2.0 Pro, and Gemini 2.0 Flash Thinking models
- Adds dynamic model loading for GitHub Models and HuggingFace models
- Adds a `gitlens.ai.modelOptions.temperature` setting to specify the temperature (randomness) for AI models that support it
- Adds a _Switch Model_ button to the AI confirmation prompts
-- Adds Windsurf support — closes [#3969](https://github.com/gitkraken/vscode-gitlens/issues/3969)
-- Adds "pro" indicators for applicable integrations — closes [#3972](https://github.com/gitkraken/vscode-gitlens/issues/3972)
+- Adds Windsurf support — closes #3969 (https://github.com/gitkraken/vscode-gitlens/issues/3969)
+- Adds "pro" indicators for applicable integrations — closes #3972 (https://github.com/gitkraken/vscode-gitlens/issues/3972)
### Changed
@@ -3723,11 +3418,11 @@ GitLens AI features now include support for the latest AI models from OpenAI, Ge
### Fixed
-- Fixes [#3952](https://github.com/gitkraken/vscode-gitlens/issues/3952) - Interactive rebase doesn't work in GL without VS Code added to path
-- Fixes [#3938](https://github.com/gitkraken/vscode-gitlens/issues/3938) - GitLens automatically initiating an external sign-in after install on vscode.dev
-- Fixes [#3946](https://github.com/gitkraken/vscode-gitlens/issues/3946) - Home View doesn't update repo state changes made when hidden
-- Fixes [#3940](https://github.com/gitkraken/vscode-gitlens/issues/3940) - Commit Details: issue autolinks can disappear after enrichment
-- Fixes [#4035](https://github.com/gitkraken/vscode-gitlens/issues/4035) - Repo is lost when "Generate commit" is requested
+- Fixes #3952 (https://github.com/gitkraken/vscode-gitlens/issues/3952) - Interactive rebase doesn't work in GL without VS Code added to path
+- Fixes #3938 (https://github.com/gitkraken/vscode-gitlens/issues/3938) - GitLens automatically initiating an external sign-in after install on vscode.dev
+- Fixes #3946 (https://github.com/gitkraken/vscode-gitlens/issues/3946) - Home View doesn't update repo state changes made when hidden
+- Fixes #3940 (https://github.com/gitkraken/vscode-gitlens/issues/3940) - Commit Details: issue autolinks can disappear after enrichment
+- Fixes #4035 (https://github.com/gitkraken/vscode-gitlens/issues/4035) - Repo is lost when "Generate commit" is requested
## Version 16.2
@@ -3739,9 +3434,9 @@ GitLens 16.2 brings support for self-hosted GitHub Enterprise and GitLab Self-Ma
GitLens Pro now supports integration with self-hosted GitHub Enterprise and GitLab Self-Managed instances, allowing users to access issue, pull request, and merge request context directly within GitLens.
-- Issues and pull/merge requests from GitHub Enterprise and GitLab Self-Managed will now appear in the GitLens [Home View](https://help.gitkraken.com/gitlens/home-view/) when linked to branches.
-- The [Start Work](https://help.gitkraken.com/gitlens/home-view/#starting-work-on-an-issue) flow now allows users to create branches and worktrees from issues in GitHub Enterprise and GitLab Self-Managed.
-- [Launchpad](https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro) now supports searching for specific pull/merge requests in GitHub Enterprise and GitLab Self-Managed integrations.
+- Issues and pull/merge requests from GitHub Enterprise and GitLab Self-Managed will now appear in the GitLens Home View (https://help.gitkraken.com/gitlens/home-view/) when linked to branches.
+- The Start Work (https://help.gitkraken.com/gitlens/home-view/#starting-work-on-an-issue) flow now allows users to create branches and worktrees from issues in GitHub Enterprise and GitLab Self-Managed.
+- Launchpad (https://help.gitkraken.com/gitlens/gitlens-features/#launchpad-pro) now supports searching for specific pull/merge requests in GitHub Enterprise and GitLab Self-Managed integrations.
### Home View Enhancements
@@ -3765,33 +3460,33 @@ GitLab and GitLab Self-Managed users can now search for specific merge requests
### Improved Visual File History
-The [Visual File History](https://help.gitkraken.com/gitlens/gitlens-features/#visual-file-history-pro) has been completely rebuilt for a better more polished experience, with more consistent bubble sizing and easier to read hovers. We've also added new zoom in and out buttons and mouse wheel support. When you are zoomed in, drag to scrub (scroll) through the history.
+The Visual File History (https://help.gitkraken.com/gitlens/gitlens-features/#visual-file-history-pro) has been completely rebuilt for a better more polished experience, with more consistent bubble sizing and easier to read hovers. We've also added new zoom in and out buttons and mouse wheel support. When you are zoomed in, drag to scrub (scroll) through the history.
### New Visual Folder History
-[Visual File History](https://help.gitkraken.com/gitlens/gitlens-features/#visual-file-history-pro) now supports interactive visualizations of an entire folder's change history, allowing you to track how a group of files has evolved over time. From the visualization, you can identify changes made by specific authors and jump directly to commits to inspect changes in detail. Access the Visual Folder History from the _Folder History_ > _Open Visual Folder History_ on folders in the _Explorer_, _Source Control_, and in GitLens views.
+Visual File History (https://help.gitkraken.com/gitlens/gitlens-features/#visual-file-history-pro) now supports interactive visualizations of an entire folder's change history, allowing you to track how a group of files has evolved over time. From the visualization, you can identify changes made by specific authors and jump directly to commits to inspect changes in detail. Access the Visual Folder History from the _Folder History_ > _Open Visual Folder History_ on folders in the _Explorer_, _Source Control_, and in GitLens views.
### Added
-- Adds richer support for GitHub Enterprise and GitLab Self-Managed — closes [#3901](https://github.com/gitkraken/vscode-gitlens/issues/3901), [#3934](https://github.com/gitkraken/vscode-gitlens/issues/3934)
-- Adds pull request/merge request support in _Launchpad_ — closes [#3923](https://github.com/gitkraken/vscode-gitlens/issues/3923)
+- Adds richer support for GitHub Enterprise and GitLab Self-Managed — closes #3901 (https://github.com/gitkraken/vscode-gitlens/issues/3901), #3934 (https://github.com/gitkraken/vscode-gitlens/issues/3934)
+- Adds pull request/merge request support in _Launchpad_ — closes #3923 (https://github.com/gitkraken/vscode-gitlens/issues/3923)
- Adds issue support to _Start Work_
- Adds integration status and connection flows to the _Home_ view
-- Adds new ability to search for a GitLab merge request in the _Launchpad_ — closes [#3788](https://github.com/gitkraken/vscode-gitlens/issues/3788)
+- Adds new ability to search for a GitLab merge request in the _Launchpad_ — closes #3788 (https://github.com/gitkraken/vscode-gitlens/issues/3788)
- Adds merge target's merged status to the _Home_ view
- GitLens will attempt to determine if the current branch has been merged into its the merge target branch (or the local branch of the merge target)
- Overhauls the _Visual File History_
- Improves commit bubble sizing to better handle outliers
- Improves hover content and interations
-- Adds explicit zoom in/out buttons and changes mouse zoom to use the mouse wheel — when zoomed, drag to scrub through the history
+- Adds explicit zoom in/out buttons and changes mouse zoom to use the mouse wheel — when zoomed, drag to scrub through the history
- Optimizes chart resizing and axis label rendering with author indicators, and re-adds the legend to the view
- Adds a new _Folder History_ > _Open Visual Folder History_ command to folders in the _Explorer_ view, _Source Control_ view, and other GitLens views
-- Adds new ability to see and act upon a "paused" Git operation, e.g. merge, rebase, cherry-pick, revert, across the _Commits_, _Commit Graph_, and _Home_ views — closes [#3913](https://github.com/gitkraken/vscode-gitlens/issues/3913)
+- Adds new ability to see and act upon a "paused" Git operation, e.g. merge, rebase, cherry-pick, revert, across the _Commits_, _Commit Graph_, and _Home_ views — closes #3913 (https://github.com/gitkraken/vscode-gitlens/issues/3913)
- Adds a new banner on the _Commit Graph_ and updates the banner on _Home_ with actions to continue, skip, or abort the operation
- Adds _Continue_, _Skip_, and _Abort_ actions to the _Commits_ view
-- Adds a _GitLens Home_ button to the _Commit Graph_ header to go to the _Home_ view title section — closes [#3873](https://github.com/gitkraken/vscode-gitlens/issues/3873)
-- Adds a new _Hidden Branches / Tags_ dropdown button next to the _Branch Visibility_ dropdown in the _Commit Graph_ toolbar — closes [#3101](https://github.com/gitkraken/vscode-gitlens/issues/3101)
-- Adds a new _Contributors_ section to comparison results in the views — quickly see who contributed changes in the specific range with statistics
+- Adds a _GitLens Home_ button to the _Commit Graph_ header to go to the _Home_ view title section — closes #3873 (https://github.com/gitkraken/vscode-gitlens/issues/3873)
+- Adds a new _Hidden Branches / Tags_ dropdown button next to the _Branch Visibility_ dropdown in the _Commit Graph_ toolbar — closes #3101 (https://github.com/gitkraken/vscode-gitlens/issues/3101)
+- Adds a new _Contributors_ section to comparison results in the views — quickly see who contributed changes in the specific range with statistics
- Adds statistics to contributors in the GitLens views when enabled
- Adds AI model name in commit message generation notifications
@@ -3801,8 +3496,8 @@ The [Visual File History](https://help.gitkraken.com/gitlens/gitlens-features/#v
- Improves branch contributors avatars on the _Home_ view; improved scoring and ordering
- Improves performance of loading/reloading the _Home_ view
- Improves performance of detecting paused Git operations, e.g. merge, rebase, cherry-pick, revert
-- Changes GitLens to be XDG-compatible — closes [#3660](https://github.com/gitkraken/vscode-gitlens/issues/3660)
-- Changes GitLens "reset" command to no longer use/open a terminal — closes [#3533](https://github.com/gitkraken/vscode-gitlens/issues/3533)
+- Changes GitLens to be XDG-compatible — closes #3660 (https://github.com/gitkraken/vscode-gitlens/issues/3660)
+- Changes GitLens "reset" command to no longer use/open a terminal — closes #3533 (https://github.com/gitkraken/vscode-gitlens/issues/3533)
- Changes to format numbers, e.g. counts, with internationalization (i18n) support
- Improves command ordering on branch context menus
- Changes _File History_ context menu to _Folder History_ on folders in the _Explorer_ view
@@ -3811,12 +3506,12 @@ Adds Open [Visual] Folder History to folders in views
### Fixed
-- Fixes [#3915](https://github.com/gitkraken/vscode-gitlens/issues/3915) - Closing a split editor with annotations causes the Clear Annotations button to get stuck
-- Fixes [#3914](https://github.com/gitkraken/vscode-gitlens/issues/3914) - Attempting to clear a file annotation on a split file w/o the annotation no-ops
-- Fixes [#3911](https://github.com/gitkraken/vscode-gitlens/issues/3911) - Avoid Home opening when first-install isn't reliable (e.g. GitPod)
-- Fixes [#3888](https://github.com/gitkraken/vscode-gitlens/issues/3888) - Graph hover should disappear when right-clicking a row
-- Fixes [#3909](https://github.com/gitkraken/vscode-gitlens/issues/3909) - GitLens "Pull with Rebase" is not rebase, but merge
-- Fixes [#3476](https://github.com/gitkraken/vscode-gitlens/issues/3476) - Can't show commit graph in floating window
+- Fixes #3915 (https://github.com/gitkraken/vscode-gitlens/issues/3915) - Closing a split editor with annotations causes the Clear Annotations button to get stuck
+- Fixes #3914 (https://github.com/gitkraken/vscode-gitlens/issues/3914) - Attempting to clear a file annotation on a split file w/o the annotation no-ops
+- Fixes #3911 (https://github.com/gitkraken/vscode-gitlens/issues/3911) - Avoid Home opening when first-install isn't reliable (e.g. GitPod)
+- Fixes #3888 (https://github.com/gitkraken/vscode-gitlens/issues/3888) - Graph hover should disappear when right-clicking a row
+- Fixes #3909 (https://github.com/gitkraken/vscode-gitlens/issues/3909) - GitLens "Pull with Rebase" is not rebase, but merge
+- Fixes #3476 (https://github.com/gitkraken/vscode-gitlens/issues/3476) - Can't show commit graph in floating window
- Fixes an issue with unpin button visibility in the _File History_ view
- Fixes intermittent issue with greater reliability of webview requests
- Fixes an issue with autolink enrichment for issues
@@ -3879,46 +3574,46 @@ GitLens now includes proactive Conflict Detection to help you avoid merge issues
- The "branch owner" is the person who contributed the most changes across the commits between the branch's HEAD and branching point
- Adds contextual tooltips throughout
- Adds pre-emptive conflict detection to _Merge_ and _Rebase_ git commands
-- Adds the ability to show stashes in the _Commits_, _Branches_ and _Worktrees_ views — off by default, can be toggled in the _View Options_ context menu of each view
-- Adds the ability to show remote branches (for the default remote) in the _Branches_ view — off by default, can be toggled in the _View Options_ context menu of each view
-- Adds the ability to associate issues with branches — closes [#3870](https://github.com/gitkraken/vscode-gitlens/issues/3870)
-- Shows issues associated with branches in _Home_ view — closes [#3806](https://github.com/gitkraken/vscode-gitlens/issues/3806)
+- Adds the ability to show stashes in the _Commits_, _Branches_ and _Worktrees_ views — off by default, can be toggled in the _View Options_ context menu of each view
+- Adds the ability to show remote branches (for the default remote) in the _Branches_ view — off by default, can be toggled in the _View Options_ context menu of each view
+- Adds the ability to associate issues with branches — closes #3870 (https://github.com/gitkraken/vscode-gitlens/issues/3870)
+- Shows issues associated with branches in _Home_ view — closes #3806 (https://github.com/gitkraken/vscode-gitlens/issues/3806)
- Shows issues associated with branches in the _Commit Graph_
-- Adds a new command _Associate Issue with Branch..._ command to the command palette and to the context menus of branches in views and the _Commit Graph_ allowing the user to associate an issue with an existing branch — closes [#3884](https://github.com/gitkraken/vscode-gitlens/issues/3884)
+- Adds a new command _Associate Issue with Branch..._ command to the command palette and to the context menus of branches in views and the _Commit Graph_ allowing the user to associate an issue with an existing branch — closes #3884 (https://github.com/gitkraken/vscode-gitlens/issues/3884)
- Associates issues chosen in the _Start Work_ command with branches created for them
-- Adds the ability to get autolinks for branches via the branch name — closes [#3547](https://github.com/gitkraken/vscode-gitlens/issues/3547)
-- Adds GitLab issues to the issues list in the _Start Work_ command when GitLab is connected — closes [#3779](https://github.com/gitkraken/vscode-gitlens/issues/3779)
+- Adds the ability to get autolinks for branches via the branch name — closes #3547 (https://github.com/gitkraken/vscode-gitlens/issues/3547)
+- Adds GitLab issues to the issues list in the _Start Work_ command when GitLab is connected — closes #3779 (https://github.com/gitkraken/vscode-gitlens/issues/3779)
- Adds the latest Gemini models to AI features
- Adds support for deep links to the _Home_ view
-- Adds `gitlens.advanced.caching.gitPath` setting to specify whether to cache the git path — closes [#2877](https://github.com/gitkraken/vscode-gitlens/issues/2877)
+- Adds `gitlens.advanced.caching.gitPath` setting to specify whether to cache the git path — closes #2877 (https://github.com/gitkraken/vscode-gitlens/issues/2877)
### Changed
-- Improves the _Launchpad_ search experience — closes [#3855](https://github.com/gitkraken/vscode-gitlens/issues/3855):
+- Improves the _Launchpad_ search experience — closes #3855 (https://github.com/gitkraken/vscode-gitlens/issues/3855):
- Adds a _Search for Pull Request..._ option that allows the user to search for pull requests outside of the listed ones in _Launchpad_. Currently supports GitHub pull requests, with GitLab soon to be added.
- Pasting a pull request URL which does not match any listed _Launchpad_ issues will automatically trigger a GitHub search for the pull request
- When in provider search mode, adds a _Cancel Searching_ option which will restore the original list of pull requests. Clearing the search input will automatically cancel the search.
-- Improves the _Start Work_ flow and user experience — closes [#3807](https://github.com/gitkraken/vscode-gitlens/issues/3807):
-- Splits the _Start Work_ button into two buttons, a _Start Work on an Issue_ button for creating a branch from an issue, and a button for creating a branch without an associated issue — closes [#3808](https://github.com/gitkraken/vscode-gitlens/issues/3808)
-- Updates the command flow so that an issue is selected first, and the option to create a worktree is presented after creating the branch — closes [#3809](https://github.com/gitkraken/vscode-gitlens/issues/3809)
-- Adds an integration connection button to the title bar — closes [#3832](https://github.com/gitkraken/vscode-gitlens/issues/3832)
-- Adds a quickpick option to connect additional integrations when no issues are found — closes [#3833](https://github.com/gitkraken/vscode-gitlens/issues/3833)
-- Rewords the placeholder text for better clarity when choosing a base for the new branch — closes [#3834](https://github.com/gitkraken/vscode-gitlens/issues/3834)
+- Improves the _Start Work_ flow and user experience — closes #3807 (https://github.com/gitkraken/vscode-gitlens/issues/3807):
+- Splits the _Start Work_ button into two buttons, a _Start Work on an Issue_ button for creating a branch from an issue, and a button for creating a branch without an associated issue — closes #3808 (https://github.com/gitkraken/vscode-gitlens/issues/3808)
+- Updates the command flow so that an issue is selected first, and the option to create a worktree is presented after creating the branch — closes #3809 (https://github.com/gitkraken/vscode-gitlens/issues/3809)
+- Adds an integration connection button to the title bar — closes #3832 (https://github.com/gitkraken/vscode-gitlens/issues/3832)
+- Adds a quickpick option to connect additional integrations when no issues are found — closes #3833 (https://github.com/gitkraken/vscode-gitlens/issues/3833)
+- Rewords the placeholder text for better clarity when choosing a base for the new branch — closes #3834 (https://github.com/gitkraken/vscode-gitlens/issues/3834)
- Adds hover tooltip on issues showing their descriptions
- Improves tooltips on "Open in Remote" icon
- Refines commit/file stats formatting and improves coloring and formatting in tooltips
- Moves the _Commit Graph_ filter commits toggle into the left of the search bar
- Improves the responsiveness of the _Worktrees_ view to changes in relevant state
- Improves the HEAD indicator icon to align more with VS Code
-- Updates prep-release reference — thanks to [PR #3732](https://github.com/gitkraken/vscode-gitlens/pull/3732) by Emmanuel Ferdman ([@emmanuel-ferdman](https://github.com/emmanuel-ferdman))
+- Updates prep-release reference — thanks to PR #3732 (https://github.com/gitkraken/vscode-gitlens/pull/3732) by Emmanuel Ferdman (@emmanuel-ferdman (https://github.com/emmanuel-ferdman))
### Fixed
-- Fixes [#3747](https://github.com/gitkraken/vscode-gitlens/issues/3747) - _Rebase Current Branch onto Branch_ incorrectly shows that the current branch is caught up to the destination
-- Fixes [#3836](https://github.com/gitkraken/vscode-gitlens/issues/3836) - Back button in _Start Work_ goes to the wrong step
-- Fixes [#3791](https://github.com/gitkraken/vscode-gitlens/issues/3791) - Pin/snooze in Launchpad trigger a full refresh and are no longer optimistic
-- Fixes [#3886](https://github.com/gitkraken/vscode-gitlens/issues/3886) - Jira orgs/projects accumulating size in global storage
-- Fixes [#3849](https://github.com/gitkraken/vscode-gitlens/issues/3849) - _Launchpad_ view state does not sync properly when connecting/disconnecting integrations
+- Fixes #3747 (https://github.com/gitkraken/vscode-gitlens/issues/3747) - _Rebase Current Branch onto Branch_ incorrectly shows that the current branch is caught up to the destination
+- Fixes #3836 (https://github.com/gitkraken/vscode-gitlens/issues/3836) - Back button in _Start Work_ goes to the wrong step
+- Fixes #3791 (https://github.com/gitkraken/vscode-gitlens/issues/3791) - Pin/snooze in Launchpad trigger a full refresh and are no longer optimistic
+- Fixes #3886 (https://github.com/gitkraken/vscode-gitlens/issues/3886) - Jira orgs/projects accumulating size in global storage
+- Fixes #3849 (https://github.com/gitkraken/vscode-gitlens/issues/3849) - _Launchpad_ view state does not sync properly when connecting/disconnecting integrations
- Fixes some cases where issues are not properly restricted to open repositories in _Start Work_
- Fixes issue bodies missing on Jira issue items in _Start Work_
- Fixes some Jira issues missing in _Start Work_
@@ -3932,7 +3627,7 @@ GitLens now includes proactive Conflict Detection to help you avoid merge issues
Shout-out to our awesome contributor from a recent patch release!
-- Emmanuel Ferdman ([@emmanuel-ferdman](https://github.com/emmanuel-ferdman))
+- Emmanuel Ferdman (@emmanuel-ferdman (https://github.com/emmanuel-ferdman))
## Version 16.0
@@ -3965,7 +3660,7 @@ Lets you quickly return to previous work by showing recent branches, worktrees,
#### Feedback
-We'll be continuing to refine this view in future releases and welcome your feedback to help shape it. Join in on the [New Home View Discussion](https://github.com/gitkraken/vscode-gitlens/discussions/3721).
+We'll be continuing to refine this view in future releases and welcome your feedback to help shape it. Join in on the New Home View Discussion (https://github.com/gitkraken/vscode-gitlens/discussions/3721).
### Consolidated GitLens Source Control Views
@@ -3991,7 +3686,7 @@ AI features are now in preview! You’ll see improved UX, support for new models
Shout-out to our awesome contributor from a recent patch release!
-- Dawn Hwang ([@hwangh95](https://github.com/hwangh95))
+- Dawn Hwang (@hwangh95 (https://github.com/hwangh95))
### Added
@@ -4010,25 +3705,25 @@ Shout-out to our awesome contributor from a recent patch release!
- Shows pull requests that need your review, are blocked, or are ready to merge
- Start work action to begin a new branch or worktree, or generate one from an existing issue
- Recent section: return to previous work by showing recent branches, worktrees, and PRs with activity for your chosen timeframe
-- Adds _Start Work_ command that opens a quick pick to initiate different flows for starting new work — closes [#3621](https://github.com/gitkraken/vscode-gitlens/issues/3621)
+- Adds _Start Work_ command that opens a quick pick to initiate different flows for starting new work — closes #3621 (https://github.com/gitkraken/vscode-gitlens/issues/3621)
- Start from an issue from GitHub or Jira (other integrations coming soon) and create a branch and/or worktree
-- Adds new ability to search for a GitHub PR in the _Launchpad_ — closes [#3543](https://github.com/gitkraken/vscode-gitlens/issues/3543), [#3684](https://github.com/gitkraken/vscode-gitlens/issues/3684)
-- Adds a new _Filter Commits_ button to the Commit Graph toolbar — closes [#3686](https://github.com/gitkraken/vscode-gitlens/issues/3686)
+- Adds new ability to search for a GitHub PR in the _Launchpad_ — closes #3543 (https://github.com/gitkraken/vscode-gitlens/issues/3543), #3684 (https://github.com/gitkraken/vscode-gitlens/issues/3684)
+- Adds a new _Filter Commits_ button to the Commit Graph toolbar — closes #3686 (https://github.com/gitkraken/vscode-gitlens/issues/3686)
- When toggled while searching the graph, it will be filtered to show only commits matching the search query
- Adds and expands AI support for GitLens' AI features, now out of experimental and in preview
- Refines and improves commit message generation and explaining changes, through better prompting and context
- Adds new model support from GitHub Copilot when installed — no api key needed
- Adds the latest OpenAI and Claude models
- Adds new models from xAI, GitHub Models, and HuggingFace
-- Adds a new _Launchpad_ view, now out of experimental mode — closes [#3615](https://github.com/gitkraken/vscode-gitlens/issues/3615):
+- Adds a new _Launchpad_ view, now out of experimental mode — closes #3615 (https://github.com/gitkraken/vscode-gitlens/issues/3615):
- Remembers the collapsed/expanded state of groups and auto-expands the _Current Branch_ group & item, if applicable
- Reflects changes better, including pinning and snoozing items
- Pinned items should now appear above non-pinned items in their respective groups
-- Adds new all-new onboarding walkthrough — closes [#3656](https://github.com/gitkraken/vscode-gitlens/issues/3656)
-- Adds new deep links to certain GitLens features and views — closes [#3679](https://github.com/gitkraken/vscode-gitlens/issues/3679)
-- Adds support for deep links to the GitLens walkthrough — closes [#3677](https://github.com/gitkraken/vscode-gitlens/issues/3677)
-- Adds support for deep links to _Launchpad_ — closes [#3678](https://github.com/gitkraken/vscode-gitlens/issues/3678)
-- Adds support for deep links to the _Commit Graph_, _Worktrees_, _Inspect_, and _Cloud Patches_ — closes [#3703](https://github.com/gitkraken/vscode-gitlens/issues/3703)
+- Adds new all-new onboarding walkthrough — closes #3656 (https://github.com/gitkraken/vscode-gitlens/issues/3656)
+- Adds new deep links to certain GitLens features and views — closes #3679 (https://github.com/gitkraken/vscode-gitlens/issues/3679)
+- Adds support for deep links to the GitLens walkthrough — closes #3677 (https://github.com/gitkraken/vscode-gitlens/issues/3677)
+- Adds support for deep links to _Launchpad_ — closes #3678 (https://github.com/gitkraken/vscode-gitlens/issues/3678)
+- Adds support for deep links to the _Commit Graph_, _Worktrees_, _Inspect_, and _Cloud Patches_ — closes #3703 (https://github.com/gitkraken/vscode-gitlens/issues/3703)
- Adds _Copy Changes (Patch)_ command to the context menu of branch comparisons and their files in the _Commits_, _Branches_, and _Remotes_ views
- Adds an _Upgrade_ and _Switch to Release Version_ to the expiration notification when using the pre-release of GitLens
@@ -4036,14 +3731,14 @@ Shout-out to our awesome contributor from a recent patch release!
- Changes the, no account, 3-day preview experience of GitLens Pro to be 3 non-consecutive days on the _Commit Graph_
- Changes the GitLens Pro 7-day trial to be 14 days, and 30 days if you invite a teamate
-- Improves _Launchpad_ & the _Launchpad_ view — closes [#3614](https://github.com/gitkraken/vscode-gitlens/issues/3614):
+- Improves _Launchpad_ & the _Launchpad_ view — closes #3614 (https://github.com/gitkraken/vscode-gitlens/issues/3614):
- Adds _Pin_ and _Snooze_ buttons to the header item in the action step
- Draft pull requests for which the current user's review is needed are now also shown in the "Needs Your Review" group, with a draft icon
- Renames _Switch to Branch or Worktree_ option to _Switch to Branch_, since it already includes options to create a worktree in the action flow
-- Improves the open in worktree action flow — closes [#3549](https://github.com/gitkraken/vscode-gitlens/issues/3549):
-- Changes to open a multi-diff editor of the changes when opening a new worktree from a PR to make reviewing easier — [#3701](https://github.com/gitkraken/vscode-gitlens/issues/3701)
+- Improves the open in worktree action flow — closes #3549 (https://github.com/gitkraken/vscode-gitlens/issues/3549):
+- Changes to open a multi-diff editor of the changes when opening a new worktree from a PR to make reviewing easier — #3701 (https://github.com/gitkraken/vscode-gitlens/issues/3701)
- Improves the _Explain_ panel in _Inspect_ and _Graph Details_ with markdown formatting
-- Changes how GitLens handles creating and deleting tags to avoid using the terminal — [#3670](https://github.com/gitkraken/vscode-gitlens/issues/3670)
+- Changes how GitLens handles creating and deleting tags to avoid using the terminal — #3670 (https://github.com/gitkraken/vscode-gitlens/issues/3670)
- Improves quick pick workflows when no repositories are open
- Renames _GK Workspaces_ (GitKraken Workspaces) to _Cloud Workspaces_
- Improves revealing items in the GitLens views
@@ -4051,9 +3746,9 @@ Shout-out to our awesome contributor from a recent patch release!
### Fixed
-- Fixes [#3549](https://github.com/gitkraken/vscode-gitlens/issues/3549) - Webviews can have issues with high contrast themes
-- Fixes [#3734](https://github.com/gitkraken/vscode-gitlens/issues/3734) - Open multi-diff editor when opening a new worktree from a PR
-- Fixes [#3133](https://github.com/gitkraken/vscode-gitlens/issues/3133) - Infinite error loop when pushing stash from GUI
+- Fixes #3549 (https://github.com/gitkraken/vscode-gitlens/issues/3549) - Webviews can have issues with high contrast themes
+- Fixes #3734 (https://github.com/gitkraken/vscode-gitlens/issues/3734) - Open multi-diff editor when opening a new worktree from a PR
+- Fixes #3133 (https://github.com/gitkraken/vscode-gitlens/issues/3133) - Infinite error loop when pushing stash from GUI
- Fixes branch creation and switch quickpicks failing to close when a worktree is created during the flow
- Fixes some cases where Launchpad can fail to detect a connected integration
- Fixed issues with renamed file status on comparisons and pull requests and ensures that renamed files get returned in file status and revision content git operations
@@ -4093,41 +3788,41 @@ GitLens 15.6 improves support for GitLens in the Cursor editor. Cursor users can
Shout-out to our awesome contributors for this release!
-- Jean Pierre ([@jeanp413](https://github.com/jeanp413))
+- Jean Pierre (@jeanp413 (https://github.com/jeanp413))
### Added
-- Adds [Cursor](https://cursor.so) support — closes [#3222](https://github.com/gitkraken/vscode-gitlens/issues/3222)
-- Adds monospace formatting in commit messages — closes [#2350](https://github.com/gitkraken/vscode-gitlens/issues/2350)
-- Adds a new `${authorFirst}` and `${authorLast}` commit formatting tokens that can be used in inline blame, commit hovers, etc — closes [#2980](https://github.com/gitkraken/vscode-gitlens/issues/2980)
-- Adds a new _Create New Branch_ button to the _Commit Graph_ toolbar — closes [#3553](https://github.com/gitkraken/vscode-gitlens/issues/3553)
-- Adds new ability to force push from the _Commit Graph_ toolbar— closes [#3493](https://github.com/gitkraken/vscode-gitlens/issues/3493)
-- Adds a new `gitlens.launchpad.includedOrganizations` setting to specify which organizations to include in _Launchpad_ — closes [#3550](https://github.com/gitkraken/vscode-gitlens/issues/3550)
+- Adds Cursor (https://cursor.so) support — closes #3222 (https://github.com/gitkraken/vscode-gitlens/issues/3222)
+- Adds monospace formatting in commit messages — closes #2350 (https://github.com/gitkraken/vscode-gitlens/issues/2350)
+- Adds a new `${authorFirst}` and `${authorLast}` commit formatting tokens that can be used in inline blame, commit hovers, etc — closes #2980 (https://github.com/gitkraken/vscode-gitlens/issues/2980)
+- Adds a new _Create New Branch_ button to the _Commit Graph_ toolbar — closes #3553 (https://github.com/gitkraken/vscode-gitlens/issues/3553)
+- Adds new ability to force push from the _Commit Graph_ toolbar— closes #3493 (https://github.com/gitkraken/vscode-gitlens/issues/3493)
+- Adds a new `gitlens.launchpad.includedOrganizations` setting to specify which organizations to include in _Launchpad_ — closes #3550 (https://github.com/gitkraken/vscode-gitlens/issues/3550)
- Adds repository owner/name and code suggest to hovers on the experimental Launchpad view
### Changed
-- Integrates the _GitKraken Account_ view into the bottom of the _Home_ view as a collapsible section — closes [#3536](https://github.com/gitkraken/vscode-gitlens/issues/3536)
+- Integrates the _GitKraken Account_ view into the bottom of the _Home_ view as a collapsible section — closes #3536 (https://github.com/gitkraken/vscode-gitlens/issues/3536)
- Changes the new _Commit Graph_ sidebar to be enabled by default; use the `gitlens.graph.sidebar.enabled` settings to disable it
-- Changes how GitLens handles creating and renaming branches to avoid using the terminal — refs [#3528](https://github.com/gitkraken/vscode-gitlens/issues/3528)
+- Changes how GitLens handles creating and renaming branches to avoid using the terminal — refs #3528 (https://github.com/gitkraken/vscode-gitlens/issues/3528)
- Changes patch generation (e.g. cloud patches, code suggest, _Copy as Patch_, _Copy WorkingChanges to Worktree..._, etc) to automatically include untracked files
- Improves _Switch_, _Open in Worktree_, and deeplink and Launchpad workflows
-- Reduces prompts for locating repositories which the user has previously opened — closes [#3555](https://github.com/gitkraken/vscode-gitlens/issues/3555)
-- Improves automatic detection of matching repositories for pull requests — closes [#3627](https://github.com/gitkraken/vscode-gitlens/issues/3627)
+- Reduces prompts for locating repositories which the user has previously opened — closes #3555 (https://github.com/gitkraken/vscode-gitlens/issues/3555)
+- Improves automatic detection of matching repositories for pull requests — closes #3627 (https://github.com/gitkraken/vscode-gitlens/issues/3627)
- Automatically fetches the repository when needed rather than prompting the user
-- Improves the integration connection indicator and connection button on the _Commit Graph_ — closes [#3538](https://github.com/gitkraken/vscode-gitlens/issues/3538)
+- Improves the integration connection indicator and connection button on the _Commit Graph_ — closes #3538 (https://github.com/gitkraken/vscode-gitlens/issues/3538)
### Fixed
-- Fixes [#3548](https://github.com/gitkraken/vscode-gitlens/issues/3548) - Change the current branch icon on the Commit Graph to a worktree icon if its on a worktree
-- Fixes [#3592](https://github.com/gitkraken/vscode-gitlens/issues/3592) - Connecting to an integration via Remotes view (but likely others) doesn't work
-- Fixes [#3571](https://github.com/gitkraken/vscode-gitlens/issues/3571) - Gitlens fails to register buttons on top-right corner — thanks to [PR #3605](https://github.com/gitkraken/vscode-gitlens/pull/3605) by Jean Pierre ([@jeanp413](https://github.com/jeanp413))
-- Fixes [#3617](https://github.com/gitkraken/vscode-gitlens/issues/3617) - Auto-links not working for alphanumberic issue numbers
-- Fixes [#3573](https://github.com/gitkraken/vscode-gitlens/issues/3573) - 'Create Branch in Worktree' option in 'Create Branch' shows a repo picker if you have multiple repos open
-- Fixes [#3612](https://github.com/gitkraken/vscode-gitlens/issues/3612) - Prevents cloud integration sync process from opening gkdev connect page/flow
-- Fixes [#3519](https://github.com/gitkraken/vscode-gitlens/issues/3519) - Add fallback/cutoff to our backend calls similar to how we handle GitHub queries
-- Fixes [#3608](https://github.com/gitkraken/vscode-gitlens/issues/3608) - Integration connection page opening on every launch of VS Code and on profile change
-- Fixes [#3618](https://github.com/gitkraken/vscode-gitlens/issues/3618) -Reauthentication not working for cloud integrations
+- Fixes #3548 (https://github.com/gitkraken/vscode-gitlens/issues/3548) - Change the current branch icon on the Commit Graph to a worktree icon if its on a worktree
+- Fixes #3592 (https://github.com/gitkraken/vscode-gitlens/issues/3592) - Connecting to an integration via Remotes view (but likely others) doesn't work
+- Fixes #3571 (https://github.com/gitkraken/vscode-gitlens/issues/3571) - Gitlens fails to register buttons on top-right corner — thanks to PR #3605 (https://github.com/gitkraken/vscode-gitlens/pull/3605) by Jean Pierre (@jeanp413 (https://github.com/jeanp413))
+- Fixes #3617 (https://github.com/gitkraken/vscode-gitlens/issues/3617) - Auto-links not working for alphanumberic issue numbers
+- Fixes #3573 (https://github.com/gitkraken/vscode-gitlens/issues/3573) - 'Create Branch in Worktree' option in 'Create Branch' shows a repo picker if you have multiple repos open
+- Fixes #3612 (https://github.com/gitkraken/vscode-gitlens/issues/3612) - Prevents cloud integration sync process from opening gkdev connect page/flow
+- Fixes #3519 (https://github.com/gitkraken/vscode-gitlens/issues/3519) - Add fallback/cutoff to our backend calls similar to how we handle GitHub queries
+- Fixes #3608 (https://github.com/gitkraken/vscode-gitlens/issues/3608) - Integration connection page opening on every launch of VS Code and on profile change
+- Fixes #3618 (https://github.com/gitkraken/vscode-gitlens/issues/3618) -Reauthentication not working for cloud integrations
- Fixes an issue where virtual repositories for GitHub PRs from forks wouldn't load properly
- Fixes an issue where deleting a worktree would not always remove the worktree from the view
- Fixes actions not working on Launchpad items with special characters in their branch name
@@ -4136,8 +3831,8 @@ Shout-out to our awesome contributors for this release!
### Engineering
-- Adds end-to-end testing infrastructure using [Playwright](https://playwright.dev)
-- Adds vscode-test to run unit-tests — closes [#3570](https://github.com/gitkraken/vscode-gitlens/issues/3570)
+- Adds end-to-end testing infrastructure using Playwright (https://playwright.dev)
+- Adds vscode-test to run unit-tests — closes #3570 (https://github.com/gitkraken/vscode-gitlens/issues/3570)
## Version 15.5
@@ -4163,7 +3858,7 @@ We've streamlined the Create Worktree command flow, now prompting for a new bran
### Added
-- Adds a `gitlens.views.showCurrentBranchOnTop` setting to specify whether the current branch is shown at the top of the views — closes [#3520](https://github.com/gitkraken/vscode-gitlens/issues/3520)
+- Adds a `gitlens.views.showCurrentBranchOnTop` setting to specify whether the current branch is shown at the top of the views — closes #3520 (https://github.com/gitkraken/vscode-gitlens/issues/3520)
- Adds a sidebar to the _Commit Graph_
- Shows counts of branches, remotes, stashes, tags, and worktrees
- Clicking an item reveals it's corresponding view
@@ -4176,8 +3871,8 @@ We've streamlined the Create Worktree command flow, now prompting for a new bran
### Fixed
-- Fixes [#3514](https://github.com/gitkraken/vscode-gitlens/issues/3514) - Attempting to delete the main worktree's branch causes a invalid prompt to delete the main worktree
-- Fixes [#3518](https://github.com/gitkraken/vscode-gitlens/issues/3518) - Branches in worktrees are no longer collapsed into folder groupings
+- Fixes #3514 (https://github.com/gitkraken/vscode-gitlens/issues/3514) - Attempting to delete the main worktree's branch causes a invalid prompt to delete the main worktree
+- Fixes #3518 (https://github.com/gitkraken/vscode-gitlens/issues/3518) - Branches in worktrees are no longer collapsed into folder groupings
### Removed
@@ -4227,9 +3922,9 @@ On the _Commit Graph_ (and commit search from the _Search & Compare_ view) you c
### Fixed
-- Fixes [#3479](https://github.com/gitkraken/vscode-gitlens/issues/3479) - Tooltip flickering
-- Fixes [#3472](https://github.com/gitkraken/vscode-gitlens/issues/3472) - "Compare working tree with.." often flashes open then closes the menu
-- Fixes [#3448](https://github.com/gitkraken/vscode-gitlens/issues/3448) - "Select for Compare" on a Commit/Stash/etc causes the Search and Compare view to be forcibly shown
+- Fixes #3479 (https://github.com/gitkraken/vscode-gitlens/issues/3479) - Tooltip flickering
+- Fixes #3472 (https://github.com/gitkraken/vscode-gitlens/issues/3472) - "Compare working tree with.." often flashes open then closes the menu
+- Fixes #3448 (https://github.com/gitkraken/vscode-gitlens/issues/3448) - "Select for Compare" on a Commit/Stash/etc causes the Search and Compare view to be forcibly shown
- Fixes the _Git Delete Branch_ command when deleting a branch that is open on a worktree by adding a step to delete the branch's worktree first
- Fixes an issue where pull requests in views could show the wrong comparison with the working tree when using worktrees
- Fixes _Copy Remote Comparison URL_ command to not open the URL, just copy it
@@ -4276,14 +3971,14 @@ Virtual repositories, such as GitHub repositories opened locally with the GitHub
- Adds GitLab (cloud-only for now) support to show and manage merge requests in _Launchpad_
- Adds a new _Connect Additional Integrations_ button to the _Launchpad_ titlebar to allow connecting additional integrations (GitHub and GitLab currently)
- Adds an new experimental _Launchpad_ view to provide a persistent view of the _Launchpad_ in the sidebar
-- To try it out, run the _Show Launchpad View_ command or set the `gitlens.views.launchpad.enabled` setting to `true` — let us know what you think!
+- To try it out, run the _Show Launchpad View_ command or set the `gitlens.views.launchpad.enabled` setting to `true` — let us know what you think!
- While its functionality is currently limited, pull requests can be expanded to show changes, commits, and code suggestions, as well as actions to open changes in the multi-diff editor, open a comparision, and more
- Adds new features and improvements to the _Commit Graph_
- Branch visibility options, formerly in the _Graph Filtering_ dropdown, are now moved to the new _Branches Visibility_ dropdown in the _Commit Graph_ header bar
-- Adds a new _Smart Branches_ visibility option to shows only relevant branches — the current branch, its upstream, and its base or target branch, to help you better focus
-- Improves interactions with hovers on rows — they should do a better job of staying out of your way
+- Adds a new _Smart Branches_ visibility option to shows only relevant branches — the current branch, its upstream, and its base or target branch, to help you better focus
+- Improves interactions with hovers on rows — they should do a better job of staying out of your way
- Adds pull request information to branches with missing upstreams
-- Adds support for GitHub and GitLab cloud integrations — automatically synced with your GitKraken account
+- Adds support for GitHub and GitLab cloud integrations — automatically synced with your GitKraken account
- Adds an improved, streamlined experience for connecting cloud integrations to GitLens
- Manage your connected integration via the the _Manage Integrations_ command or the _Integrations_ button on the _GitKraken Account_ view
- Adds comparison support to virtual (GitHub) repositories
@@ -4301,10 +3996,10 @@ Virtual repositories, such as GitHub repositories opened locally with the GitHub
### Fixed
-- Fixes [#3445](https://github.com/gitkraken/vscode-gitlens/issues/3445) - Cannot merge branch into detached HEAD
-- Fixes [#3443](https://github.com/gitkraken/vscode-gitlens/issues/3443) - Don't show gitlens context menu items in Copilot Chat codeblock editors
-- Fixes [#3457](https://github.com/gitkraken/vscode-gitlens/issues/3457) - Enriched autolink duplication in graph hover (and possibly other places)
-- Fixes [#3473](https://github.com/gitkraken/vscode-gitlens/issues/3473) - Plus features can't be restored after they are hidden
+- Fixes #3445 (https://github.com/gitkraken/vscode-gitlens/issues/3445) - Cannot merge branch into detached HEAD
+- Fixes #3443 (https://github.com/gitkraken/vscode-gitlens/issues/3443) - Don't show gitlens context menu items in Copilot Chat codeblock editors
+- Fixes #3457 (https://github.com/gitkraken/vscode-gitlens/issues/3457) - Enriched autolink duplication in graph hover (and possibly other places)
+- Fixes #3473 (https://github.com/gitkraken/vscode-gitlens/issues/3473) - Plus features can't be restored after they are hidden
- Fixes column resizing being stuck when the mouse leaves the _Commit Graph_
- Fixes issues with incorrect commit count when using the merge and rebase commands
- Fixes issues where a merge or rebase operation says there or no changes when there are changes
@@ -4364,9 +4059,9 @@ GitLens now supports Anthropic's latest Claude 3.5 Sonnet model for our experime
### Fixed
-- Fixes [#3344](https://github.com/gitkraken/vscode-gitlens/issues/3344) - Make changing the AI key easier
-- Fixes [#3377](https://github.com/gitkraken/vscode-gitlens/issues/3377) - Cannot read properties of undefined (reading 'start')
-- Fixes [#3377](https://github.com/gitkraken/vscode-gitlens/issues/3378) - Deleting a worktree (without force) with working changes causes double prompts
+- Fixes #3344 (https://github.com/gitkraken/vscode-gitlens/issues/3344) - Make changing the AI key easier
+- Fixes #3377 (https://github.com/gitkraken/vscode-gitlens/issues/3377) - Cannot read properties of undefined (reading 'start')
+- Fixes #3377 (https://github.com/gitkraken/vscode-gitlens/issues/3378) - Deleting a worktree (without force) with working changes causes double prompts
- Fixes fixes issue with Jira integration not refreshing
- Fixes the _Learn More_ link not working in the account verification dialog
- Upgrading to Pro and account management now no longer require the user to log in again in their respective pages on _gitkraken.dev_
@@ -4390,13 +4085,13 @@ To simplify the overall configuration of AI models, we have unified all settings
We've made several improvements to the Launchpad to provide a more intuitive and user-friendly experience. The collapsed state of Launchpad groups is now saved between uses, ensuring a consistent view across sessions. The Draft and Pinned categories in the Launchpad always sort their items by date, making it easier to find recent entries. The Launchpad status bar indicator now provides clear indications when there is an error loading data, keeping you informed of any issues. Additionally, we've improved loading performance and are continuing to look for ways to improve that in the future.
-To leave us feedback such as what do you think, is this useful, what does it have that you like, what is it missing, etc. reach out to us on the GitLens [GitHub Discussion board](https://github.com/gitkraken/vscode-gitlens/discussions/3286). We really want to hear your feedback!
+To leave us feedback such as what do you think, is this useful, what does it have that you like, what is it missing, etc. reach out to us on the GitLens GitHub Discussion board (https://github.com/gitkraken/vscode-gitlens/discussions/3286). We really want to hear your feedback!
### Thank you to our contributors
Shout-out to our awesome contributors for this release!
-- bm-w ([@bm-w](https://github.com/bm-w))
+- bm-w (@bm-w (https://github.com/bm-w))
### Added
@@ -4417,8 +4112,8 @@ Shout-out to our awesome contributors for this release!
### Fixed
-- Fixes [#3295](https://github.com/gitkraken/vscode-gitlens/issues/3295) - Incorrect pluralization in Authors lens — thanks to [PR #3296](https://github.com/gitkraken/vscode-gitlens/pull/3296) by bm-w ([@bm-w](https://github.com/bm-w))
-- Fixes [#3277](https://github.com/gitkraken/vscode-gitlens/issues/3277) - Unable to pull branch when the local branch whose name differs from its tracking branch
+- Fixes #3295 (https://github.com/gitkraken/vscode-gitlens/issues/3295) - Incorrect pluralization in Authors lens — thanks to PR #3296 (https://github.com/gitkraken/vscode-gitlens/pull/3296) by bm-w (@bm-w (https://github.com/bm-w))
+- Fixes #3277 (https://github.com/gitkraken/vscode-gitlens/issues/3277) - Unable to pull branch when the local branch whose name differs from its tracking branch
## Version 15.0
@@ -4442,7 +4137,7 @@ Code Suggest is a new cloud feature that frees your code reviews from the unnece
You can create a Code Suggestion from the _Inspect: Overview_ tab when on a PR's branch. You can also start Code Suggestions on a pull request directly from the Launchpad. Simply choose which file changes to include, add a title and optional description, and you're ready to go.
-Upon creation of a Code Suggestion, a comment will appear on the pull request. Code Suggestions can be viewed and applied directly from [gitkraken.dev](https://gitkraken.dev?source=help_center&product=gitlens), or opened in GitKraken Desktop or GitLens.
+Upon creation of a Code Suggestion, a comment will appear on the pull request. Code Suggestions can be viewed and applied directly from gitkraken.dev (https://gitkraken.dev?source=help_center&product=gitlens), or opened in GitKraken Desktop or GitLens.
You can see a PR's Code Suggestions from anywhere we currently display PR information in our views, including Commits, Branches, Remotes, and the new Pull Request view. From there you can view the changes, apply them, accept or reject the code suggestion, or copy a link to share with team members.
@@ -4462,11 +4157,11 @@ We've also expanded our OpenAI and Anthropic model support to include the latest
Shout-out to our awesome contributors for this release!
-- may ([@m4rch3n1ng](https://github.com/m4rch3n1ng))
+- may (@m4rch3n1ng (https://github.com/m4rch3n1ng))
### Added
-- Adds [Launchpad](https://gitkraken.com/solutions/launchpad?utm_source=gitlens-extension&utm_medium=in-app-links) `preview`, a new Pro feature bringing your GitHub pull requests into a unified, categorized list to keep you focused and your team unblocked
+- Adds Launchpad (https://gitkraken.com/solutions/launchpad?utm_source=gitlens-extension&utm_medium=in-app-links) `preview`, a new Pro feature bringing your GitHub pull requests into a unified, categorized list to keep you focused and your team unblocked
- Open using the new _GitLens: Open Launchpad_ command
- Categorizes pull requests by status
- _Current Branch_: Pull requests associated with your current branch
@@ -4505,10 +4200,10 @@ Shout-out to our awesome contributors for this release!
- `gitlens.launchpad.indicator.polling.enabled`: Specifies whether to regularly check for changes to pull requests
- `gitlens.launchpad.indicator.polling.interval`: Specifies the interval in minutes to check for changes to pull requests
- Adds new features that make code reviews easier
-- Adds [Code Suggest](https://gitkraken.com/solutions/code-suggest?utm_source=gitlens-extension&utm_medium=in-app-links) `preview`, a cloud feature, that frees your code reviews from unnecessary restrictions
+- Adds Code Suggest (https://gitkraken.com/solutions/code-suggest?utm_source=gitlens-extension&utm_medium=in-app-links) `preview`, a cloud feature, that frees your code reviews from unnecessary restrictions
- Create a Code Suggestion from the _Inspect: Overview_ tab when on a PR's branch
- Upon creation of a Code Suggestion, a comment will appear on the pull request
-- Code Suggestions can be viewed and apply directly from [gitkraken.dev](https://gitkraken.dev?source=help_center&product=gitlens), or open in GitKraken Desktop or GitLens.
+- Code Suggestions can be viewed and apply directly from gitkraken.dev (https://gitkraken.dev?source=help_center&product=gitlens), or open in GitKraken Desktop or GitLens.
- See a PR's Code Suggestions from anywhere we currently display PR information in our views (Commits, Branches, Remotes)
- You can additionally start Code Suggestions from the Launchpad
- Adds a _Pull Request_ view to view PR commits and review file changes
@@ -4542,13 +4237,13 @@ Shout-out to our awesome contributors for this release!
### Fixed
-- Fixes [#3221](https://github.com/gitkraken/vscode-gitlens/issues/3221) - Cannot use word "detached" in branch names
-- Fixes [#3197](https://github.com/gitkraken/vscode-gitlens/issues/3197) - Only emojify standalone emojis — thanks to [PR #3208](https://github.com/gitkraken/vscode-gitlens/pull/3208) by may ([@m4rch3n1ng](https://github.com/m4rch3n1ng))
-- Fixes [#3180](https://github.com/gitkraken/vscode-gitlens/issues/3180) - Focus View feedback button is not working
-- Fixes [#3179](https://github.com/gitkraken/vscode-gitlens/issues/3179) - The checkmarks in cherry pick are not displayed
-- Fixes [#3249](https://github.com/gitkraken/vscode-gitlens/issues/3249) - Error "Cannot read properties of null (reading 'map')
-- Fixes [#3198](https://github.com/gitkraken/vscode-gitlens/issues/3198) - Repository location in cloud workspace doesn't work when the repo descriptor does not contain a url
-- Fixes [#3143](https://github.com/gitkraken/vscode-gitlens/issues/3143) - File Annotation icon isn't themed according to the icons...
+- Fixes #3221 (https://github.com/gitkraken/vscode-gitlens/issues/3221) - Cannot use word "detached" in branch names
+- Fixes #3197 (https://github.com/gitkraken/vscode-gitlens/issues/3197) - Only emojify standalone emojis — thanks to PR #3208 (https://github.com/gitkraken/vscode-gitlens/pull/3208) by may (@m4rch3n1ng (https://github.com/m4rch3n1ng))
+- Fixes #3180 (https://github.com/gitkraken/vscode-gitlens/issues/3180) - Focus View feedback button is not working
+- Fixes #3179 (https://github.com/gitkraken/vscode-gitlens/issues/3179) - The checkmarks in cherry pick are not displayed
+- Fixes #3249 (https://github.com/gitkraken/vscode-gitlens/issues/3249) - Error "Cannot read properties of null (reading 'map')
+- Fixes #3198 (https://github.com/gitkraken/vscode-gitlens/issues/3198) - Repository location in cloud workspace doesn't work when the repo descriptor does not contain a url
+- Fixes #3143 (https://github.com/gitkraken/vscode-gitlens/issues/3143) - File Annotation icon isn't themed according to the icons...
## Version 14.9
@@ -4575,17 +4270,17 @@ We've added support for Anthropic's Claude 3 Opus & Sonnet models for GitLens' e
### Changed
-- Re-adds _Add to Workspace_ option when creating a worktree — closes [#3160](https://github.com/gitkraken/vscode-gitlens/issues/3160)
-- Changes _Commit Graph_ date style to default to the default date style — refs [#3153](https://github.com/gitkraken/vscode-gitlens/issues/3153)
+- Re-adds _Add to Workspace_ option when creating a worktree — closes #3160 (https://github.com/gitkraken/vscode-gitlens/issues/3160)
+- Changes _Commit Graph_ date style to default to the default date style — refs #3153 (https://github.com/gitkraken/vscode-gitlens/issues/3153)
- Renames the _Compare Ancestry with Working Tree_ command on branches to _Compare Common Base with Working Tree_ for better clarity
- Improves _File Blame_ annotations performance and layout accuracy with certain character sets
- Improves string formatting performance
### Fixed
-- Fixes [#3146](https://github.com/gitkraken/vscode-gitlens/issues/3146) - Search & Compare fails to remember items after restart
-- Fixes [#3152](https://github.com/gitkraken/vscode-gitlens/issues/3152) - Fixes double encoding of redirect URLs during account sign-in which affects certain environments
-- Fixes [#3153](https://github.com/gitkraken/vscode-gitlens/issues/3153) - `gitlens.defaultDateStyle` not working in Commit Details view
+- Fixes #3146 (https://github.com/gitkraken/vscode-gitlens/issues/3146) - Search & Compare fails to remember items after restart
+- Fixes #3152 (https://github.com/gitkraken/vscode-gitlens/issues/3152) - Fixes double encoding of redirect URLs during account sign-in which affects certain environments
+- Fixes #3153 (https://github.com/gitkraken/vscode-gitlens/issues/3153) - `gitlens.defaultDateStyle` not working in Commit Details view
- Fixes the _Open Pull Request Changes_ & _Compare Pull Request_ commands to scope the changes only to the pull request
- Fixes broken _Compare Common Base with Working Tree_ (previously _Compare Ancestry with Working Tree_)
- Fixes issue when switching to a worktree via branch switch when there are multiple repos in the workspace
@@ -4606,19 +4301,19 @@ VS Code's new multi-diff editor is out of experimental, so we've enabled it in o
### Cloud Patch Enterprise Storage ☁️
-For Enterprise customers, there is now the option to host Cloud Patches on your own dedicated storage for maximum security. Your organization's admin can configure the self-managed storage at [Security](https://gitkraken.dev/settings/security?source=help_center&product=gitlens). When creating a Cloud Patch, GitLens will confirm they are being stored on your secure organization storage.
+For Enterprise customers, there is now the option to host Cloud Patches on your own dedicated storage for maximum security. Your organization's admin can configure the self-managed storage at Security (https://gitkraken.dev/settings/security?source=help_center&product=gitlens). When creating a Cloud Patch, GitLens will confirm they are being stored on your secure organization storage.
### Thank you to our contributors
Shout-out to our awesome contributors for this release!
-- yutotnh ([@yutotnh](https://github.com/yutotnh))
+- yutotnh (@yutotnh (https://github.com/yutotnh))
### Added
- Adds support for Cloud Patches hosted on your own dedicated storage for the highest level of security (requires an Enterprise plan)
- Improves worktree usage, discoverability, and accessibility
-- Simplifies the create worktree and open worktree flows — reduces number of steps and options presented
+- Simplifies the create worktree and open worktree flows — reduces number of steps and options presented
- Adds _Create Branch in New Worktree_ confirmation option when creating branches, e.g. via the _GitLens: Git Create Branch..._ command
- Adds _Create Worktree for Branch_, _Create Worktree for Local Branch_, and _Create Worktree for New Local Branch_ confirmation options when switching branches, e.g. via the _GitLens: Git Switch to..._ command
- Adds a _Copy Working Changes to Worktree..._ command to the _Commit Graph_ and command palette to copy the current working changes to an existing worktree
@@ -4641,12 +4336,12 @@ Shout-out to our awesome contributors for this release!
- Adds an _Open All Changes_ inline button to branch status (upstream) and branch status files in GitLens views
- Adds an _Open Changes_ submenu to branch status (upstream) and branch status files in GitLens views
- Adds ability to preserve inline and file annotations while editing, previously experimental and now enabled by default
-- Renames the `gitlens.experimental.allowAnnotationsWhenDirty` setting to `gitlens.fileAnnotations.preserveWhileEditing`, which is enabled by default, to specify whether file annotations will be preserved while editing — closes [#1988](https://github.com/gitkraken/vscode-gitlens/issues/1988), [#3016](https://github.com/gitkraken/vscode-gitlens/issues/3016)
+- Renames the `gitlens.experimental.allowAnnotationsWhenDirty` setting to `gitlens.fileAnnotations.preserveWhileEditing`, which is enabled by default, to specify whether file annotations will be preserved while editing — closes #1988 (https://github.com/gitkraken/vscode-gitlens/issues/1988), #3016 (https://github.com/gitkraken/vscode-gitlens/issues/3016)
- Use the existing `gitlens.advanced.blame.delayAfterEdit` setting to control how long to wait (defaults to 5s) before the annotation will update while the file is still dirty, which only applies if the file is under the `gitlens.advanced.sizeThresholdAfterEdit` setting threshold (defaults to 5000 lines)
- Adds an _Open File Annotation Settings_ command to the _File Annotations_ submenu in the editor toolbar to open the GitLens Settings editor to the file annotations sections
-- Adds `gitlens.blame.fontFamily`, `gitlens.blame.fontSize`, `gitlens.blame.fontWeight` settings to specify the font (family, size, and weight respectively) of the _File Blame_ annotations — closes [#3134](https://github.com/gitkraken/vscode-gitlens/issues/3134)
+- Adds `gitlens.blame.fontFamily`, `gitlens.blame.fontSize`, `gitlens.blame.fontWeight` settings to specify the font (family, size, and weight respectively) of the _File Blame_ annotations — closes #3134 (https://github.com/gitkraken/vscode-gitlens/issues/3134)
- Adds _Copy Link to Code_, _Copy Link to File_, and _Copy Link to File at Revision..._ commands to the _Share_ submenu in the editor line number (gutter) context menu
-- Adds an alternate flow (pick another file) when using the _Open File at Revision..._ and _Open Changes with Revision..._ commands to open a file that has been renamed and the rename is currently unstaged — closes [#3109](https://github.com/gitkraken/vscode-gitlens/issues/3109)
+- Adds an alternate flow (pick another file) when using the _Open File at Revision..._ and _Open Changes with Revision..._ commands to open a file that has been renamed and the rename is currently unstaged — closes #3109 (https://github.com/gitkraken/vscode-gitlens/issues/3109)
- Adds access to most _Git Command Palette_ commands directly to the command palette
- Adds _Rename Stash..._ options to stash quick pick menus
- Adds support for the latest GPT-4 Turbo models
@@ -4661,10 +4356,10 @@ Shout-out to our awesome contributors for this release!
### Fixed
-- Fixes [#3115](https://github.com/gitkraken/vscode-gitlens/issues/3115) - Always-on file annotations
+- Fixes #3115 (https://github.com/gitkraken/vscode-gitlens/issues/3115) - Always-on file annotations
- Fixes ahead/behind diffs on files (root) in the _Commits_ view to correctly show the diff of the range rather than the base to the working tree
- Fixes missing repository icons in the _Repositories_ view
-- Fixes [#3116](https://github.com/gitkraken/vscode-gitlens/issues/3116) - Fix typos in README.md and package.json — thanks to [PR #3117](https://github.com/gitkraken/vscode-gitlens/pull/3117) by yutotnh ([@yutotnh](https://github.com/yutotnh))
+- Fixes #3116 (https://github.com/gitkraken/vscode-gitlens/issues/3116) - Fix typos in README.md and package.json — thanks to PR #3117 (https://github.com/gitkraken/vscode-gitlens/pull/3117) by yutotnh (@yutotnh (https://github.com/yutotnh))
## Version 14.7
@@ -4689,8 +4384,8 @@ Use or share these links to quickly and easily open the referenced file or code
Shout-out to our awesome contributors for this release!
-- Ian Chamberlain ([@ian-h-chamberlain](https://github.com/ian-h-chamberlain))
-- Brandon Cheng ([@gluxon](https://github.com/gluxon))
+- Ian Chamberlain (@ian-h-chamberlain (https://github.com/ian-h-chamberlain))
+- Brandon Cheng (@gluxon (https://github.com/gluxon))
### Added
@@ -4701,36 +4396,36 @@ Shout-out to our awesome contributors for this release!
- Adds support for deep links to files and code
- Deep link format: `https://gitkraken.dev/link/r/{repoId}/f/{filePath}?[url={remoteUrl}|path={repoPath}]&lines={lines}&ref={ref}`
- Adds _Copy Link to File_, _Copy Link to File at Revision..._, and _Copy Link to Code_ commands to the _Copy As_ submenu in the editor context menu and to the _Share_ submenu of files in GitLens views
-- Adds the ability to choose multiple stashes to drop in the _Git Command Palette_'s _stash drop_ command — closes [#3102](https://github.com/gitkraken/vscode-gitlens/issues/3102)
+- Adds the ability to choose multiple stashes to drop in the _Git Command Palette_'s _stash drop_ command — closes #3102 (https://github.com/gitkraken/vscode-gitlens/issues/3102)
- Adds a new _prune_ subcommand to the _Git Command Palette_'s _branch_ command to easily delete local branches with missing upstreams
- Adds a new _Push Stash Snapshot_ confirmation option to the _Git Command Palette_'s _stash push_ command to save a stash without changing the working tree
- Adds _Copy_ to search results in the _Search & Compare_ view to copy the search query to more easily share or paste queries into the _Commit Graph_
- Adds a status bar indicator when blame annotations (inline, statusbar, file annotations, etc) are paused because the file has unsaved changes (dirty), with a tooltip explaining why and how to configure/change the behavior
-- Adds an experimental `gitlens.experimental.allowAnnotationsWhenDirty` setting to specify whether file annotations are allowed on files with unsaved changes (dirty) — closes [#1988](https://github.com/gitkraken/vscode-gitlens/issues/1988), [#3016](https://github.com/gitkraken/vscode-gitlens/issues/3016)
+- Adds an experimental `gitlens.experimental.allowAnnotationsWhenDirty` setting to specify whether file annotations are allowed on files with unsaved changes (dirty) — closes #1988 (https://github.com/gitkraken/vscode-gitlens/issues/1988), #3016 (https://github.com/gitkraken/vscode-gitlens/issues/3016)
- Use the existing `gitlens.advanced.blame.delayAfterEdit` setting to control how long to wait (defaults to 5s) before the annotation will update while the file is still dirty, which only applies if the file is under the `gitlens.advanced.sizeThresholdAfterEdit` setting threshold (defaults to 5000 lines)
-- Adds a `gitlens.fileAnnotations.dismissOnEscape` setting to specify whether pressing the `ESC` key dismisses the active file annotations — closes [#3016](https://github.com/gitkraken/vscode-gitlens/issues/3016)
+- Adds a `gitlens.fileAnnotations.dismissOnEscape` setting to specify whether pressing the `ESC` key dismisses the active file annotations — closes #3016 (https://github.com/gitkraken/vscode-gitlens/issues/3016)
### Changed
-- Changes the commit search by file to allow some fuzziness by default — closes [#3086](https://github.com/gitkraken/vscode-gitlens/issues/3086)
+- Changes the commit search by file to allow some fuzziness by default — closes #3086 (https://github.com/gitkraken/vscode-gitlens/issues/3086)
- For example, if you enter `file:readme.txt`, we will treat it as `file:**/readme.txt`, or if you enter `file:readme` it will be treated as `file:*readme*`
- Improves the _Switch_ command to no longer fail when trying to switch to a branch that is linked to another worktree and instead offers to open the worktree
- Changes branch/tag "tips" that are show on commits in many GitLens views to be truncated to 11 characters by default to avoid stealing to much real estate
### Fixed
-- Fixes [#3087](https://github.com/gitkraken/vscode-gitlens/issues/3087) - Terminal executed commands fail if the GitLens terminal is closed
-- Fixes [#2784](https://github.com/gitkraken/vscode-gitlens/issues/2784) - Git stash push error
-- Fixes [#2926](https://github.com/gitkraken/vscode-gitlens/issues/2926) in more cases - "Open File at Revision" has incorrect editor label if revision contains path separator — thanks to [PR #3060](https://github.com/gitkraken/vscode-gitlens/issues/3060) by Ian Chamberlain ([@ian-h-chamberlain](https://github.com/ian-h-chamberlain))
-- Fixes [#3066](https://github.com/gitkraken/vscode-gitlens/issues/3066) - Editing a large file and switching away to another file without saving causes current line blame to disappear; thanks to [PR #3067](https://github.com/gitkraken/vscode-gitlens/pulls/3067) by Brandon Cheng ([@gluxon](https://github.com/gluxon))
-- Fixes [#3063](https://github.com/gitkraken/vscode-gitlens/issues/3063) - Missing icons in GitLens Settings UI
+- Fixes #3087 (https://github.com/gitkraken/vscode-gitlens/issues/3087) - Terminal executed commands fail if the GitLens terminal is closed
+- Fixes #2784 (https://github.com/gitkraken/vscode-gitlens/issues/2784) - Git stash push error
+- Fixes #2926 (https://github.com/gitkraken/vscode-gitlens/issues/2926) in more cases - "Open File at Revision" has incorrect editor label if revision contains path separator — thanks to PR #3060 (https://github.com/gitkraken/vscode-gitlens/issues/3060) by Ian Chamberlain (@ian-h-chamberlain (https://github.com/ian-h-chamberlain))
+- Fixes #3066 (https://github.com/gitkraken/vscode-gitlens/issues/3066) - Editing a large file and switching away to another file without saving causes current line blame to disappear; thanks to PR #3067 (https://github.com/gitkraken/vscode-gitlens/pulls/3067) by Brandon Cheng (@gluxon (https://github.com/gluxon))
+- Fixes #3063 (https://github.com/gitkraken/vscode-gitlens/issues/3063) - Missing icons in GitLens Settings UI
- Fixes issue with _Switch_ command not honoring the confirmation setting
- Fixes worktree delete from offering to delete main worktree (which isn't possible)
- Fixes worktree delete on windows when the worktree's folder is missing
### Removed
-- Removes the `gitlens.experimental.nativeGit` setting as it is now the default experience — closes [#3055](https://github.com/gitkraken/vscode-gitlens/issues/3055)
+- Removes the `gitlens.experimental.nativeGit` setting as it is now the default experience — closes #3055 (https://github.com/gitkraken/vscode-gitlens/issues/3055)
## Version 14.6
@@ -4766,24 +4461,24 @@ You can now open changes in VS Code's new multi-diff editor. This requires VS Co
Shout-out to our awesome contributor for this release!
-- Victor Hallberg ([@mogelbrod](https://github.com/mogelbrod))
+- Victor Hallberg (@mogelbrod (https://github.com/mogelbrod))
### Added
- Adds the ability to specify who can access a Cloud Patch when creating it
-- _Anyone with the link_ — allows anyone with the link and a GitKraken account to access the Cloud Patch
-- _Members of my Org with the link_ — allows only members of your selected GitKraken organization with the link to access the Cloud Patch
+- _Anyone with the link_ — allows anyone with the link and a GitKraken account to access the Cloud Patch
+- _Members of my Org with the link_ — allows only members of your selected GitKraken organization with the link to access the Cloud Patch
- (Coming soon to GitLens) Ability to explicitly share to specific members from your organization and add them as collaborators on a Cloud Patch
- Cloud Patches that have been explicitly shared with you, i.e. you are a collaborator, now will appear in the _Cloud Patches_ view under _Shared with Me_
-- Adds timed snoozing for items in the _Focus View_ — choose from a selection of times when snoozing and the item will automatically move out of the snoozed tab when that time expires
-- Adds the ability to open folder changes — closes [#3020](https://github.com/gitkraken/vscode-gitlens/issues/3020)
+- Adds timed snoozing for items in the _Focus View_ — choose from a selection of times when snoozing and the item will automatically move out of the snoozed tab when that time expires
+- Adds the ability to open folder changes — closes #3020 (https://github.com/gitkraken/vscode-gitlens/issues/3020)
- Adds _Open Folder Changes with Revision..._ & _Open Folder Changes with Branch or Tag..._ commands to the Command Palette and to the _Explorer_ and _Source Control_ views
- Requires VS Code `1.85` or later and `multiDiffEditor.experimental.enabled` to be enabled
- Adds last modified time of the file when showing blame annotations for uncommitted changes
- Adds search results to the minimap tooltips on the _Commit Graph_
- Adds support for Anthropic's Claude 2.1 model for GitLens' experimental AI features
- Adds a status indicator when the upstream branch is missing in _Commits_ view
-- Adds support for opening renamed/deleted files using the _Open File at Revision..._ & _Open File at Revision from..._ commands by showing a quick pick menu if the requested file doesn't exist in the selected revision — closes [#708](https://github.com/gitkraken/vscode-gitlens/issues/708) thanks to [PR #2825](https://github.com/gitkraken/vscode-gitlens/pull/2825) by Victor Hallberg ([@mogelbrod](https://github.com/mogelbrod))
+- Adds support for opening renamed/deleted files using the _Open File at Revision..._ & _Open File at Revision from..._ commands by showing a quick pick menu if the requested file doesn't exist in the selected revision — closes #708 (https://github.com/gitkraken/vscode-gitlens/issues/708) thanks to PR #2825 (https://github.com/gitkraken/vscode-gitlens/pull/2825) by Victor Hallberg (@mogelbrod (https://github.com/mogelbrod))
- Adds an _Open Changes_ submenu to comparisons in the _Search & Compare_ view
- Adds experimental `gitlens.experimental.openChangesInMultiDiffEditor` setting to specify whether to open multiple changes in VS Code's experimental multi-diff editor (single tab) or in individual diff editors (multiple tabs)
- Adds an inline _Open All Changes_ command to commits, stashes, and comparisons in the views
@@ -4792,7 +4487,7 @@ Shout-out to our awesome contributor for this release!
- Requires VS Code `1.85` or later and `multiDiffEditor.experimental.enabled` to be enabled
- Adds a confirmation prompt when attempting to undo a commit with uncommitted changes
- Adds a _[Show|Hide] Merge Commits_ toggle to the _Contributors_ view
-- Adds _Open in Integrated Terminal_ command to repositories in the views — closes [#3053](https://github.com/gitkraken/vscode-gitlens/issues/3053)
+- Adds _Open in Integrated Terminal_ command to repositories in the views — closes #3053 (https://github.com/gitkraken/vscode-gitlens/issues/3053)
- Adds _Open in Terminal_ & _Open in Integrated Terminal_ commands to the upstream status in the _Commits_ view
- Adds the ability to choose an active GitKraken organization in the _Account View_ for users with multiple GitKraken organizations.
@@ -4804,12 +4499,12 @@ Shout-out to our awesome contributor for this release!
### Fixed
-- Fixes [#2663](https://github.com/gitkraken/vscode-gitlens/issues/2663) - Debounce bug: file blame isn't cleared when editing document while text in output window changes
-- Fixes [#3050](https://github.com/gitkraken/vscode-gitlens/issues/3050) - Opening revision of a renamed file is broken
-- Fixes [#3019](https://github.com/gitkraken/vscode-gitlens/issues/3019) - Commits Views not working
-- Fixes [#3026](https://github.com/gitkraken/vscode-gitlens/issues/3026) - Gitlens stopped working in sub-repositories
-- Fixes [#2746](https://github.com/gitkraken/vscode-gitlens/issues/2746) - Remove 'undo commit' command from gitlens inspect
-- Fixes [#2482](https://github.com/gitkraken/vscode-gitlens/issues/2482) - Unresponsive "commits" view and "branches" view update due to git log
+- Fixes #2663 (https://github.com/gitkraken/vscode-gitlens/issues/2663) - Debounce bug: file blame isn't cleared when editing document while text in output window changes
+- Fixes #3050 (https://github.com/gitkraken/vscode-gitlens/issues/3050) - Opening revision of a renamed file is broken
+- Fixes #3019 (https://github.com/gitkraken/vscode-gitlens/issues/3019) - Commits Views not working
+- Fixes #3026 (https://github.com/gitkraken/vscode-gitlens/issues/3026) - Gitlens stopped working in sub-repositories
+- Fixes #2746 (https://github.com/gitkraken/vscode-gitlens/issues/2746) - Remove 'undo commit' command from gitlens inspect
+- Fixes #2482 (https://github.com/gitkraken/vscode-gitlens/issues/2482) - Unresponsive "commits" view and "branches" view update due to git log
- Fixes duplicate entries in the _Search & Compare_ view when adding a new comparison from outside the view and before the view has loaded
- Fixes _Load more_ in the _File History_ view when the file has been renamed
- Fixes broken _Open Changed & Close Unchanged Files_ (`gitlens.views.openOnlyChangedFiles`) command in the views
@@ -4825,7 +4520,7 @@ GitLens 14.5 features the all new Cloud Patches preview ☁️, which allows you
### Cloud Patches preview ☁️
-[Cloud Patches](https://www.gitkraken.com/solutions/cloud-patches) aim to shift developer collaboration earlier in the process for faster feedback, cleaner pull requests, and overcoming tricky code challenges as a team. Create Cloud Patches from working changes, commits, stashes, or comparisons — then share the patch URL with others to get feedback and iterate on the changes together. It is currently available across GitLens, GitKraken Desktop, and GitKraken CLI, with plans to add commenting and more capabilities soon.
+Cloud Patches (https://www.gitkraken.com/solutions/cloud-patches) aim to shift developer collaboration earlier in the process for faster feedback, cleaner pull requests, and overcoming tricky code challenges as a team. Create Cloud Patches from working changes, commits, stashes, or comparisons — then share the patch URL with others to get feedback and iterate on the changes together. It is currently available across GitLens, GitKraken Desktop, and GitKraken CLI, with plans to add commenting and more capabilities soon.
### Open Multiple Commit Graph & Focus Tabs
@@ -4835,12 +4530,12 @@ Open multiple instances of the Commit Graph, Focus, and Visual File History view
Shout-out to all of our awesome contributors for this release!
-- Aidos Kanapyanov ([@aidoskanapyanov](https://github.com/aidoskanapyanov))
-- Shashank Shastri ([@Shashank-Shastri](https://github.com/Shashank-Shastri))
+- Aidos Kanapyanov (@aidoskanapyanov (https://github.com/aidoskanapyanov))
+- Shashank Shastri (@Shashank-Shastri (https://github.com/Shashank-Shastri))
### Added
-- Adds a preview of [Cloud Patches](https://www.gitkraken.com/solutions/cloud-patches), an all-new ☁️ feature — engage in early collaboration before the pull request:
+- Adds a preview of Cloud Patches (https://www.gitkraken.com/solutions/cloud-patches), an all-new ☁️ feature — engage in early collaboration before the pull request:
- Share your work with others by creating a Cloud Patch from Working Changes, Commits, Stashes or Comparisons
- View Cloud Patches from URLs shared to you and apply them to your working tree or to a new or existing branch
- Manage your Cloud Patches from the new _Cloud Patches_ view in the GitLens side bar
@@ -4854,19 +4549,19 @@ Shout-out to all of our awesome contributors for this release!
- Adds a _Split Visual File History_ command to the _Visual File History_ tab context menu
- Adds a `gitlens.visualHistory.allowMultiple` setting to specify whether to allow opening multiple instances of the _Visual File History_ in the editor area
- Adds a _Generate Commit Message (Experimental)_ button to the SCM input when supported (currently `1.84.0-insider` only)
-- Adds a `gitlens.ai.experimental.generateCommitMessage.enabled` setting to specify whether to enable GitLens' experimental, AI-powered, on-demand commit message generation — closes [#2652](https://github.com/gitkraken/vscode-gitlens/issues/2652)
+- Adds a `gitlens.ai.experimental.generateCommitMessage.enabled` setting to specify whether to enable GitLens' experimental, AI-powered, on-demand commit message generation — closes #2652 (https://github.com/gitkraken/vscode-gitlens/issues/2652)
- Improves the experience of the _Search Commits_ quick pick menu
- Adds a stateful authors picker to make it much easier to search for commits by specific authors
- Adds a file and folder picker to make it much easier to search for commits containing specific files or in specific folders
-- Adds ability to sort repositories in the views and quick pick menus — closes [#2836](https://github.com/gitkraken/vscode-gitlens/issues/2836) thanks to [PR #2991](https://github.com/gitkraken/vscode-gitlens/pull/2991)
-- Adds a `gitlens.sortRepositoriesBy` setting to specify how repositories are sorted in quick pick menus and views by Aidos Kanapyanov ([@aidoskanapyanov](https://github.com/aidoskanapyanov))
-- Adds a _[Show|Hide] Merge Commits_ toggle to the Commits\_ view — closes [#1399](https://github.com/gitkraken/vscode-gitlens/issues/1399) thanks to [PR #1540](https://github.com/gitkraken/vscode-gitlens/pull/1540) by Shashank Shastri ([@Shashank-Shastri](https://github.com/Shashank-Shastri))
+- Adds ability to sort repositories in the views and quick pick menus — closes #2836 (https://github.com/gitkraken/vscode-gitlens/issues/2836) thanks to PR #2991 (https://github.com/gitkraken/vscode-gitlens/pull/2991)
+- Adds a `gitlens.sortRepositoriesBy` setting to specify how repositories are sorted in quick pick menus and views by Aidos Kanapyanov (@aidoskanapyanov (https://github.com/aidoskanapyanov))
+- Adds a _[Show|Hide] Merge Commits_ toggle to the Commits\_ view — closes #1399 (https://github.com/gitkraken/vscode-gitlens/issues/1399) thanks to PR #1540 (https://github.com/gitkraken/vscode-gitlens/pull/1540) by Shashank Shastri (@Shashank-Shastri (https://github.com/Shashank-Shastri))
- Adds a _Filter Commits by Author..._ commands to the _Commits_ view and comparisons context menus to filter commits in the _Commits_ view by specific authors
- Adds ability to publish to a remote branch to a specific commit using the _Push to Commit_ command
- Adds an _Open Comparison on Remote_ command to comparisons in views
- Adds a _Share > Copy Link to Repository_ command on branches in the views
- Adds _Share > Copy Link to Branch_ and _Share > Copy Link to Repository_ commands on the current branch status in the _Commits_ view
-- Adds a _Clear Reviewed Files_ command to comparisons to clear all reviewed files — closes [#2987](https://github.com/gitkraken/vscode-gitlens/issues/2987)
+- Adds a _Clear Reviewed Files_ command to comparisons to clear all reviewed files — closes #2987 (https://github.com/gitkraken/vscode-gitlens/issues/2987)
- Adds a _Collapse_ command to many view nodes
- Adds a `gitlens.liveshare.enabled` setting to specify whether to enable integration with Visual Studio Live Share
@@ -4874,23 +4569,23 @@ Shout-out to all of our awesome contributors for this release!
- Improves accuracy, performance, and memory usage related to parsing diffs, used in _Changes_ hovers, _Changes_ file annotations, etc
- Improves confirmation messaging in the _Git Command Palette_
-- Refines merge/rebase messaging when there is nothing to do — refs [#1660](https://github.com/gitkraken/vscode-gitlens/issues/1660)
+- Refines merge/rebase messaging when there is nothing to do — refs #1660 (https://github.com/gitkraken/vscode-gitlens/issues/1660)
- Improves view messaging while loading/discovering repositories
- Honors VS Code's `git.useForcePushWithLease` and `git.useForcePushIfIncludes` settings when force pushing
- Changes _File Heatmap_ annotations to not color the entire line by default. Want it back, add `line` to the `gitlens.heatmap.locations` setting
### Fixed
-- Fixes [#2997](https://github.com/gitkraken/vscode-gitlens/issues/2997) - "push to commit" pushes everything instead of up to the selected commit
-- Fixes [#2615](https://github.com/gitkraken/vscode-gitlens/issues/2615) - Source Control views disappear after opening a file beyond a symbolic link
-- Fixes [#2443](https://github.com/gitkraken/vscode-gitlens/issues/2443) - UNC-PATH: File History changes not displaying any changes when open
-- Fixes [#2625](https://github.com/gitkraken/vscode-gitlens/issues/2625) - full issue ref has escape characters that break hover links
-- Fixes [#2987](https://github.com/gitkraken/vscode-gitlens/issues/2987) - Unable to remove all marks on reviewed files with a single operation
-- Fixes [#2923](https://github.com/gitkraken/vscode-gitlens/issues/2923) - TypeError: Only absolute URLs are supported
-- Fixes [#2926](https://github.com/gitkraken/vscode-gitlens/issues/2926) - "Open File at Revision" has incorrect editor label if revision contains path separator
-- Fixes [#2971](https://github.com/gitkraken/vscode-gitlens/issues/2971) - \[Regression\] The branch column header text disappears when you have a hidden ref
-- Fixes [#2814](https://github.com/gitkraken/vscode-gitlens/issues/2814) - GitLens Inspect: "Files Changed" not following when switching between commits in File History
-- Fixes [#2952](https://github.com/gitkraken/vscode-gitlens/issues/2952) - Inline blame not working because of missing ignoreRevsFile
+- Fixes #2997 (https://github.com/gitkraken/vscode-gitlens/issues/2997) - "push to commit" pushes everything instead of up to the selected commit
+- Fixes #2615 (https://github.com/gitkraken/vscode-gitlens/issues/2615) - Source Control views disappear after opening a file beyond a symbolic link
+- Fixes #2443 (https://github.com/gitkraken/vscode-gitlens/issues/2443) - UNC-PATH: File History changes not displaying any changes when open
+- Fixes #2625 (https://github.com/gitkraken/vscode-gitlens/issues/2625) - full issue ref has escape characters that break hover links
+- Fixes #2987 (https://github.com/gitkraken/vscode-gitlens/issues/2987) - Unable to remove all marks on reviewed files with a single operation
+- Fixes #2923 (https://github.com/gitkraken/vscode-gitlens/issues/2923) - TypeError: Only absolute URLs are supported
+- Fixes #2926 (https://github.com/gitkraken/vscode-gitlens/issues/2926) - "Open File at Revision" has incorrect editor label if revision contains path separator
+- Fixes #2971 (https://github.com/gitkraken/vscode-gitlens/issues/2971) - \[Regression\] The branch column header text disappears when you have a hidden ref
+- Fixes #2814 (https://github.com/gitkraken/vscode-gitlens/issues/2814) - GitLens Inspect: "Files Changed" not following when switching between commits in File History
+- Fixes #2952 (https://github.com/gitkraken/vscode-gitlens/issues/2952) - Inline blame not working because of missing ignoreRevsFile
- Fixes issue where _Changes_ hovers and _Changes_ file annotations sometimes weren't accurate
- Fixes intermittent issue where inline blame and other revision-based editor features are unavailable when repository discovery takes a bit
- Fixes intermittent issues where details sometimes get cleared/overwritten when opening the _Commit Details_ view
@@ -4924,7 +4619,7 @@ Inline blame and status bar blame now appear faster on hover. This performance i
- Adds a _Working Changes_ tab to the _Commit Details_ and _Graph Details_ views to show your working tree changes
- Adds _Stage Changes_ and _Unstage Changes_ commands to files on the _Working Changes_ tab
-- Adds a _[Show|Hide] Merge Commits_ toggle to the _File History_ view — closes [#2104](https://github.com/gitkraken/vscode-gitlens/issues/2104) & [#2944](https://github.com/gitkraken/vscode-gitlens/issues/2944)
+- Adds a _[Show|Hide] Merge Commits_ toggle to the _File History_ view — closes #2104 (https://github.com/gitkraken/vscode-gitlens/issues/2104) & #2944 (https://github.com/gitkraken/vscode-gitlens/issues/2944)
- Adds a `gitlens.advanced.fileHistoryShowMergeCommits` setting to specify whether merge commits will be show in file histories
- Adds deep link support for workspaces in the _GitKraken Workspaces_ view
- Deep link format: `https://gitkraken.dev/link/workspaces/{workspaceId}`
@@ -4933,19 +4628,19 @@ Inline blame and status bar blame now appear faster on hover. This performance i
### Changed
- Improves performance of inline blame, status bar blame, and hovers especially when working with remotes with connected integrations
-- Changes the _File History_ view to follow renames and filters out merge commits by default — closes [#2104](https://github.com/gitkraken/vscode-gitlens/issues/2104) & [#2944](https://github.com/gitkraken/vscode-gitlens/issues/2944)
-- Changes the _File History_ view to allow following renames while showing history across all branches (which was a previous limitation of Git) — closes [#2828](https://github.com/gitkraken/vscode-gitlens/issues/2828)
+- Changes the _File History_ view to follow renames and filters out merge commits by default — closes #2104 (https://github.com/gitkraken/vscode-gitlens/issues/2104) & #2944 (https://github.com/gitkraken/vscode-gitlens/issues/2944)
+- Changes the _File History_ view to allow following renames while showing history across all branches (which was a previous limitation of Git) — closes #2828 (https://github.com/gitkraken/vscode-gitlens/issues/2828)
- Changes to use our own implementation of `fetch`, `push`, and `pull` Git operations, rather than delegating to VS Code to avoid limitations especially with GitKraken Workspaces. Please report any issues and you can revert this (for now) by setting `"gitlens.experimental.nativeGit"` to `"false"` in your settings
-- Relaxes PR autolink detection for Azure DevOps to use `PR ` instead of `Merged PR ` — closes [#2908](https://github.com/gitkraken/vscode-gitlens/issues/2908)
+- Relaxes PR autolink detection for Azure DevOps to use `PR ` instead of `Merged PR ` — closes #2908 (https://github.com/gitkraken/vscode-gitlens/issues/2908)
- Changes wording on `Reset Stored OpenAI Key` command to `Reset Stored AI Key` to reflect support for other providers
### Fixed
-- Fixes [#2941](https://github.com/gitkraken/vscode-gitlens/issues/2941) - Invalid Request when trying to generate a commit message using Anthropic API
-- Fixes [#2940](https://github.com/gitkraken/vscode-gitlens/issues/2940) - Can't use Azure OpenAI model because i can't save the openai key because of the verification
-- Fixes [#2928](https://github.com/gitkraken/vscode-gitlens/issues/2928) - Apply Changes should create new files when needed
-- Fixes [#2896](https://github.com/gitkraken/vscode-gitlens/issues/2896) - Repositories view stuck in loading state
-- Fixes [#2460](https://github.com/gitkraken/vscode-gitlens/issues/2460) - Gitlens Remote provider doesn't work properly in "Commit graph" view
+- Fixes #2941 (https://github.com/gitkraken/vscode-gitlens/issues/2941) - Invalid Request when trying to generate a commit message using Anthropic API
+- Fixes #2940 (https://github.com/gitkraken/vscode-gitlens/issues/2940) - Can't use Azure OpenAI model because i can't save the openai key because of the verification
+- Fixes #2928 (https://github.com/gitkraken/vscode-gitlens/issues/2928) - Apply Changes should create new files when needed
+- Fixes #2896 (https://github.com/gitkraken/vscode-gitlens/issues/2896) - Repositories view stuck in loading state
+- Fixes #2460 (https://github.com/gitkraken/vscode-gitlens/issues/2460) - Gitlens Remote provider doesn't work properly in "Commit graph" view
- Fixes issue with "View as [List|Tree]" toggle not working in the _Commit Details_ view
- Fixes an issue with deep links sometimes failing to properly resolve when a matching repository without the remote is found
- Fixes an issue in the _Commit Graph_ where commits not in the history of a merge commit were showing in the same column
@@ -4972,13 +4667,13 @@ From the _Search & Compare_, you now have checkboxes next to each files to help
Shout-out to our awesome contributor for this release!
-- Omar Ghazi ([@omarfesal](https://github.com/omarfesal))
+- Omar Ghazi (@omarfesal (https://github.com/omarfesal))
### Added
-- Adds checkboxes to files in the _Search & Compare_ view to allow for tracking review progress — closes [#836](https://github.com/gitkraken/vscode-gitlens/issues/836)
+- Adds checkboxes to files in the _Search & Compare_ view to allow for tracking review progress — closes #836 (https://github.com/gitkraken/vscode-gitlens/issues/836)
- Allows the _Commit Graph_ to be open in the panel and in the editor area simultaneously
-- Adds an _Open Changes_ button to commits in the file history quick pick menu — closes [#2641](https://github.com/gitkraken/vscode-gitlens/issues/2641) thanks to [PR #2800](https://github.com/gitkraken/vscode-gitlens/pull/2800) by Omar Ghazi ([@omarfesal](https://github.com/omarfesal))
+- Adds an _Open Changes_ button to commits in the file history quick pick menu — closes #2641 (https://github.com/gitkraken/vscode-gitlens/issues/2641) thanks to PR #2800 (https://github.com/gitkraken/vscode-gitlens/pull/2800) by Omar Ghazi (@omarfesal (https://github.com/omarfesal))
### Changed
@@ -4986,7 +4681,7 @@ Shout-out to our awesome contributor for this release!
### Fixed
-- Fixes [#2885](https://github.com/gitkraken/vscode-gitlens/issues/2885) - Folder History not show changed files of commit
+- Fixes #2885 (https://github.com/gitkraken/vscode-gitlens/issues/2885) - Folder History not show changed files of commit
- Fixes issues with opening changes (diffs) of renamed files
- Fixes issues with deep links including when opening VS Code from the deep link
@@ -5010,7 +4705,7 @@ Furthermore, we've added a search bar to the Focus View to help you quickly find
Shout-out to all of our awesome contributors for this release!
-- Victor Hallberg ([@mogelbrod](https://github.com/mogelbrod))
+- Victor Hallberg (@mogelbrod (https://github.com/mogelbrod))
### Added
@@ -5030,7 +4725,7 @@ Shout-out to all of our awesome contributors for this release!
### Fixed
-- Fixes [#2823](https://github.com/gitkraken/vscode-gitlens/issues/2823) - Handle stdout/stderr Buffers in shell run() — thanks to [PR #2824](https://github.com/gitkraken/vscode-gitlens/pull/2824) by Victor Hallberg ([@mogelbrod](https://github.com/mogelbrod))
+- Fixes #2823 (https://github.com/gitkraken/vscode-gitlens/issues/2823) - Handle stdout/stderr Buffers in shell run() — thanks to PR #2824 (https://github.com/gitkraken/vscode-gitlens/pull/2824) by Victor Hallberg (@mogelbrod (https://github.com/mogelbrod))
- Fixes issues with missing worktrees breaking the Worktrees view and Worktree quick pick menus
## Version 14.1
@@ -5058,8 +4753,8 @@ You can now deep link directly into comparisons in the _Search & Compare_ view.
Shout-out to all of our awesome contributors for this release!
-- Neil Ghosh ([@neilghosh](https://github.com/neilghosh))
-- Leo Dan Peña ([@leo9-py](https://github.com/leo9-py))
+- Neil Ghosh (@neilghosh (https://github.com/neilghosh))
+- Leo Dan Peña (@leo9-py (https://github.com/leo9-py))
### Added
@@ -5083,15 +4778,15 @@ Shout-out to all of our awesome contributors for this release!
### Fixed
-- Fixes [#2798](https://github.com/gitkraken/vscode-gitlens/issues/2798) - Improve response from OpenAI if key used is tied to a free account
-- Fixes [#2785](https://github.com/gitkraken/vscode-gitlens/issues/2785) - Remote Provider Integration URL is broken — thanks to [PR #2786](https://github.com/gitkraken/vscode-gitlens/pull/2786) by Neil Ghosh ([@neilghosh](https://github.com/neilghosh))
-- Fixes [#2791](https://github.com/gitkraken/vscode-gitlens/issues/2791) - Unable to use contributors link in README.md — thanks to [PR #2792](https://github.com/gitkraken/vscode-gitlens/pull/2792) by Leo Dan Peña ([@leo9-py](https://github.com/leo9-py))
-- Fixes [#2793](https://github.com/gitkraken/vscode-gitlens/issues/2793) - Requesting username change in contributors README page — thanks to [PR #2794](https://github.com/gitkraken/vscode-gitlens/pull/2794) by Leo Dan Peña ([@leo9-py](https://github.com/leo9-py))
+- Fixes #2798 (https://github.com/gitkraken/vscode-gitlens/issues/2798) - Improve response from OpenAI if key used is tied to a free account
+- Fixes #2785 (https://github.com/gitkraken/vscode-gitlens/issues/2785) - Remote Provider Integration URL is broken — thanks to PR #2786 (https://github.com/gitkraken/vscode-gitlens/pull/2786) by Neil Ghosh (@neilghosh (https://github.com/neilghosh))
+- Fixes #2791 (https://github.com/gitkraken/vscode-gitlens/issues/2791) - Unable to use contributors link in README.md — thanks to PR #2792 (https://github.com/gitkraken/vscode-gitlens/pull/2792) by Leo Dan Peña (@leo9-py (https://github.com/leo9-py))
+- Fixes #2793 (https://github.com/gitkraken/vscode-gitlens/issues/2793) - Requesting username change in contributors README page — thanks to PR #2794 (https://github.com/gitkraken/vscode-gitlens/pull/2794) by Leo Dan Peña (@leo9-py (https://github.com/leo9-py))
- Fixes some rendering issues when scrolling in the _Commit Graph_
- Fixes an issue with some shared workspaces not showing up in the _GitKraken Workspaces_ view when they should
- Fixes an issue when adding repositories to a workspace in the _GitKraken Workspaces_ view where the added repository would show as missing until refreshing the view
-## Version 14.0 — GitLens Reimagined
+## Version 14.0 — GitLens Reimagined
### Wednesday, June 14, 2023
@@ -5194,10 +4889,10 @@ Reset your columns between the _Default_ and the new _Compact_ set via the conte
### Added
-- Adds an all-new Welcome experience to quickly get started with GitLens and discover features — even if you are familiar with GitLens, definitely check it out!
+- Adds an all-new Welcome experience to quickly get started with GitLens and discover features — even if you are familiar with GitLens, definitely check it out!
- Adds a new streamlined _Get Started with GitLens_ walkthrough
- Adds an all-new _Home_ view for quick access to GitLens features and _GitKraken Account_ for managing your account
-- Adds a new reimagined views layout — see discussion [#2721](https://github.com/gitkraken/vscode-gitlens/discussions/2721) for more details
+- Adds a new reimagined views layout — see discussion #2721 (https://github.com/gitkraken/vscode-gitlens/discussions/2721) for more details
- Rearranges the GitLens views for greater focus and productivity, including the new _GitLens Inspect_ and moved some of our views from Source Control into either _GitLens_ or _GitLens Inspect_.
- Adds a new GitLens Inspect activity bar icon focuses on providing contextual information and insights to what you're actively working on
- Adds a _Reset Views Layout_ command to reset all the GitLens views to the new default layout
@@ -5208,7 +4903,7 @@ Reset your columns between the _Default_ and the new _Compact_ set via the conte
- Open a GitKraken cloud workspace as a local, persisted, VS Code workspace file (further improvements coming soon)
- Open a cloud workspace or repository in a new window (or your current window)
- See your currently open repositories in the _Current Window_ section
-- Explore and interact with any repository in a GitKraken cloud workspace, some actions are currently limited to repositories which are open in your current window — ones highlighted in green
+- Explore and interact with any repository in a GitKraken cloud workspace, some actions are currently limited to repositories which are open in your current window — ones highlighted in green
- (Coming soon) Share your GitKraken cloud workspaces with your team or organization
- Adds new _Commit Graph_ `PRO` features and improvements
- Makes the _Panel_ layout the default for easy access to the Commit Graph with a dedicated details view
@@ -5236,15 +4931,15 @@ Reset your columns between the _Default_ and the new _Compact_ set via the conte
- Adds the ability to choose which AI provider, OpenAI or Anthropic, and AI model are used for GitLens' experimental AI features
- Adds a _Switch AI Model_ command to the command palette and from the _Explain (AI)_ panel on the _Commit Details_ view
- Adds a `gitlens.ai.experimental.provider` setting to specify the AI provider to use (defaults to `openai`)
-- Adds a `gitlens.ai.experimental.openai.model` setting to specify the OpenAI model (defaults to `gpt-3.5-turbo`) — closes [#2636](https://github.com/gitkraken/vscode-gitlens/issues/2636) thanks to [PR #2637](https://github.com/gitkraken/vscode-gitlens/pull/2637) by Daniel Rodríguez ([@sadasant](https://github.com/sadasant))
+- Adds a `gitlens.ai.experimental.openai.model` setting to specify the OpenAI model (defaults to `gpt-3.5-turbo`) — closes #2636 (https://github.com/gitkraken/vscode-gitlens/issues/2636) thanks to PR #2637 (https://github.com/gitkraken/vscode-gitlens/pull/2637) by Daniel Rodríguez (@sadasant (https://github.com/sadasant))
- Adds a `gitlens.ai.experimental.anthropic.model` setting to specify the Anthropic model (defaults to `claude-v1`)
- Adds expanded deep link support
- Adds cloning, adding a remote, and fetching from the target remote when resolving a deep link
- Adds deep linking to a repository with direct file path support
- Adds the automatic restoration of all GitLens webviews when you restart VS Code
-- Adds ability to control encoding for custom remote configuration — closes [#2336](https://github.com/gitkraken/vscode-gitlens/issues/2336)
+- Adds ability to control encoding for custom remote configuration — closes #2336 (https://github.com/gitkraken/vscode-gitlens/issues/2336)
- Improves performance and rendering of the _Visual File History_ and optimizes it for usage in the side bars
-- Adds a _Full history_ option to the _Visual File History_ — closes [#2690](https://github.com/gitkraken/vscode-gitlens/issues/2690)
+- Adds a _Full history_ option to the _Visual File History_ — closes #2690 (https://github.com/gitkraken/vscode-gitlens/issues/2690)
- Adds a loading progress indicator
- Adds _Reveal in File Explorer_ command to repositories
- Adds _Copy SHA_ command to stashes
@@ -5261,12 +4956,12 @@ Reset your columns between the _Default_ and the new _Compact_ set via the conte
### Fixed
-- Fixes [#2728](https://github.com/gitkraken/vscode-gitlens/issues/2728) - Submodule commit graph will not open in the panel layout
-- Fixes [#2734](https://github.com/gitkraken/vscode-gitlens/issues/2734) - 🐛 File History: Browse ... not working
-- Fixes [#2671](https://github.com/gitkraken/vscode-gitlens/issues/2671) - Incorrect locale information provided GitLens
-- Fixes [#2689](https://github.com/gitkraken/vscode-gitlens/issues/2689) - GitLens hangs on github.dev on Safari
-- Fixes [#2680](https://github.com/gitkraken/vscode-gitlens/issues/2680) - Git path with spaces is not properly quoted in the command
-- Fixes [#2677](https://github.com/gitkraken/vscode-gitlens/issues/2677) - Merging branch produces path error
+- Fixes #2728 (https://github.com/gitkraken/vscode-gitlens/issues/2728) - Submodule commit graph will not open in the panel layout
+- Fixes #2734 (https://github.com/gitkraken/vscode-gitlens/issues/2734) - 🐛 File History: Browse ... not working
+- Fixes #2671 (https://github.com/gitkraken/vscode-gitlens/issues/2671) - Incorrect locale information provided GitLens
+- Fixes #2689 (https://github.com/gitkraken/vscode-gitlens/issues/2689) - GitLens hangs on github.dev on Safari
+- Fixes #2680 (https://github.com/gitkraken/vscode-gitlens/issues/2680) - Git path with spaces is not properly quoted in the command
+- Fixes #2677 (https://github.com/gitkraken/vscode-gitlens/issues/2677) - Merging branch produces path error
- Fixes an issue with comparison commands on File/Line History views
- Fixes an issue with stale state on many webviews when shown after being hidden
- Fixes an issue with fetch/push/pull on the _Commit Graph_ header
@@ -5282,7 +4977,7 @@ GitLens 13.6 brings a range of enhancements and additions to the Commit Graph an
## Context Menu Updates
-To improve structure and findability of our menu options, we’ve made several changes to our context menus. Many Copy Remote URL commands, which were previously in a Copy As submenu, have been moved to a Share submenu within GitLens views, which aligns with VS Code menus. And once [microsoft/vscode#176316](https://github.com/microsoft/vscode/issues/176316) lands we will move the rest of the Copy Remote URL commands into the appropriate Share submenu. This reorganization consolidates related commands and makes it easier to locate and utilize them.
+To improve structure and findability of our menu options, we’ve made several changes to our context menus. Many Copy Remote URL commands, which were previously in a Copy As submenu, have been moved to a Share submenu within GitLens views, which aligns with VS Code menus. And once microsoft/vscode#176316 (https://github.com/microsoft/vscode/issues/176316) lands we will move the rest of the Copy Remote URL commands into the appropriate Share submenu. This reorganization consolidates related commands and makes it easier to locate and utilize them.
Similarly, the Copy SHA and Copy Message commands, previously nested in submenus, have been promoted to the root of the context menu. This elevates their visibility and enables quick access for performing actions on commits. Additionally, the Copy Relative Path command has been relocated to the root of the context menu. These adjustments enhance convenience when working with file paths.
@@ -5310,11 +5005,11 @@ You can now search within stashes using the Commit Graph, the Search & Compare v
### Added
-- Adds the ability to rename stashes — closes [#2538](https://github.com/gitkraken/vscode-gitlens/issues/2538)
+- Adds the ability to rename stashes — closes #2538 (https://github.com/gitkraken/vscode-gitlens/issues/2538)
- Adds a new _Rename Stash..._ command to the _Stashes_ view
- Adds new _Commit Graph_ features and improvements
- Adds a _Push_ or _Pull_ toolbar button depending the current branch being ahead or behind it's upstream
-- Adds support for the _Commit Graph_ over [Visual Studio Live Share](https://visualstudio.microsoft.com/services/live-share/) sessions
+- Adds support for the _Commit Graph_ over Visual Studio Live Share (https://visualstudio.microsoft.com/services/live-share/) sessions
- Adds the ability to move all of the columns, including the ones that were previously unmovable
- Automatically switches column headers from text to icons when the column's width is too small for the text to be useful
- Automatically switches the Author column to shows avatars rather than text when the column is sized to its minimum width
@@ -5349,16 +5044,16 @@ You can now search within stashes using the Commit Graph, the Search & Compare v
- Adds a `gitlens.views.searchAndCompare.files.icon` setting to specify how the _Search & Compare_ view will display file icons
- Renames _Delete Stash..._ command to _Drop Stash..._ in the _Stashes_ view
- Removes the commit icon when hiding avatars in the _Commits_ view to allow for a more compact layout
-- Limits Git CodeLens on docker files — closes [#2153](https://github.com/gitkraken/vscode-gitlens/issues/2153)
-- Shows progress notification for deep links earlier in the process — closes [#2662](https://github.com/gitkraken/vscode-gitlens/issues/2662)
+- Limits Git CodeLens on docker files — closes #2153 (https://github.com/gitkraken/vscode-gitlens/issues/2153)
+- Shows progress notification for deep links earlier in the process — closes #2662 (https://github.com/gitkraken/vscode-gitlens/issues/2662)
### Fixed
-- Fixes [#2664](https://github.com/gitkraken/vscode-gitlens/issues/2664) - Terminal run Git command can be "corrupted" if there is previous text waiting in the terminal
-- Fixes [#2660](https://github.com/gitkraken/vscode-gitlens/issues/2660) - Commands executed in the terminal fail to honor found Git path
-- Fixes [#2654](https://github.com/gitkraken/vscode-gitlens/issues/2654) - Toggle zen mode not working until you restart vscode
-- Fixes [#2629](https://github.com/gitkraken/vscode-gitlens/issues/2629) - When on VSCode web, add handling for failing repo discovery
-- Fixes many issues with using GitLens over [Visual Studio Live Share](https://visualstudio.microsoft.com/services/live-share/) sessions
+- Fixes #2664 (https://github.com/gitkraken/vscode-gitlens/issues/2664) - Terminal run Git command can be "corrupted" if there is previous text waiting in the terminal
+- Fixes #2660 (https://github.com/gitkraken/vscode-gitlens/issues/2660) - Commands executed in the terminal fail to honor found Git path
+- Fixes #2654 (https://github.com/gitkraken/vscode-gitlens/issues/2654) - Toggle zen mode not working until you restart vscode
+- Fixes #2629 (https://github.com/gitkraken/vscode-gitlens/issues/2629) - When on VSCode web, add handling for failing repo discovery
+- Fixes many issues with using GitLens over Visual Studio Live Share (https://visualstudio.microsoft.com/services/live-share/) sessions
- Fixes mouse scrubbing issues with the minimap on the _Commit Graph_
- Fixes _Refresh Repository Access_ and _Reset Repository Access Cache_ commands to always be available
- Fixes state not being restored on the Home webview
@@ -5368,7 +5063,7 @@ You can now search within stashes using the Commit Graph, the Search & Compare v
### Removed
-- Removes "Open Commit on Remote" command from the VS Code Timeline view as it can no longer be supported — see [microsoft/vscode#177319](https://github.com/microsoft/vscode/issues/177319)
+- Removes "Open Commit on Remote" command from the VS Code Timeline view as it can no longer be supported — see microsoft/vscode#177319 (https://github.com/microsoft/vscode/issues/177319)
## Version 13.5
@@ -5408,21 +5103,21 @@ We've heard your feedback on the Commit Details view and the confusion and diffi
Shout-out to all of our awesome contributors for this release!
-- WofWca ([@WofWca](https://github.com/WofWca))
+- WofWca (@WofWca (https://github.com/WofWca))
### Added
-- Adds the ability to switch to an alternate panel layout for the _Commit Graph_ — closes [#2602](https://github.com/gitkraken/vscode-gitlens/issues/2602) and [#2537](https://github.com/gitkraken/vscode-gitlens/issues/2537)
+- Adds the ability to switch to an alternate panel layout for the _Commit Graph_ — closes #2602 (https://github.com/gitkraken/vscode-gitlens/issues/2602) and #2537 (https://github.com/gitkraken/vscode-gitlens/issues/2537)
- Adds a new context menu from the _Commit Graph Settings_ (cog) to switch between the "Editor" and "Panel" layouts
- Adds a `gitlens.graph.layout` setting to specify the layout of the _Commit Graph_
- `editor` - Shows the _Commit Graph_ in an editor tab
- `panel` - Shows the _Commit Graph_ in the bottom panel with an additional _Commit Graph Details_ view alongside on the right
- Adds new _Commit Graph_ features and improvements
- Adds a compact layout to the Graph column of the _Commit Graph_
-- Adds a context menu option to the header to toggle between the "Compact" and "Default" layouts — closes [#2611](https://github.com/gitkraken/vscode-gitlens/pull/2611)
+- Adds a context menu option to the header to toggle between the "Compact" and "Default" layouts — closes #2611 (https://github.com/gitkraken/vscode-gitlens/pull/2611)
- Shows pull request icons on local branches when their upstream branch is associated with a pull request
- Adds tooltips to work-in-progress (WIP) and stash nodes
-- Adds a "Publish Branch" context menu action to local branches without an upstream branch — closes [#2619](https://github.com/gitkraken/vscode-gitlens/pull/2619)
+- Adds a "Publish Branch" context menu action to local branches without an upstream branch — closes #2619 (https://github.com/gitkraken/vscode-gitlens/pull/2619)
- Lowers the minimum width of the "Branch / Tag" column
- Adds actions to _Focus View_ Pull Requests
- Switch to or create a local branch
@@ -5431,25 +5126,25 @@ Shout-out to all of our awesome contributors for this release!
### Changed
-- Reduces the size of the GitLens (desktop) bundle which reduces memory usage and improves startup time — ~7% smaller (1.21MB -> 1.13MB)
+- Reduces the size of the GitLens (desktop) bundle which reduces memory usage and improves startup time — ~7% smaller (1.21MB -> 1.13MB)
- Consolidates the "extension" side of all the GitLens webviews/webview-views into a unified controller and code-splits each webview/webview-view into its own bundle
- Allows for very minimal code to be loaded for each webview/webview-view until its used, so if you never use a webview you never "pay" the cost of loading it
-- Changes _Open Associated Pull Request_ command to support opening associated pull requests with the current branch or the HEAD commit if no branch association was found — closes [#2559](https://github.com/gitkraken/vscode-gitlens/issues/2559)
+- Changes _Open Associated Pull Request_ command to support opening associated pull requests with the current branch or the HEAD commit if no branch association was found — closes #2559 (https://github.com/gitkraken/vscode-gitlens/issues/2559)
- Improves the "pinning" of the _Commit Details_ view
- Avoids automatically pinning
- Changes the pinned state to be much more apparent
-- Changes _Commit Details_ to always open diffs in the same editor group as the currently active editor — closes [#2537](https://github.com/gitkraken/vscode-gitlens/issues/2537)
+- Changes _Commit Details_ to always open diffs in the same editor group as the currently active editor — closes #2537 (https://github.com/gitkraken/vscode-gitlens/issues/2537)
### Fixed
-- Fixes [#2597](https://github.com/gitkraken/vscode-gitlens/issues/2597) - Allow disabling "Open worktree for pull request via GitLens..." from repository context menu
-- Fixes [#2612](https://github.com/gitkraken/vscode-gitlens/issues/2612) - Clarify GitLens telemetry settings
-- Fixes [#2583](https://github.com/gitkraken/vscode-gitlens/issues/2583) - Regression with _Open Worktree for Pull Request via GitLens..._ command
-- Fixes [#2252](https://github.com/gitkraken/vscode-gitlens/issues/2252) - "Copy As"/"Copy Remote File Url" copies %23 instead of # in case of Gitea — thanks to [PR #2603](https://github.com/gitkraken/vscode-gitlens/pull/2603) by WofWca ([@WofWca](https://github.com/WofWca))
-- Fixes [#2582](https://github.com/gitkraken/vscode-gitlens/issues/2582) - _Visual File History_ background color when in a panel
-- Fixes [#2609](https://github.com/gitkraken/vscode-gitlens/issues/2609) - If you check out a branch that is hidden, GitLens should show the branch still
+- Fixes #2597 (https://github.com/gitkraken/vscode-gitlens/issues/2597) - Allow disabling "Open worktree for pull request via GitLens..." from repository context menu
+- Fixes #2612 (https://github.com/gitkraken/vscode-gitlens/issues/2612) - Clarify GitLens telemetry settings
+- Fixes #2583 (https://github.com/gitkraken/vscode-gitlens/issues/2583) - Regression with _Open Worktree for Pull Request via GitLens..._ command
+- Fixes #2252 (https://github.com/gitkraken/vscode-gitlens/issues/2252) - "Copy As"/"Copy Remote File Url" copies %23 instead of # in case of Gitea — thanks to PR #2603 (https://github.com/gitkraken/vscode-gitlens/pull/2603) by WofWca (@WofWca (https://github.com/WofWca))
+- Fixes #2582 (https://github.com/gitkraken/vscode-gitlens/issues/2582) - _Visual File History_ background color when in a panel
+- Fixes #2609 (https://github.com/gitkraken/vscode-gitlens/issues/2609) - If you check out a branch that is hidden, GitLens should show the branch still
- Fixes tooltips sometimes failing to show in _Commit Graph_ rows when the Date column is hidden
-- Fixes [#2595](https://github.com/gitkraken/vscode-gitlens/issues/2595) - Error when stashing changes
+- Fixes #2595 (https://github.com/gitkraken/vscode-gitlens/issues/2595) - Error when stashing changes
## Version 13.4
@@ -5503,14 +5198,14 @@ To opt-in to the Pre-release edition, select GitLens from the extensions sidebar
Shout-out to all of our awesome contributors for this release!
-- Nafiur Rahman Khadem ([@ShafinKhadem](https://github.com/ShafinKhadem))
-- Skyler Dawson ([@foxwoods369](https://github.com/foxwoods369))
-- haha ([@hahaaha](https://github.com/hahaaha))
+- Nafiur Rahman Khadem (@ShafinKhadem (https://github.com/ShafinKhadem))
+- Skyler Dawson (@foxwoods369 (https://github.com/foxwoods369))
+- haha (@hahaaha (https://github.com/hahaaha))
### Added
- Adds an experimental _Generate Commit Message (Experimental)_ command to use OpenAI to generate a commit message for staged changes
-- Adds a `gitlens.experimental.generateCommitMessagePrompt` setting to specify the prompt to use to tell OpenAI how to structure or format the generated commit message — can have fun with it and make your commit messages in the style of a pirate, etc
+- Adds a `gitlens.experimental.generateCommitMessagePrompt` setting to specify the prompt to use to tell OpenAI how to structure or format the generated commit message — can have fun with it and make your commit messages in the style of a pirate, etc
- Adds auto-detection for `.git-blame-ignore-revs` files and excludes the commits listed within from the blame annotations
- Adds a _Open Git Worktree..._ command to jump directly to opening a worktree in the _Git Command Palette_
- Adds a _Copy Relative Path_ context menu action for active editors and file nodes in sidebar views
@@ -5530,17 +5225,17 @@ Shout-out to all of our awesome contributors for this release!
### Fixed
-- Fixes [#2550](https://github.com/gitkraken/vscode-gitlens/issues/2550) - Related pull request disappears after refresh
-- Fixes [#2549](https://github.com/gitkraken/vscode-gitlens/issues/2549) - toggle code lens does not work with gitlens.codeLens.enabled == false
-- Fixes [#2553](https://github.com/gitkraken/vscode-gitlens/issues/2553) - Can't add remote url with git@ format
-- Fixes [#2083](https://github.com/gitkraken/vscode-gitlens/issues/2083), [#2539](https://github.com/gitkraken/vscode-gitlens/issues/2539) - Fix stashing staged changes — thanks to [PR #2540](https://github.com/gitkraken/vscode-gitlens/pull/2540) by Nafiur Rahman Khadem ([@ShafinKhadem](https://github.com/ShafinKhadem))
-- Fixes [#1968](https://github.com/gitkraken/vscode-gitlens/issues/1968) & [#1027](https://github.com/gitkraken/vscode-gitlens/issues/1027) - Fetch-> fatal: could not read Username — thanks to [PR #2481](https://github.com/gitkraken/vscode-gitlens/pull/2481) by Skyler Dawson ([@foxwoods369](https://github.com/foxwoods369))
-- Fixes [#2495](https://github.com/gitkraken/vscode-gitlens/issues/2495) - Cannot use GitLens Pro feature on public repo in some folders
-- Fixes [#2530](https://github.com/gitkraken/vscode-gitlens/issues/2530) - Error when creating worktrees in certain conditions
-- Fixed [#2566](https://github.com/gitkraken/vscode-gitlens/issues/2566) - hide context menu in output panel — thanks to [PR #2568](https://github.com/gitkraken/vscode-gitlens/pull/2568) by hahaaha ([@hahaaha](https://github.com/hahaaha))
-- Fixes [#2533](https://github.com/gitkraken/vscode-gitlens/issues/2533) - Current Branch Only graph filter sometimes fails
-- Fixes [#2504](https://github.com/gitkraken/vscode-gitlens/issues/2504) - Graph header theme colors were referencing the titlebar color properties
-- Fixes [#2527](https://github.com/gitkraken/vscode-gitlens/issues/2527) - shows added files for Open All Changes
+- Fixes #2550 (https://github.com/gitkraken/vscode-gitlens/issues/2550) - Related pull request disappears after refresh
+- Fixes #2549 (https://github.com/gitkraken/vscode-gitlens/issues/2549) - toggle code lens does not work with gitlens.codeLens.enabled == false
+- Fixes #2553 (https://github.com/gitkraken/vscode-gitlens/issues/2553) - Can't add remote url with git@ format
+- Fixes #2083 (https://github.com/gitkraken/vscode-gitlens/issues/2083), #2539 (https://github.com/gitkraken/vscode-gitlens/issues/2539) - Fix stashing staged changes — thanks to PR #2540 (https://github.com/gitkraken/vscode-gitlens/pull/2540) by Nafiur Rahman Khadem (@ShafinKhadem (https://github.com/ShafinKhadem))
+- Fixes #1968 (https://github.com/gitkraken/vscode-gitlens/issues/1968) & #1027 (https://github.com/gitkraken/vscode-gitlens/issues/1027) - Fetch-> fatal: could not read Username — thanks to PR #2481 (https://github.com/gitkraken/vscode-gitlens/pull/2481) by Skyler Dawson (@foxwoods369 (https://github.com/foxwoods369))
+- Fixes #2495 (https://github.com/gitkraken/vscode-gitlens/issues/2495) - Cannot use GitLens Pro feature on public repo in some folders
+- Fixes #2530 (https://github.com/gitkraken/vscode-gitlens/issues/2530) - Error when creating worktrees in certain conditions
+- Fixed #2566 (https://github.com/gitkraken/vscode-gitlens/issues/2566) - hide context menu in output panel — thanks to PR #2568 (https://github.com/gitkraken/vscode-gitlens/pull/2568) by hahaaha (@hahaaha (https://github.com/hahaaha))
+- Fixes #2533 (https://github.com/gitkraken/vscode-gitlens/issues/2533) - Current Branch Only graph filter sometimes fails
+- Fixes #2504 (https://github.com/gitkraken/vscode-gitlens/issues/2504) - Graph header theme colors were referencing the titlebar color properties
+- Fixes #2527 (https://github.com/gitkraken/vscode-gitlens/issues/2527) - shows added files for Open All Changes
- Fixes an issue where trial status can be shown rather than a purchased license
- Fixes graph issue where scroll markers do not update until mouseover when changing the `gitlens.graph.scrollMarkers.additionalTypes` setting.
@@ -5584,7 +5279,7 @@ The green line showcases HEAD while search results are depicted by yellow lines.
- In the upper row, the blue blocks signify remote branches, while the brown blocks refer to tags.
- Within the lower row, the pink blocks denote stashes, and the blue blocks represent local branches.
-We really want to hear your feedback - this is still a very early feature and we're currently still playing with colors, and additional features. To leave us feedback such as what do you think, is this useful, what does it have that you like, what is it missing, etc. reach out to us on the GitLens, [GitHub Discussion board](https://github.com/gitkraken/vscode-gitlens/discussions/2477#discussion-4807133).
+We really want to hear your feedback - this is still a very early feature and we're currently still playing with colors, and additional features. To leave us feedback such as what do you think, is this useful, what does it have that you like, what is it missing, etc. reach out to us on the GitLens, GitHub Discussion board (https://github.com/gitkraken/vscode-gitlens/discussions/2477#discussion-4807133).
#### Changes column (lines added/deleted)
@@ -5629,8 +5324,8 @@ The link will then open in the Commit Graph and can be used to quickly access an
- Adds the ability to show any associated pull requests with branches
- Adds a double-click action on the PR icon to open the PR in the browser
- Adds context menu actions to _Open Pull Request on Remote_ and _Copy_ the PR URL
-- Adds a `gitlens.graph.pullRequests.enabled` setting to toggle PR icons — closes [#2450](https://github.com/gitkraken/vscode-gitlens/issues/2450)
-- Adds a context menu to the WIP row — closes [#2458](https://github.com/gitkraken/vscode-gitlens/issues/2458)
+- Adds a `gitlens.graph.pullRequests.enabled` setting to toggle PR icons — closes #2450 (https://github.com/gitkraken/vscode-gitlens/issues/2450)
+- Adds a context menu to the WIP row — closes #2458 (https://github.com/gitkraken/vscode-gitlens/issues/2458)
- Adds a double-click action on commit rows to open the _Commit Details_ view
- Improves Author and Avatar tooltips to now also show the contributor's email address, if available
- Improves Date tooltips to now always show both the absolute and relative date
@@ -5655,13 +5350,13 @@ The link will then open in the Commit Graph and can be used to quickly access an
### Removed
-- Removes the use of an external color library for the _File Heatmap_ annotations and webview themes — reduces the bundled extension size
+- Removes the use of an external color library for the _File Heatmap_ annotations and webview themes — reduces the bundled extension size
### Fixed
-- Fixes [#2355](https://github.com/gitkraken/vscode-gitlens/issues/2355) - Search by changes stops working in version 13.x.x
-- Fixes [#2473](https://github.com/gitkraken/vscode-gitlens/issues/2473) - Commit graph status bar show wrong last fetched date
-- Fixes [#2409](https://github.com/gitkraken/vscode-gitlens/issues/2409) - Commit Graph Show Current Branch Only shows unrelated commits from other branches
+- Fixes #2355 (https://github.com/gitkraken/vscode-gitlens/issues/2355) - Search by changes stops working in version 13.x.x
+- Fixes #2473 (https://github.com/gitkraken/vscode-gitlens/issues/2473) - Commit graph status bar show wrong last fetched date
+- Fixes #2409 (https://github.com/gitkraken/vscode-gitlens/issues/2409) - Commit Graph Show Current Branch Only shows unrelated commits from other branches
- Fixes an issue where pinning not being respected in Commit Details view
- Fixes graph issue where search results that are merge commits are not highlighted when the `gitlens.graph.dimMergeCommits` setting is enabled
- Fixes graph issue where rows with tags belonging to a hovered branch are not highlighted when the `gitlens.graph.highlightRowsOnRefHover` setting is enabled
@@ -5672,7 +5367,7 @@ The link will then open in the Commit Graph and can be used to quickly access an
### Tuesday, Dec 20th, 2022
-Since the release of [GitLens 13](https://www.gitkraken.com/blog/gitlens-13), we know how the power of GitLens Pro features like the Commit Graph, have been helping supercharge your dev workflow. That’s why we’re excited to present GitLens 13.2, with all new (and highly requested) Graph improvements like filtering, to quickly focus on what is most important to you. We've also streamlined the Commit Graph interface with a new header bar, providing context and quick access to switch between repositories or branches, and even fetch to keep up to date. Get ready to level up your Git game with GitLens 13.2!
+Since the release of GitLens 13 (https://www.gitkraken.com/blog/gitlens-13), we know how the power of GitLens Pro features like the Commit Graph, have been helping supercharge your dev workflow. That’s why we’re excited to present GitLens 13.2, with all new (and highly requested) Graph improvements like filtering, to quickly focus on what is most important to you. We've also streamlined the Commit Graph interface with a new header bar, providing context and quick access to switch between repositories or branches, and even fetch to keep up to date. Get ready to level up your Git game with GitLens 13.2!
### Filtering
@@ -5750,15 +5445,15 @@ Using the new keyboard shortcuts, `SHIFT+UP` and `SHIFT+DOWN` on the Commit Grap
### Fixed
-- Fixes [#2394](https://github.com/gitkraken/vscode-gitlens/issues/2394) - Work in progress file diff compares working tree with working tree, instead of working tree with head
-- Fixes [#2207](https://github.com/gitkraken/vscode-gitlens/issues/2207) - Error when trying to push individual commit
-- Fixes [#2301](https://github.com/gitkraken/vscode-gitlens/issues/2301) - Create Worktree button doesn't work in certain cases
-- Fixes [#2382](https://github.com/gitkraken/vscode-gitlens/issues/2382) - commits disappearing from commit details view when they shouldn't
-- Fixes [#2318](https://github.com/gitkraken/vscode-gitlens/issues/2318) - GitLens need to login again after VS Code insiders upgrade every day
-- Fixes [#2377](https://github.com/gitkraken/vscode-gitlens/issues/2377) - Missing Azure Devops Icon
-- Fixes [#2380](https://github.com/gitkraken/vscode-gitlens/issues/2380) - Autolink fails with curly braces
-- Fixes [#2362](https://github.com/gitkraken/vscode-gitlens/issues/2362) - Visual File History becomes unavailable when the workspace contains private repo
-- Fixes [#2381](https://github.com/gitkraken/vscode-gitlens/issues/2381) - can't use scrollbar in 'Commit Graph' view
+- Fixes #2394 (https://github.com/gitkraken/vscode-gitlens/issues/2394) - Work in progress file diff compares working tree with working tree, instead of working tree with head
+- Fixes #2207 (https://github.com/gitkraken/vscode-gitlens/issues/2207) - Error when trying to push individual commit
+- Fixes #2301 (https://github.com/gitkraken/vscode-gitlens/issues/2301) - Create Worktree button doesn't work in certain cases
+- Fixes #2382 (https://github.com/gitkraken/vscode-gitlens/issues/2382) - commits disappearing from commit details view when they shouldn't
+- Fixes #2318 (https://github.com/gitkraken/vscode-gitlens/issues/2318) - GitLens need to login again after VS Code insiders upgrade every day
+- Fixes #2377 (https://github.com/gitkraken/vscode-gitlens/issues/2377) - Missing Azure Devops Icon
+- Fixes #2380 (https://github.com/gitkraken/vscode-gitlens/issues/2380) - Autolink fails with curly braces
+- Fixes #2362 (https://github.com/gitkraken/vscode-gitlens/issues/2362) - Visual File History becomes unavailable when the workspace contains private repo
+- Fixes #2381 (https://github.com/gitkraken/vscode-gitlens/issues/2381) - can't use scrollbar in 'Commit Graph' view
- Fixes an issue where focusout hides toolbar actions for the graph
- Fixes an issue where _Switch to Another Branch..._ doesn't work in the Graph editor toolbar
- Fixes graph issue with row highlighting/dimming sticking when the graph loses focus
@@ -5770,7 +5465,7 @@ Using the new keyboard shortcuts, `SHIFT+UP` and `SHIFT+DOWN` on the Commit Grap
### Thursday, November 17th, 2022
-With GitLens 13, we released the power of GitLens Pro features like the Commit Graph, Visual File History, and Worktrees to ALL users on local and public repos. No account required. Learn more about the changes happening with GitLens in this [article](https://www.gitkraken.com/blog/gitlens-13).
+With GitLens 13, we released the power of GitLens Pro features like the Commit Graph, Visual File History, and Worktrees to ALL users on local and public repos. No account required. Learn more about the changes happening with GitLens in this article (https://www.gitkraken.com/blog/gitlens-13).
## Commit Graph Enhancements
@@ -5811,7 +5506,7 @@ Keeping a home tidy is important! We’ve streamlined the Home view to make it e
## Added
- Adds Commit Graph enhancements
-- Adds the ability to set keyboard shortcuts to commits and stashes on the Commit Graph — closes [#2345](https://github.com/gitkraken/vscode-gitlens/issues/2345) - Keyboard shortcuts can be applied to many of the gitlens.graph.\* commands and should use gitlens:webview:graph:focus && !gitlens:webview:graph:inputFocus for their "When Expression" to only apply when the Commit Graph is focused - For example, add the following to your keybindings.json to allow Ctrl+C to copy the selected commit's SHA to the clipboard
+- Adds the ability to set keyboard shortcuts to commits and stashes on the Commit Graph — closes #2345 (https://github.com/gitkraken/vscode-gitlens/issues/2345) - Keyboard shortcuts can be applied to many of the gitlens.graph.\* commands and should use gitlens:webview:graph:focus && !gitlens:webview:graph:inputFocus for their "When Expression" to only apply when the Commit Graph is focused - For example, add the following to your keybindings.json to allow Ctrl+C to copy the selected commit's SHA to the clipboard
{
"key": "ctrl+c",
"command": "gitlens.graph.copySha",
@@ -5823,7 +5518,7 @@ Keeping a home tidy is important! We’ve streamlined the Home view to make it e
- Adds a @me search filter to the search box
- Adds history navigation to the search box in the Commit Graph
- When the search field is focused, use the up arrow and down arrow to navigate through any previous searches that yielded results
-- Adds ability to reset to any commit in the Commit Graph and GitLens views — closes [#2326](https://github.com/gitkraken/vscode-gitlens/issues/2326)
+- Adds ability to reset to any commit in the Commit Graph and GitLens views — closes #2326 (https://github.com/gitkraken/vscode-gitlens/issues/2326)
- Adds Interactive Rebase Editor performance and UX improvements
- Changes the header and footer to always be visible
- Shows the Commit Details view on commit selection
@@ -5831,7 +5526,7 @@ Keeping a home tidy is important! We’ve streamlined the Home view to make it e
- Adds full (multiline) commit message
- Adds the f fixup shortcut key to UI
- Consolidates the UI for author and committer information into a stack of avatars
-- Adds emoji support for commit messages — closes [#1789](https://github.com/gitkraken/vscode-gitlens/issues/1789)
+- Adds emoji support for commit messages — closes #1789 (https://github.com/gitkraken/vscode-gitlens/issues/1789)
- Ensures that large rebases show rich commit details
- Adds Commit Details view improvements
- Adds custom and non-rich integration-based autolinks and improves autolink display
@@ -5849,29 +5544,29 @@ Keeping a home tidy is important! We’ve streamlined the Home view to make it e
## Changed
- Changes the Home view to always be available and polishes the experience
-- Changes SHA terminal links to use the Commit Details view — closes [#2320](https://github.com/gitkraken/vscode-gitlens/issues/2320)
+- Changes SHA terminal links to use the Commit Details view — closes #2320 (https://github.com/gitkraken/vscode-gitlens/issues/2320)
- Adds a gitlens.terminalLinks.showDetailsView setting to specify whether to show the Commit Details view when clicking on a commit link
-- Changes to uses VS Code as Git's core.editor for terminal run commands — closes [#2134](https://github.com/gitkraken/vscode-gitlens/issues/2134) thanks to PR [#2135](https://github.com/gitkraken/vscode-gitlens/pull/2135) by Nafiur Rahman Khadem [@ShafinKhadem](https://github.com/ShafinKhadem)
+- Changes to uses VS Code as Git's core.editor for terminal run commands — closes #2134 (https://github.com/gitkraken/vscode-gitlens/issues/2134) thanks to PR #2135 (https://github.com/gitkraken/vscode-gitlens/pull/2135) by Nafiur Rahman Khadem @ShafinKhadem (https://github.com/ShafinKhadem)
- Adds a gitlens.terminal.overrideGitEditor setting to specify whether to use VS Code as Git's core.editor for GitLens terminal commands
- Polishes webview (Commit Graph, Interactive Rebase Editor, etc) scroll bars to match VS Code's style and behavior
## Fixed
-- Fixes [#2339](https://github.com/gitkraken/vscode-gitlens/issues/2339) - Commit details "Autolinks" group shows wrong count
-- Fixes [#2346](https://github.com/gitkraken/vscode-gitlens/issues/2346) - Multiple cursors on the same line duplicate inline annotations; thanks to PR [#2347](https://github.com/gitkraken/vscode-gitlens/pull/2347) by Yonatan Greenfeld [@YonatanGreenfeld](https://github.com/YonatanGreenfeld)
-- Fixes [#2344](https://github.com/gitkraken/vscode-gitlens/issues/2344) - copying abbreviated commit SHAs is not working
-- Fixes [#2342](https://github.com/gitkraken/vscode-gitlens/issues/2342) - Local remotes are incorrectly treated as private
-- Fixes [#2052](https://github.com/gitkraken/vscode-gitlens/issues/2052) - Interactive Rebase fails to start when using xonsh shell due to command quoting
-- Fixes [#2141](https://github.com/gitkraken/vscode-gitlens/issues/2141) - GitLens' rebase UI randomly fails loading interactive rebase when performed outside of VSC
-- Fixes [#1732](https://github.com/gitkraken/vscode-gitlens/issues/1732) - Phantom rebase-merge directory (rm -rf ".git/rebase-merge")
-- Fixes [#1652](https://github.com/gitkraken/vscode-gitlens/issues/1652) - Closing interactive rebase editor after "git rebase --edit" aborts rebase-in-progress
-- Fixes [#1549](https://github.com/gitkraken/vscode-gitlens/issues/1549) - Fetch does not work when local branch name differs from remote branch name
-- Fixes [#2292](https://github.com/gitkraken/vscode-gitlens/issues/2292) - Push button in BranchTrackingStatusNode of non-current branch does not trigger "Push force"
-- Fixes [#1488](https://github.com/gitkraken/vscode-gitlens/issues/1488) - Open Folder History not working with non-English language pack
-- Fixes [#2303](https://github.com/gitkraken/vscode-gitlens/issues/2303) - "Googlesource" gerrit only supports two levels of domain — thanks to PR [#2304](https://github.com/gitkraken/vscode-gitlens/pull/2304) by Matt Buckley [@Mattadore](https://github.com/Mattadore)
-- Fixes [#2315](https://github.com/gitkraken/vscode-gitlens/issues/2315) - Commit details secondary side bar banner doesn't stay dismissed
-- Fixes [#2329](https://github.com/gitkraken/vscode-gitlens/issues/2329) - Remember UI settings in Commit Details panel
-- Fixes [#1606](https://github.com/gitkraken/vscode-gitlens/issues/1606) - Adjusts capitalization of "URL" — thanks to PR [#2341](https://github.com/gitkraken/vscode-gitlens/pull/2341) by Dave Nicolson [@dnicolson](https://github.com/dnicolson)
+- Fixes #2339 (https://github.com/gitkraken/vscode-gitlens/issues/2339) - Commit details "Autolinks" group shows wrong count
+- Fixes #2346 (https://github.com/gitkraken/vscode-gitlens/issues/2346) - Multiple cursors on the same line duplicate inline annotations; thanks to PR #2347 (https://github.com/gitkraken/vscode-gitlens/pull/2347) by Yonatan Greenfeld @YonatanGreenfeld (https://github.com/YonatanGreenfeld)
+- Fixes #2344 (https://github.com/gitkraken/vscode-gitlens/issues/2344) - copying abbreviated commit SHAs is not working
+- Fixes #2342 (https://github.com/gitkraken/vscode-gitlens/issues/2342) - Local remotes are incorrectly treated as private
+- Fixes #2052 (https://github.com/gitkraken/vscode-gitlens/issues/2052) - Interactive Rebase fails to start when using xonsh shell due to command quoting
+- Fixes #2141 (https://github.com/gitkraken/vscode-gitlens/issues/2141) - GitLens' rebase UI randomly fails loading interactive rebase when performed outside of VSC
+- Fixes #1732 (https://github.com/gitkraken/vscode-gitlens/issues/1732) - Phantom rebase-merge directory (rm -rf ".git/rebase-merge")
+- Fixes #1652 (https://github.com/gitkraken/vscode-gitlens/issues/1652) - Closing interactive rebase editor after "git rebase --edit" aborts rebase-in-progress
+- Fixes #1549 (https://github.com/gitkraken/vscode-gitlens/issues/1549) - Fetch does not work when local branch name differs from remote branch name
+- Fixes #2292 (https://github.com/gitkraken/vscode-gitlens/issues/2292) - Push button in BranchTrackingStatusNode of non-current branch does not trigger "Push force"
+- Fixes #1488 (https://github.com/gitkraken/vscode-gitlens/issues/1488) - Open Folder History not working with non-English language pack
+- Fixes #2303 (https://github.com/gitkraken/vscode-gitlens/issues/2303) - "Googlesource" gerrit only supports two levels of domain — thanks to PR #2304 (https://github.com/gitkraken/vscode-gitlens/pull/2304) by Matt Buckley @Mattadore (https://github.com/Mattadore)
+- Fixes #2315 (https://github.com/gitkraken/vscode-gitlens/issues/2315) - Commit details secondary side bar banner doesn't stay dismissed
+- Fixes #2329 (https://github.com/gitkraken/vscode-gitlens/issues/2329) - Remember UI settings in Commit Details panel
+- Fixes #1606 (https://github.com/gitkraken/vscode-gitlens/issues/1606) - Adjusts capitalization of "URL" — thanks to PR #2341 (https://github.com/gitkraken/vscode-gitlens/pull/2341) by Dave Nicolson @dnicolson (https://github.com/dnicolson)
- Fixes issue where we weren't honoring the default gravatar style (gitlens.defaultGravatarsStyle) in certain cases
- Fixes graph issue where stashes are sometimes assigned the wrong column
- Fixes graph issue with commit rows being incorrectly hidden in some cases
@@ -5888,13 +5583,13 @@ Find what you seek.
## GitLens Pro Features for All on Local & Public Repos `PRO`
-With GitLens 13.0, we are excited to bring the power of GitLens Pro features like the Commit Graph, Visual File History, and Worktrees to ALL users on local and public repos. No account required. Learn more about the changes happening with GitLens in this [article](https://www.gitkraken.com/blog/gitlens-13).
+With GitLens 13.0, we are excited to bring the power of GitLens Pro features like the Commit Graph, Visual File History, and Worktrees to ALL users on local and public repos. No account required. Learn more about the changes happening with GitLens in this article (https://www.gitkraken.com/blog/gitlens-13).
Here’s how to get started with each of the GitLens Pro features with your local or public repos:
-- [Commit Graph](https://help.gitkraken.com/gitlens/gitlens-plus/#commit-graph)
-- [Worktrees](https://help.gitkraken.com/gitlens/gitlens-plus/#worktrees)
-- [Visual File History](https://help.gitkraken.com/gitlens/gitlens-plus/#visual-file-history)
+- Commit Graph (https://help.gitkraken.com/gitlens/gitlens-plus/#commit-graph)
+- Worktrees (https://help.gitkraken.com/gitlens/gitlens-plus/#worktrees)
+- Visual File History (https://help.gitkraken.com/gitlens/gitlens-plus/#visual-file-history)
## Commit Graph - Now out of Preview! `PRO`
@@ -5973,9 +5668,9 @@ To open the Commit Details view, open the command palette using Cmd+Shift+P and
### Fixed
-- Fixes [#2203](https://github.com/gitkraken/vscode-gitlens/issues/2203) - Autolinks missing under commit details
-- Fixes [#2230](https://github.com/gitkraken/vscode-gitlens/issues/2230) - j and k are inverted in ascending rebase order
-- Fixes [#2195](https://github.com/gitkraken/vscode-gitlens/issues/2195) - Cannot open new files from commit details
+- Fixes #2203 (https://github.com/gitkraken/vscode-gitlens/issues/2203) - Autolinks missing under commit details
+- Fixes #2230 (https://github.com/gitkraken/vscode-gitlens/issues/2230) - j and k are inverted in ascending rebase order
+- Fixes #2195 (https://github.com/gitkraken/vscode-gitlens/issues/2195) - Cannot open new files from commit details
- Fixes Commit Details view showing incorrect diffs for certain commits
- Fixes Commit Details view showing incorrect actions for uncommitted changes
- Fixes prioritization of multiple PRs associated with the same commit to choose a merged PR over others
@@ -6005,9 +5700,9 @@ You may also access the Commit Graph by clicking this graph icon from the Source
The Commit Graph is available to all users working on public repositories, and requires no account. Additionally, users with a paid GitLens Pro subscription can use the Commit Graph with private repos.
-For those on [vscode.dev](vscode.dev) or [github.dev](github.dev), this also means you can open the Commit Graph on a web browser.
+For those on vscode.dev (vscode.dev) or github.dev (github.dev), this also means you can open the Commit Graph on a web browser.
-The Commit Graph is in `Preview` mode, and we’d love to hear your feedback in the [Commit Graph discussion on GitHub](https://github.com/gitkraken/vscode-gitlens/discussions/2158).
+The Commit Graph is in `Preview` mode, and we’d love to hear your feedback in the Commit Graph discussion on GitHub (https://github.com/gitkraken/vscode-gitlens/discussions/2158).
## Commit Details View
@@ -6044,7 +5739,7 @@ Please note that your IdP will first need to be configured before setting up the
Additional requirements: - Configurable only by GitKraken Owner or Admin of an organization - Subscribed to either the Teams or Enterprise plan
-→ [Documentation: How to set up SSO in GitKraken](https://help.gitkraken.com/gitkraken-client/single-sign-on/)
+→ Documentation: How to set up SSO in GitKraken (https://help.gitkraken.com/gitkraken-client/single-sign-on/)
### Signing in with SSO
@@ -6076,26 +5771,26 @@ And users may now search for text on the `Interactive Rebase Editor` using Ctrl
- Adds Commit Graph
- Adds Commit Details View
-- Adds [**rich integration**](https://github.com/gitkraken/vscode-gitlens#remote-provider-integrations-) with GitHub Enterprise — closes [#1210](https://github.com/gitkraken/vscode-gitlens/issues/1210)
+- Adds **rich integration** (https://github.com/gitkraken/vscode-gitlens#remote-provider-integrations-) with GitHub Enterprise — closes #1210 (https://github.com/gitkraken/vscode-gitlens/issues/1210)
- Adds associated pull request to line annotations and hovers
-Pull requests on line annotation and hovers
+!Pull requests on line annotation and hovers (https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/hovers-current-line-details.png)
- Adds associated pull request to status bar blame
-Pull requests on status bar
+!Pull requests on status bar (https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/status-bar.png)
- Adds GitHub avatars
- Adds associated pull requests to branches and commits in GitLens views
- Adds rich autolinks for GitHub issues and merge requests, including titles, status, and authors
- Adds rich support to _Autolinked Issues and Pull Requests_ within comparisons to list autolinked GitHub issues and merge requests in commit messages
-- Adds new stash behaviors to use the Source Control (commit message) input box — closes [#2081](https://github.com/gitkraken/vscode-gitlens/issues/2081)
+- Adds new stash behaviors to use the Source Control (commit message) input box — closes #2081 (https://github.com/gitkraken/vscode-gitlens/issues/2081)
- When a stash is applied or popped and the Source Control input is empty, we will now update the Source Control input to the stash message
- When stashing changes and the Source Control input is not empty, we will now default the stash message input to the Source Control input value
-- Adds the ability to search (Ctrl+F) for text on the Interactive Rebase Editor — closes [#2050](https://github.com/gitkraken/vscode-gitlens/issues/2050)
-- Adds stats (additions & deletions) to files nodes in comparisons — closes [#2078](https://github.com/gitkraken/vscode-gitlens/issues/2078) thanks to help via [PR #2079](https://github.com/gitkraken/vscode-gitlens/pull/2079) by Nafiur Rahman Khadem ([@ShafinKhadem](https://github.com/ShafinKhadem))
-- Adds the ability to uniquely format uncommitted changes for the current line blame annotations — closes [#1987](https://github.com/gitkraken/vscode-gitlens/issues/1987)
+- Adds the ability to search (Ctrl+F) for text on the Interactive Rebase Editor — closes #2050 (https://github.com/gitkraken/vscode-gitlens/issues/2050)
+- Adds stats (additions & deletions) to files nodes in comparisons — closes #2078 (https://github.com/gitkraken/vscode-gitlens/issues/2078) thanks to help via PR #2079 (https://github.com/gitkraken/vscode-gitlens/pull/2079) by Nafiur Rahman Khadem (@ShafinKhadem (https://github.com/ShafinKhadem))
+- Adds the ability to uniquely format uncommitted changes for the current line blame annotations — closes #1987 (https://github.com/gitkraken/vscode-gitlens/issues/1987)
- Adds a `gitlens.currentLine.uncommittedChangesFormat` setting to specify the uncommitted changes format of the current line blame annotation. **NOTE**: Setting this to an empty string will disable current line blame annotations for uncommitted changes
- Adds variable expansion support to the `gitlens.worktrees.defaultLocation` setting
-- `${userHome}` — the path of the user's home folder
-- `${workspaceFolder}` — the path of the folder opened in VS Code containing the specified repository
-- `${workspaceFolderBasename}` — the name of the folder opened in VS Code containing the specified repository without any slashes (/)
+- `${userHome}` — the path of the user's home folder
+- `${workspaceFolder}` — the path of the folder opened in VS Code containing the specified repository
+- `${workspaceFolderBasename}` — the name of the folder opened in VS Code containing the specified repository without any slashes (/)
- Adds owner avatars to remotes in the _Remotes_ view for GitHub remotes
### Changed
@@ -6107,24 +5802,24 @@ Pull requests on status bar
- Changes display of filtered state of files nodes in comparisons
- Improves diff stat parsing performance and reduced memory usage
- Disallows comparisons with the working tree on the right-side (left-side still works as expected) and disables swapping
-- Uses VS Code as `core.editor` in rebase — closes [#2084](https://github.com/gitkraken/vscode-gitlens/issues/2084) thanks to [PR #2085](https://github.com/gitkraken/vscode-gitlens/pull/2085) by Nafiur Rahman Khadem ([@ShafinKhadem](https://github.com/ShafinKhadem))
+- Uses VS Code as `core.editor` in rebase — closes #2084 (https://github.com/gitkraken/vscode-gitlens/issues/2084) thanks to PR #2085 (https://github.com/gitkraken/vscode-gitlens/pull/2085) by Nafiur Rahman Khadem (@ShafinKhadem (https://github.com/ShafinKhadem))
### Fixed
-- Fixes [#2156](https://github.com/gitkraken/vscode-gitlens/issues/2156) - Reduce extension package size
-- Fixes [#2136](https://github.com/gitkraken/vscode-gitlens/issues/2136) - Search & Compare quickpick shouldn't select the mode text when opening
-- Fixes [#1896](https://github.com/gitkraken/vscode-gitlens/issues/1896) - Cannot read property 'fsPath' of undefined
-- Fixes [#1550](https://github.com/gitkraken/vscode-gitlens/issues/1550) - Push button in commit widget does not trigger "Push force" when ALT is pressed.
-- Fixes [#1991](https://github.com/gitkraken/vscode-gitlens/issues/1991) - Git lens status bar entry has an incomprehensible accessibility label
-- Fixes [#2125](https://github.com/gitkraken/vscode-gitlens/issues/2125) - "git log" command in version 12.x is very slow
-- Fixes [#2121](https://github.com/gitkraken/vscode-gitlens/issues/2121) - Typo in GitLens header — thanks to [PR #2122](https://github.com/gitkraken/vscode-gitlens/pull/2122) by Chase Knowlden ([@ChaseKnowlden](https://github.com/ChaseKnowlden))
-- Fixes [#2082](https://github.com/gitkraken/vscode-gitlens/issues/2082) - GitLens Home view unreadable in certain themes
-- Fixes [#2070](https://github.com/gitkraken/vscode-gitlens/issues/2070) - Quoted HTML / JSX syntax is not escaped correctly
-- Fixes [#2069](https://github.com/gitkraken/vscode-gitlens/issues/2069) - Heatmap - incorrect behavior of gitlens.heatmap.fadeLines with gitlens.heatmap.ageThreshold
+- Fixes #2156 (https://github.com/gitkraken/vscode-gitlens/issues/2156) - Reduce extension package size
+- Fixes #2136 (https://github.com/gitkraken/vscode-gitlens/issues/2136) - Search & Compare quickpick shouldn't select the mode text when opening
+- Fixes #1896 (https://github.com/gitkraken/vscode-gitlens/issues/1896) - Cannot read property 'fsPath' of undefined
+- Fixes #1550 (https://github.com/gitkraken/vscode-gitlens/issues/1550) - Push button in commit widget does not trigger "Push force" when ALT is pressed.
+- Fixes #1991 (https://github.com/gitkraken/vscode-gitlens/issues/1991) - Git lens status bar entry has an incomprehensible accessibility label
+- Fixes #2125 (https://github.com/gitkraken/vscode-gitlens/issues/2125) - "git log" command in version 12.x is very slow
+- Fixes #2121 (https://github.com/gitkraken/vscode-gitlens/issues/2121) - Typo in GitLens header — thanks to PR #2122 (https://github.com/gitkraken/vscode-gitlens/pull/2122) by Chase Knowlden (@ChaseKnowlden (https://github.com/ChaseKnowlden))
+- Fixes #2082 (https://github.com/gitkraken/vscode-gitlens/issues/2082) - GitLens Home view unreadable in certain themes
+- Fixes #2070 (https://github.com/gitkraken/vscode-gitlens/issues/2070) - Quoted HTML / JSX syntax is not escaped correctly
+- Fixes #2069 (https://github.com/gitkraken/vscode-gitlens/issues/2069) - Heatmap - incorrect behavior of gitlens.heatmap.fadeLines with gitlens.heatmap.ageThreshold
- Fixes an issue where choosing "Hide Current Branch Pull Request" from the _Commits_ view overflow menu wouldn't hide the PR node
- Fixes an issue where stashes without a message aren't displayed properly
- Fixes an issue where the _Stashes_ view empty state isn't displayed properly when there are no stashes
-- Fixes typos via [PR #2086](https://github.com/gitkraken/vscode-gitlens/pull/2086) by stampyzfanz ([@stampyzfanz](https://github.com/stampyzfanz)), and [PR #2043](https://github.com/gitkraken/vscode-gitlens/pull/2043), [PR #2040](https://github.com/gitkraken/vscode-gitlens/pull/2040), [PR #2042](https://github.com/gitkraken/vscode-gitlens/pull/2042) by jogo- ([@jogo-](https://github.com/jogo-))
+- Fixes typos via PR #2086 (https://github.com/gitkraken/vscode-gitlens/pull/2086) by stampyzfanz (@stampyzfanz (https://github.com/stampyzfanz)), and PR #2043 (https://github.com/gitkraken/vscode-gitlens/pull/2043), PR #2040 (https://github.com/gitkraken/vscode-gitlens/pull/2040), PR #2042 (https://github.com/gitkraken/vscode-gitlens/pull/2042) by jogo- (@jogo- (https://github.com/jogo-))
---
@@ -6132,8 +5827,9 @@ Pull requests on status bar
URL: https://help.gitkraken.com/gitlens/gl-security/
Description: Learn how GitLens secures your data, including collection, transfer, storage, and SOC 2 certification.
+Last updated: March 2026
-Last updated: August 2025
+This page explains GitLens data collection, storage, transport security, and SOC 2 status for users evaluating GitLens security and compliance. Use it when you need to confirm what GitLens stores, where service data lives, and which protections apply to subscription, account, and AI-related data.
## Data Collection and Storage
@@ -6151,7 +5847,7 @@ The table below outlines the types of data GitLens collects, how it is secured d
## SOC 2 Compliance
GitKraken and its tools, including GitLens, are **SOC 2 certified**.
-If you would like to request a copy of our SOC 2 report, please visit our [Trust Center](https://trust.gitkraken.com/) to begin the request process.
+If you would like to request a copy of our SOC 2 report, please visit our Trust Center (https://trust.gitkraken.com/) to begin the request process.
Please note: an MNDA must be signed before we can provide a copy of the report.
@@ -6163,21 +5859,24 @@ Note: SOC 2 reports are only available for Business and Enterprise customers.
URL: https://help.gitkraken.com/gitlens/gitlens-settings/
Description: Learn how to access and customize GitLens settings in Visual Studio Code
+Last updated: March 2026
-Last updated: July 2025
+| Settings area | What it controls | Best for |
+|---|---|---|
+| Current Line Blame | Inline blame annotations on the active line | Understanding recent line history |
+| Git CodeLens | Commit and authorship details above code | Navigating file and symbol history |
+| Hovers | Hover cards for commits, lines, and revisions | Inspecting details without leaving the editor |
+| Views | Sidebar panels and history surfaces | Tailoring GitLens navigation to your workflow |
## Overview
-
-GitLens interactive settings editor in VS Code
-
GitLens offers a powerful and easy-to-use **interactive settings editor** that helps you configure many features directly in Visual Studio Code.
-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).
+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).
GitLens is highly customizable—nearly every feature can be tailored to fit your workflow using the available settings.
-## Current Line Blame Settings
+## How to Configure Current Line Blame
Use these settings to customize how GitLens displays blame annotations for the current line of code. These annotations help identify the last commit that modified a line, along with contextual details like date, author, and related pull requests.
@@ -6185,13 +5884,13 @@ Name
Description
gitlens.currentLine.dateFormat
-Defines how absolute dates appear in current line blame annotations using the ${date} token. Refer to the Moment.js format guide.
+Defines how absolute dates appear in current line blame annotations using the ${date} token. Refer to the Moment.js format guide (https://momentjs.com/docs/#/displaying/format/).
gitlens.currentLine.enabled
Enables or disables current line blame annotations by default. Toggle annotations in any window with the Toggle Line Blame Annotations command (gitlens.toggleLineBlame).
gitlens.currentLine.format
-Sets the display format for the annotation. See Commit Tokens for supported placeholders. Date format is managed by gitlens.currentLine.dateFormat.
+Sets the display format for the annotation. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) for supported placeholders. Date format is managed by gitlens.currentLine.dateFormat.
gitlens.currentLine.pullRequests.enabled
Shows pull request info (if available) for the commit in the current line annotation. Requires a connected remote provider like GitHub.
@@ -6216,7 +5915,7 @@ Sets the font weight for inline blame annotations.
***
-## Git CodeLens Settings
+## How to Customize Git CodeLens
These settings control GitLens CodeLens overlays, which provide inline contextual information such as author and commit history directly in your code.
@@ -6249,7 +5948,7 @@ containers – start of container symbols (e.g., classes, interfaces)
blocks – start of block symbols (e.g., functions, methods)
gitlens.codeLens.symbolScopes
-Defines specific symbol types to include or exclude from CodeLens. Prefix a symbol with ! to exclude it. Uses SymbolKind values.
+Defines specific symbol types to include or exclude from CodeLens. Prefix a symbol with ! to exclude it. Uses SymbolKind (https://code.visualstudio.com/docs/extensionAPI/vscode-api#_a-namesymbolkindaspan-classcodeitem-id660symbolkindspan) values.
***
@@ -6268,13 +5967,13 @@ Specifies the command executed when clicking the blame status bar item. Default
gitlens.toggleFileBlame, gitlens.toggleFileHeatmap, gitlens.toggleFileChanges, gitlens.toggleFileChangesOnly, gitlens.diffWithPrevious, gitlens.revealCommitInView, gitlens.showCommitsInView, gitlens.showQuickCommitDetails, gitlens.showQuickCommitFileDetails, gitlens.showQuickFileHistory, gitlens.showQuickRepoHistory, gitlens.openCommitOnRemote, gitlens.copyRemoteCommitUrl, gitlens.openFileOnRemote, gitlens.copyRemoteFileUrl
gitlens.statusBar.dateFormat
-Sets the date format using the ${date} token. For valid formats, see the Moment.js documentation.
+Sets the date format using the ${date} token. For valid formats, see the Moment.js documentation (https://momentjs.com/docs/#/displaying/format/).
gitlens.statusBar.enabled
Enables or disables blame information in the status bar.
gitlens.statusBar.format
-Defines the display format of blame data in the status bar. Refer to Commit Tokens. Controlled alongside gitlens.statusBar.dateFormat.
+Defines the display format of blame data in the status bar. Refer to Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens). Controlled alongside gitlens.statusBar.dateFormat.
gitlens.statusBar.pullRequests.enabled
Shows pull request details for the commit in the status bar, if available. Requires a connected remote (e.g., GitHub).
@@ -6283,11 +5982,11 @@ gitlens.statusBar.reduceFlicker
Reduces visual flicker by preventing blame info from clearing when switching lines.
gitlens.statusBar.tooltipFormat
-Specifies the markdown format used in the hover tooltip over blame info. See Commit Tokens.
+Specifies the markdown format used in the hover tooltip over blame info. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens).
***
-## Hover Settings
+## How to Customize GitLens Hovers
Use these settings to control when and how GitLens displays hover popups that show commit details, line changes, avatars, and pull request information.
@@ -6328,7 +6027,7 @@ gitlens.hovers.currentLine.over
Controls when hovers appear on the current line:annotation – hover only on the annotationline – hover anywhere on the line
gitlens.hovers.detailsMarkdownFormat
-Defines the markdown format used for commit details hovers. See Commit Tokens.
+Defines the markdown format used for commit details hovers. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens).
gitlens.hovers.enabled
Enables or disables all GitLens hovers.
@@ -6353,22 +6052,22 @@ gitlens.views.defaultItemLimit
Specifies the default number of items to show in a view list. Use 0 for no limit.
gitlens.views.formats.commits.label
-Specifies the format of commits in the views. See Commit Tokens in the GitLens docs.
+Specifies the format of commits in the views. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs.
gitlens.views.formats.commits.description
-Specifies the description format of commits in the views. See Commit Tokens in the GitLens docs.
+Specifies the description format of commits in the views. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs.
gitlens.views.formats.files.label
-Specifies the format of a file in the views. See File Tokens in the GitLens docs.
+Specifies the format of a file in the views. See File Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs.
gitlens.views.formats.files.description
-Specifies the description format of a file in the views. See File Tokens in the GitLens docs.
+Specifies the description format of a file in the views. See File Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs.
gitlens.views.formats.stashes.label
-Specifies the format of stashes in the views. See Commit Tokens in the GitLens docs.
+Specifies the format of stashes in the views. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs.
gitlens.views.formats.stashes.description
-Specifies the description format of stashes in the views. See Commit Tokens in the GitLens docs.
+Specifies the description format of stashes in the views. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs.
gitlens.views.formats.stashes.tooltip
Specifies the tooltip format of stashes in GitLens views.
@@ -6422,7 +6121,7 @@ Specifies which views to show in the grouped GitLens view.
## Commits View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings control how the GitLens Commits view displays commit data, associated files, and pull request information.
@@ -6466,7 +6165,7 @@ working – compares working tree to a selected reference
## Repositories View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings customize how repositories are displayed and interacted with in the GitLens Repositories view.
@@ -6539,7 +6238,7 @@ Displays upstream tracking status of the current branch for each repository.
## File History View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings configure the behavior and display options for the GitLens File History view.
@@ -6556,7 +6255,7 @@ Controls whether merge commits are shown in file history:show – includes merge
## Line History View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings configure the display behavior of the GitLens Line History view.
@@ -6570,7 +6269,7 @@ Displays avatar images instead of status icons in the Line History view.
## Branch View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings configure the display and behavior of the GitLens Branches view.
@@ -6618,7 +6317,7 @@ branch – compares the current branch with a selected reference
## Remotes View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings define how branches, files, and pull requests appear in the GitLens Remotes view.
@@ -6666,7 +6365,7 @@ branch – compares the current branch with a selected reference
## Stashes View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings control how files and stash entries are displayed in the GitLens Stashes view.
@@ -6692,7 +6391,7 @@ Determines whether stashes appear in the Stashes view or the Repositories view.
## Tags View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings control how Git tags and related files appear in the GitLens Tags view.
@@ -6726,7 +6425,7 @@ Determines whether tags are shown in the Tags view or revealed in the Repositori
## Worktrees View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings control how worktrees and related information appear in the GitLens Worktrees view.
@@ -6769,7 +6468,7 @@ branch – compares with a selected reference (e.g., tag or branch)
## Contributors View Settings
-See also [View Settings](/gitlens/settings/#view-settings)
+See also View Settings (/gitlens/settings/#view-settings)
Name
Description
@@ -6802,7 +6501,7 @@ Specifies whether to show contributor statistics in the Contributors view. This
## Search & Compare View Settings
-See also [View Settings](/gitlens/settings/#view-settings).
+See also View Settings (/gitlens/settings/#view-settings).
These settings control the display options for files and avatars in the GitLens Search Commits and Compare views.
@@ -6850,10 +6549,10 @@ gitlens.blame.compact
Compacts (deduplicates) adjacent matching blame annotations.
gitlens.blame.dateFormat
-Formats absolute dates (e.g., using ${date}) in blame annotations. See the Moment.js documentation for valid formats.
+Formats absolute dates (e.g., using ${date}) in blame annotations. See the Moment.js documentation (https://momentjs.com/docs/#/displaying/format/) for valid formats.
gitlens.blame.format
-Specifies the display format of blame annotations. See Commit Tokens. Date format is controlled by gitlens.blame.dateFormat.
+Specifies the display format of blame annotations. See Commit Tokens (https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens). Date format is controlled by gitlens.blame.dateFormat.
gitlens.blame.heatmap.enabled
Enables a heatmap indicator in blame annotations.
@@ -7032,13 +6731,13 @@ Name
Description
gitlens.defaultDateFormat
-Specifies the default format for absolute dates. See the Moment.js documentation for valid format strings.
+Specifies the default format for absolute dates. See the Moment.js documentation (https://momentjs.com/docs/#/displaying/format/) for valid format strings.
gitlens.defaultDateLocale
-Specifies the locale for date formatting, using a BCP 47 language tag. Defaults to the VS Code locale. Use system to follow the current system locale or specify a locale like en-US (US English), en-GB (British English), de-DE (German), ja-JP (Japanese), etc.
+Specifies the locale for date formatting, using a BCP 47 language tag (https://en.wikipedia.org/wiki/IETF_language_tag#List_of_major_primary_language_subtags). Defaults to the VS Code locale. Use system to follow the current system locale or specify a locale like en-US (US English), en-GB (British English), de-DE (German), ja-JP (Japanese), etc.
gitlens.defaultDateShortFormat
-Specifies the default format for short absolute dates. See the Moment.js documentation for valid format strings.
+Specifies the default format for short absolute dates. See the Moment.js documentation (https://momentjs.com/docs/#/displaying/format/) for valid format strings.
gitlens.defaultDateSource
Determines whether commit dates use the authored date or the committed date.
@@ -7047,7 +6746,7 @@ gitlens.defaultDateStyle
Specifies the default display style for dates.
gitlens.defaultTimeFormat
-Specifies the default format for times. See the Moment.js documentation for valid format strings.
+Specifies the default format for times. See the Moment.js documentation (https://momentjs.com/docs/#/displaying/format/) for valid format strings.
***
@@ -7123,9 +6822,9 @@ Name
Description
gitlens.autolinks
-Defines autolinks to external resources in commit messages. Use <num> as a placeholder for the reference number.Example for Jira issues:
+Defines autolinks to external resources in commit messages. Use