+
+You can manage Cloud Patches from the **Cloud Patches view** in the GitLens sidebar.
-A Cloud Patch can be created from Working Changes, Commits, Stashes or Comparisons by using the "Share as Cloud Patch" option from the command palette or from the Share submenu in applicable gitlens views.
+
+ 
+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
-When creating a Cloud Patch, you have the following sharing options:
+
+ 
+ Note: If you have multiple organizations, you can easily switch between them from the GitKraken Account view.
-
+
+
+
+
+If you do not want Cloud Patch data stored on GitKraken servers, you can host Cloud Patches on your own **AWS S3 storage instance**.
-### Self-Hosting Cloud Patch data
+For configuration instructions, see [Self-Hosted Documentation](/gk-dev/gk-dev-home/#self-hosted).
-If you do not want your Cloud Patch data stored on GitKraken Servers, we offer the ability for you to host Cloud Patches on your own AWS S3 storage instance. For more information on configuring this, see our documentation [here](/gk-dev/gk-dev-home/#self-hosted).
+Note: If you belong to multiple organizations, you can switch between them from the GitKraken Account view.
+Note: Code Suggest is currently only available for repositories on github.com.
-
+Reviewers can then view, accept, and apply these suggestions directly to the pull request branch.
-To begin suggesting changes, open the [GitLens Inspect Overview](/gitlens/side-bar/#overview) for the desired repository and checkout a branch that has an open pull request. From here, you will have the option to _Start Review for PR #PR_. You may begin modifying and saving any file you would like to include in the code suggestion. Once you are ready, select _Suggest Changes for PR_, provide a title, and then finish with _Create Code Suggestion_.
+
+ 
+---
-This will include a comment on the pull request with two options: you can select _Code Suggestion for #PR_ to open the suggestion in gitkraken.dev or select _locally on your machine_ to open the suggestion in GitKraken or GitLens.
+## 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.
+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**.
-When selecting _locally on your machine_ you can open them on GitLens or [GitKraken Desktop](/gitkraken-client/pull-requests/#review-code-and-suggest-changes). Here, you can review the changes by selecting each file and once you are ready, you can select _Apply_ to apply to the branch you currently have checked out or select the dropdown and then _Apply to a Branch_ to apply to a new branch or select an existing branch. This will apply the patch locally.
+
+ 
+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**
-When selecting the _Code Suggestion for #PR_ you will be taken to gitkraken.dev to review and accept the changes. Here, you can review the changes by selecting each file and once you are ready, you can select _Commit Suggestions_. This will create a new commit on the remote for the existing branch (shown under _COMMIT SUGGESTIONS 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).
+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.
+
+
+
+ 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.
-To open the Commit Graph, open the command palette using the keyboard shortcut `Cmd/ctrl + Shift + P` and type “Show Commit Graph”. This will open a new tab and render your current repo’s commit history, where you may scroll through your history and resize any of the columns widths.
+
+ 
+---
-At the top of the commit graph the repository name, the branch name that is currently checked out, and the last fetched time is shown. This section offers the ability to switch branches by selecting the branch name and the ability to fetch by selecting "Fetch".
+### Open the Commit Graph
-
+1. Open the Command Palette:
+ - macOS: Cmd + Shift + P
+ - Windows/Linux: Ctrl + Shift + P
+2. Type **Show Commit Graph** and select it.
-Note: The Commit Graph is available to all users working on public or local repositories, and requires no account. Additionally, users with a paid GitLens subscription or trial can use the Commit Graph with private repos.
+The Commit Graph opens in a new tab, where you can scroll through history and resize column widths.
+
+
+
+
+
+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**.
-A Commit Graph Panel Layout is offered to show the Commit Graph in the bottom Panel (near the Terminal) with a dedicated Commit Graph Details view alongside the Commit Graph. To switch between the Editor Layout and Panel Layout, select the Commit Graph settings gear located at the top right of the editor. From there, select the "Prefer Commit Graph in Panel Layout" or "Prefer Commit Graph in Editor Area". The Commit Graph can also be opened in both the Penel Layout and Editor Area simultaneously.
+
+
+#### 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.
-A compact layout for the Graph column is offered in the Commit Graph to reduce the visual complexity and size of the Graph column. To enable the compact layout, right click on the Graph column header, and select the Compact Graph Column Layout option. Additionally the Author column displays avatars instead of text when sized to its minimum width, which pairs nicely with the compact Graph column as you can retain avatars. Also, when the any of the Commit Graph columns are resized small enough so that their text would be truncated, they switch to displaying icons to ensure that crucial information remains visible, even in constrained display settings.
+
+
+#### Scroll Markers
+Scroll markers highlight key points in the Commit Graph, including:
+- Checked-out branches
+- Selected rows
+- Search results
-The scroll markers indicate points of interest on the commit graph such as checked-out branches, selected rows, and search results. This provides the ability to jump to important points like the HEAD or refs. This can be toggled on or off in the [Commit Graph settings](/gitlens/gitlens-features/#settings).
+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).
-
+
+ 
+Search for **GitLens: Open Settings**.
+
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+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).
-### Hiding Remotes, Branches or Tags
+
+ 
+### Hiding Remotes, Branches, or Tags
-Filter options can be accessed from the filter dropdown. This provides the ability to switch between _Show Current Branch Only_ - to show the current branch and its upstream remote - or _Show All Local Branches_ - this is selected by default. Additionally, remote-only branches, stashes and tags can be hidden/shown and merge commit rows can be dimmed.
+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.
-
+
+ 
+You can also dim merge commit rows for clarity.
-The Minimap can be toggled between showing commits or lines changed by selecting the graph icon dropdown in the top right of the Activity Minimap. Additionally, markers can be toggled on or off from here.
+
+ 
+---
-Minimap Overview:
+### Minimap (Experimental)
-- Reads left to right - left is the most recent and the right is older
-- Highlighted region: Commit Graph area that is in view
-- Green Lines: HEAD
-- Yellow lines: Search results
-- Upper row markers:
- - Blue blocks: remote branches
- - Brown blocks: Tags
-- Lower row markers:
- - Pink blocks: stashes
- - Blue blocks: local branches
+The Minimap provides a high-level overview of repository activity. It shows commits, branches, HEAD/upstream, and more, letting you quickly jump to points of interest.
+
+- Select the **Toggle Minimap** icon in the Commit Graph toolbar to enable or disable it.
+- Use the graph icon dropdown to switch between **Commits** or **Lines Changed** views.
+- Toggle markers on or off from the same menu.
+
+
+
+ Note: We would love to hear your feedback regarding the Minimap. Please share it on the GitHub Discussion board.
-Note: We’d love your feedback on the Minimap. Please share it on the GitHub Discussion board.
+ \ No newline at end of file diff --git a/gitlens/GL-Launchpad.md b/gitlens/GL-Launchpad.md index 67689c9..6c8d7ce 100644 --- a/gitlens/GL-Launchpad.md +++ b/gitlens/GL-Launchpad.md @@ -1,41 +1,88 @@ --- - title: Launchpad -description: Gitlens Launchpad +description: Use GitLens Launchpad to organize and prioritize pull requests in VS Code. taxonomy: category: gitlens --- -The Launchpad organizes pull requests by status allowing you to identify bottlenecks and take actions on them. This offers the ability to organize and quickly take actions on pull requests with priority. +Last updated: August 2025 + +## LaunchpadPRO
-
+The GitLens Launchpad helps you manage pull requests by status, so you can quickly identify bottlenecks, prioritize work, and take action.
-Currently, this view is supported for GitHub.com and GitLab.com repositories. In order to see the Launchpad, you will need to connect the GitHub Integration .
-
+ 
+### Open the Launchpad
-Here you can see a list of all pull requests for your repositories that are ready to merge, blocked, require follow-up, need your review, are waiting for a review, are a draft, or are snoozed. You can select the pull request to see more information about it and take action on it such as open it in a browser, merge (if ready to merge) or switch to the branch/worktree.
+1. Open the Command Palette:
+ - macOS: Cmd + Shift + P
+ - Windows/Linux: Ctrl + Shift + P
+2. Search for **GitLens: Open Launchpad**, or select **Pull Request** from the status bar in VS Code.
-
+
+ 
+The Launchpad displays pull requests for your repositories, grouped by status:
+- Ready to merge
+- Blocked
+- Requires follow-up
+- Needs your review
+- Waiting for review
+- Draft
+- Snoozed
+
+Select a pull request to:
+- View detailed information
+- Open it in a browser
+- Merge it (if ready)
+- Switch to the branch or worktree
+
+
+ 
+You can start or review [Code Suggestions](/gitlens/gitlens-features/#code-suggest-preview) directly from pull requests in the Launchpad.
+
+
+
+ Note: The Launchpad is currently organized by prioritizing items on the list that require more action by elevating them to the top. This is subject to change in the future.
-This Feature is only available for Pro subscription tiers or higher
-Note: SOC 2 reports are only available for Business and Enterprise customers.
+
+
+### Claude Sonnet 4.5 AI Model Support
+
+GitLens now supports Anthropic's Claude Sonnet 4.5 model for all AI-powered features, including:
+
+- Commit and message generation in the _Commit Composer_
+- Code explanations and summaries
+- Pull request descriptions
+- Changelog generation
+
+This latest model brings improved reasoning capabilities and more accurate, context-aware suggestions to your development workflow.
+
+### Large Changeset Performance Improvements
+
+Working with large changesets and complex commit histories is now significantly faster and more responsive across multiple GitLens views.
+
+#### Inspect and Graph Details Views
+
+The _Inspect_ and _Graph Details_ views now feature dramatically improved performance through virtualized tree rendering. This enhancement makes working with repositories with large commits significantly faster and more responsive.
+
+Along with the performance boost, keyboard navigation has been enhanced with comprehensive support for:
+
+- **Arrow keys** for navigating through items
+- **Home/End** keys for jumping to the first or last item
+- **Enter/Space** for selecting and activating items
+- **Tab** for moving between sections
+- **Type-ahead search** for quickly finding specific items
+
+These improvements make it easier to navigate and explore your repository's history, especially when working with a large number of files or reviewing detailed commit information.
+
+#### Commit Composer `PREVIEW`
+
+The _Commit Composer_ now handles large file diffs more efficiently, preventing performance degradation when working with substantial changes. This ensures a smooth composition experience regardless of the size of your working changes.
+
+### Linear Integration Enhancements `PRO`
+
+Introduced in GitLens 17.5, Linear issue trackering continues to evolve with autolinks for branches in Home and the Commit Graph. Along with some reliability and functionality improvements, these enhancements provide a more seamless experience when working with Linear issues in your GitLens workflows.
+
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- Noritaka Kobayashi ([@noritaka1166](https://github.com/noritaka1166))
+
+---
+
+### Added
+
+- Adds support for Claude Sonnet 4.5 for GitLens' AI features
+
+### 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))
+ - 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))
+
+### 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 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))
+
+
+
+
+## Version 17.5
+
+#### Tuesday, September 23, 2025
+
+GitLens 17.5 introduces the GitKraken MCP for Git and integration enhanced AI chat workflows, expands integration support with Linear, and launches a new Student Plan for GitHub Student Developer Pack members.
+
+
+
+### GitKraken MCP: Git Intelligence for AI Chat
+
+GitLens 17.5 bundles the GitKraken Model Context Protocol (MCP) server, bringing Git and repository intelligence directly to AI chat interfaces in VS Code, Cursor, Windsurf, and other compatible IDEs.
+
+The GitKraken MCP transforms how you interact with Git through AI by surfacing repository information, issue tracking data, and pull request details—the same rich context that GitLens has provided in UI form for years—now accessible through conversational AI.
+
+
+
+
+
+#### Enhanced Developer Workflows
+
+The MCP enables powerful use cases through AI chat:
+
+**Issue and Branch Management**
+- List issues: *"List all open Jira issues assigned to me"*
+ - GitKraken MCP fetches and displays issue details from your connected trackers
+- Start work on an issue: *"Start work on Jira issue PROJ-123"*
+ - GitKraken MCP pulls issue details, stashes changes if needed, and creates a feature branch
+
+**Pull Request Assistance**
+- Create a pull request: *"Create a pull request for my current branch"*
+ - GitKraken MCP gathers branch diffs, generates a PR title and description, and opens the PR in your connected Git provider
+
+**Debug and Understand History**
+- 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/).
+
+#### 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/).
+
+We're just scratching the surface of what's possible with the GitKraken MCP. Future releases will expand capabilities, integrations, and IDE support.
+
+### Linear Integration `PRO`
+
+Teams using Linear for issue tracking can now connect to Linear and bring issue information directly into GitLens workflows.
+
+- **Start work seamlessly**: Create branches or worktrees directly from Linear issues
+- **Rich contextual information**: View Linear issue details in the Commit Graph, Home View, blame annotations, and Commit Details
+
+This integration follows the same pattern as GitLens' other issue tracker connections, providing a unified experience whether you're using GitHub Issues, Jira, or Linear.
+
+### Student Plan
+
+GitKraken now offers a Student Plan for members of the GitHub Student Developer Pack! This plan provides students with:
+
+- **Private repository access**: Use paid GitLens features like the Commit Graph and Visual File History on private repos
+- **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).
+
+---
+
+### Added
+
+- 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)
+
+### Changed
+
+- Improves AI provider/model fallback handling for better reliability
+
+### Fixed
+
+- Fixes connection flow when multiple integrations need to be connected
+
+
+
+## Version 17.4
+
+#### Thursday, August 21, 2025
+
+GitLens 17.4 transforms the Commit Composer experience with a powerful new composing view, introduces Azure DevOps Server integration for Pro users, enhances AI explanations, adds support for new AI models like GPT-5, and delivers significant improvements to worktree workflows.
+
+
+
+### New Commit Composer View `PREVIEW`
+
+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.
+
+
+
+#### Interactive Draft Commits
+
+When composing commits, GitLens now creates "draft" commits that you can review, modify, and refine before applying them to your repository. This new workflow lets you:
+
+- **Preview before committing**: See exactly what will be committed before it touches your repository
+- **Switch Models**: Try composition with different AI models
+- **Guide the AI**: Provide custom instructions to match your team's conventions and preferences
+- **Iterate and refine**: Regenerate individual messages or entire commit compositions
+- **Review and edit**: Manually tweak any commit message or approach
+
+
+
+You can launch the new Commit Composer view from several places in GitLens:
+
+- **GitLens commit details view**
+- **Context menu on the WIP row** in the GitLens Commit Graph
+- **Active branch card** in the GitLens Home View
+- **✨ icon in the SCM view header**
+- **Command palette**: Search for "Compose Commits"
+
+
+
+
+The foundation is now in place for even more powerful composition features in future releases, including intuitive drag-and-drop functionality for moving lines and hunks between commits, creating new draft commits on the fly, and reordering commit sequences.
+
+Whether you prefer to let AI handle the heavy lifting or want granular control over every detail, Commit Composer provides the flexibility to create well-structured commit histories that make code reviews more effective and repository history easier to understand.
+
+### Azure DevOps Server Integration `PRO`
+
+GitLens Pro now supports self-hosted Azure DevOps Server instances, bringing the same rich integration experience you know from cloud-hosted services to your on-premises environments.
+
+Connect your Azure DevOps Server to unlock:
+
+- **Streamlined issue workflows** - Start work on Azure issues by creating branches or worktrees directly from GitLens
+- **Rich blame and hover information** - View Azure issue and pull request details inline with your code
+- **Launchpad integration** - Monitor pull request blockers and review status from a unified view
+- **Native pull request creation** - Create Azure pull requests without leaving your IDE
+
+### New AI Model Support
+This release adds support for GPT-5 family (GPT-5, GPT-5 Mini, GPT-5 Nano), and Claude 4.1 Opus models
+
+### AI Explanation Improvements
+
+AI-powered explanations now provide immediate feedback with enhanced user experience improvements:
+
+- **Instant summary views** open immediately when generating explanations
+- **Clear progress indicators** show pending AI analysis status
+- **Streamlined presentation** focuses your attention on the generated content
+
+
+
+### Branch Upstream Management
+You can now easily modify the upstream for local branches in GitLens from places like the Branches view and Commit Graph.
+
+### 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:
+
+- **Repository filtering** - New header controls let you focus on specific repositories or worktrees
+- **Visual differentiation** - Improved icons help distinguish between repositories and worktrees
+- **Reduced interface noise** - Minimized flashing and blanking during worktree discovery
+- **Unified repository picker** - Visual grouping makes selecting repositories and worktrees more intuitive
+
+These enhancements work seamlessly with VS Code's native worktree support, providing a polished experience whether you're working with single repositories or complex multi-worktree setups.
+
+---
+
+### 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)
+ - 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
+ - Adds custom instruction support to guide AI output to match team conventions and preferences
+ - Adds integrated diff review for each proposed commit, and manual editing capabilities for any commit message or approach
+ - Adds manual commit composition support (no AI provider required for basic functionality)
+ - 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))
+ - 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 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))
+
+### 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))
+- 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))
+
+### 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))
+
+
+
+## Version 17.3
+
+#### Tuesday, July 8, 2025
+
+GitLens 17.3 transforms how you search and interact with your repository history. This release introduces natural language search for both the Commit Graph and Commit Search commands, enhanced time-based filtering, improved AI-powered commit generation and the ability to provide feedback on AI results.
+
+
+
+### Natural Language Search for Commits `PRO`
+Say goodbye to complex query syntax! GitLens 17.3 introduces natural language search for the Commit Graph and command palette, allowing you to find exactly what you're looking for using natural language.
+
+
+
+Instead of memorizing query tags like `@me`, `message:`, `author:`, or `file:`, simply describe what you're looking for:
+
+"Show all commits made by Eric this week"
+
+"Find commits that modified package.json last week"
+
+"Show all commits that changed files with "auth" in the name in the last 12 days"
+
+GitLens leverages AI to automatically translate your natural language queries into the appropriate search syntax, making repository exploration more intuitive than ever. You can still reveal the generated query to learn the underlying syntax and refine your searches.
+
+### Time-Based Search Filters
+GitLens 17.3 adds powerful new `after:` and `before:` filters that make temporal filtering more intuitive and flexible.
+These new filters work seamlessly with both traditional query syntax and the new natural language search:
+
+- `after:2025-01-01` - commits made after January 1st, 2025
+- `before:2024-12-25` - commits made before December 25th, 2024
+- `after:6.months.ago` - commits made after 6 months ago
+- `before:2.weeks.ago` - commits made before 2 weeks ago
+
+The filters accept specific date strings (YYYY-MM-DD format) or relative date expressions, and integrate automatically when using natural language queries, making it easier than ever to focus on specific timeframes in your repository history.
+
+### Enhanced Commit Composer Access `PREVIEW`
+Building on the Commit Composer preview introduced in 17.2, we've made AI-powered commit generation more accessible by adding it directly to the Commit Details panel with an option to `Commit with AI (Preview)`.
+
+
+
+You can now generate multiple commits at once from your working directory changes with a single click, streamlining the process of creating meaningful, well-structured commits with AI assistance.
+
+📝 _While in Preview, Commit Composer will create a stash of your changes as a backup when generating commits should you need to revert them. You can also undo the generated commits with a single click from the success notification._
+
+### AI Feature Feedback
+GitLens can now collect feedback about AI-powered features. When using AI capabilities like explaining commits, branches, and stashes, or generating commits with Commit Composer, you'll notice new 👍 and 👎 icons in the toolbar of generated summaries that will tell us if the result was helpful or not.
+
+This feedback helps us understand how well our AI results meet your needs and allows us to refine our prompts and models to deliver better, more relevant outputs. Your input is invaluable as we continue to enhance the accuracy and usefulness of GitLens AI features.
+
+---
+
+### 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 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 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))
+
+### 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 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
+
+#### Tuesday, June 17, 2025
+
+GitLens 17.2 transforms how you craft your Git history with the early preview of Commit Composer, a set of AI-powered features that automatically organize your changes into meaningful, well-structured commits. This release also refines the Home View UX to streamline workflows, introduces advanced AI security controls for organizations, and delivers a cleaner AI explanation experience—all designed to help you tell better stories with your code.
+
+
+
+### Commit Composer Early `Preview`
+In this release, we're excited to share an early preview of **Commit Composer**, a set of AI-powered features that help you organize your Git commits into clear, logical stories.
+
+Commit Composer will analyze your code changes and use AI to:
+- **Organize related changes** across files into logical, cohesive commits
+- **Generate meaningful commit messages** that clearly describe what each commit accomplishes
+- **Create commit descriptions** that provide helpful context for reviewers
+
+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).
+
+
+
+### 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.
+
+
+
+#### Streamlined Issue Association
+When no issue is associated with your current branch, we've removed the large "Associate an Issue" button to reduce visual clutter. You can still associate issues using the subtle issue icon in the header.
+When an issue is identified, it now appears above the current branch to reinforce the natural workflow progression from issue → branch → pull request.
+
+#### Enhanced Repository Navigation
+The main header is now a breadcrumb that helps you understand your current repo context. The repository name is collapsed by default with the branch prominently displayed, so you always know which branch you're working on. Hover over the breadcrumb to reveal the full repository name when needed.
+
+#### Simplified Pull Request Creation
+We've consolidated the "Create Pull Request" and "Create with AI" buttons into a streamlined split button. Click the main button for standard PR creation, or click the smaller ✨ button to generate AI-powered titles and descriptions.
+
+### Advanced AI Security Controls for Organizations `ADVANCED`
+Organizations on the Advanced plan now have granular control over AI provider access for their teams. Admins can:
+
+- Disable specific AI providers to block access to certain models
+- Set custom API keys for specific providers that all organization members will use
+- Configure custom URLs and keys for additional AI providers
+
+These controls ensure compliance with organizational security policies while maintaining access to AI-powered features.
+
+### Refined AI Explanations
+AI explanations now open in a single rendered markdown file instead of showing both the rendered content and markdown source. This reduces editor tab clutter and provides a cleaner reading experience that can be easily closed without save prompts.
+
+---
+
+### 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 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 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
+- Adds inline buttons to the stash and commit picker and ensures proper messaging when there are no stashes or commits available
+- Adds the _Open Worktree in New Window_ command to branch cards in _Home_ view
+
+### 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))
+- 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
+- Automatically expands the remote in _Remotes_ view when it is the only remote
+
+### 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))
+
+
+
+## Version 17.1
+
+#### Thursday, May 15, 2025
+
+GitLens 17.1 brings significant enhancements to AI-powered explanations, more AI provider options, introduces major Visual History improvements, and includes performance optimizations to Git operations and the Commit Graph.
+
+
+
+### Enhanced AI Explanations
+
+We've greatly expanded AI explanation capabilities beyond just commit explanations, making it easier understand more aspects of your repository, from more places in GitLens.
+
+
+
+**✨Explain** functionality now includes generating summaries of changes for **branches**, **working changes**, and **stashes** in Preview. All summaries will open in rendered markdown instead of the Commit Details panel for better visibility and persistence.
+
+You'll find ✨Explain options for commits, branches, stashes, and working changes in several places:
+ - In the Commit Graph
+ - Available as commands in the command palette
+ - In many GitLens views: Commits, Branches, Stashes, Search & Compare, etc.
+ - In branch cards in the Home view
+
+With these new AI explanation capabilities, you can quickly understand:
+- What changed across all commits in a branch - ✨Explain Branch (Preview)
+- What you've modified in your working directory - ✨Explain Working Changes (Preview)
+- What you've previously stashed - ✨Explain Stash (Preview)
+
+### AI Provider Support
+
+We've also expanded AI provider support to give you more options when using GitLens AI features, including:
+- New OpenAI and Google models
+- Self-hosted Azure AI models
+- OpenAI-compatible API providers
+- Local Ollama models
+- OpenRouter support
+
+### Home Workflow Improvements
+
+The Home view now provides more accurate context about your work and offers more flexibility in how you manage branches and their relationships.
+
+- **Improved issue association** for more accurate tracking of issues related to branches
+- **Manual merge target selection** allows you to change the merge target for your active branch when the assumed target isn't correct
+
+
+
+### Graph Enhancements
+
+We've made several improvements to the Commit Graph for better performance and usability.
+
+- **Performance optimization** with behind-the-scenes changes for faster graph rendering
+- **Enhanced Commit Details** with:
+ - Autolinks moved directly into the commit message component for easier access
+ - ✨Explain Commit positioned closer to the commit message
+ - Streamlined panel layout providing more space for the file tree
+
+
+
+### GitLens Visual History: A Reimagined History Experience
+
+We're excited to introduce the all-new Visual History feature in GitLens, a powerful evolution of Visual File History. This reimagined view provides a dynamic and insightful visualization of your repository's history, offering unparalleled flexibility to explore changes across files, folders, branches, and your entire project.
+
+Visual History empowers you to understand the evolution of your codebase in a whole new way, helping you answer critical questions about who changed what, when, and in which context.
+
+
+
+- **New navigation breadcrumb** allowing you to start at file level and move up to folder and repo levels
+- **Interactive diff scrubber** for more precise navigation of diff history
+- **Performance improvements** when loading visualizations and zooming
+- **Repository visualization** accessible directly from the Home view
+
+### Smarter, Faster Git
+This release brings major improvements to how GitLens interacts with Git under the hood — delivering faster performance, better accuracy, and more responsiveness, especially in large repositories.
+
+- **Rewritten Git execution and parsing engine** for dramatically faster and more reliable Git operations.
+- **Smarter contributor stats** with improved fetching performance and richer data.
+- **Faster and more accurate commit searches** across the Commit Graph and Search & Compare views.
+- **Streamlined file and line history** with more precise results and snappier performance.
+- **Improved Git cancellation handling** for smoother UX and lower system impact.
+- **New performance settings**, like delaying file detail loading on commits, give you more control in large repos.
+
+These enhancements ensure GitLens continues to scale with your codebase — helping you move faster with more confidence.
+
+---
+
+### Added
+
+- Adds AI-powered "Explain" commands for work-in-progress (WIP) changes, commits, stashes, and branches
+ - Adds _Explain Branch Changes (Preview)_, _Explain Changes (Preview)_, and _Explain Working Changes (Preview)_ actions to branches, commits and stashes, and WIP, respectively in the _Commit Graph_
+ - Adds _Explain Branch Changes (Preview)_ and _Explain Changes (Preview)_ actions to branches, commits and stashes in the other GitLens views
+ - Adds an _✨ Explain_ button to the editor and status bar blame hovers
+ - Adds an _✨ Explain_ button above the commit message in the _Inspect_ view which replaces the _Explain_ panel
+ - 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 support for Azure AI (OpenAI-compatible) models
+ - 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
+ - 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
+ - Adds the configuration popover to customize the visualization, including the branch or all branches, timeframe, and how to slice the history
+ - 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 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 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
+- Adds `Copy SHA` action to editor hovers
+- Adds avatars to the hidden Branch / Tags popover in the _Commit Graph_
+
+### Changed
+
+- 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
+ - Improves performance of loading data for the _Commit Graph_
+ - 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
+ - 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 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))
+
+### 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 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
+- Fixes issues when using older versions of Git (>= Git 2.7.2)
+- Fixes cases where rename detection was not working properly
+
+### Removed
+
+- Deprecates the `gk-target-base` Git configuration key
+
+### 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))
+
+
+
+## Version 17.0
+
+#### Monday, March 31, 2025
+
+GitLens 17 brings powerful new integrations, enhanced AI capabilities, and workflow improvements to help you collaborate more efficiently. This release introduces official Bitbucket integration, adds GitKraken AI as a provider for AI-powered features, delivers new AI capabilities like changelog generation and PR creation, and extends multi-select actions in the Commit Graph.
+
+
+
+### 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.
+
+- Two model options available in this release:
+ - Google Gemini 2.0 Flash
+ - Google Gemini 2.0 Flash-lite
+
+The active AI provider and model that GitLens uses can be found in the Integrations menu in Home View for better visibility and management.
+
+### New AI Features
+
+#### AI Pull Request Creation
+
+Creating meaningful pull requests is now easier than ever with AI-assisted PR creation.
+
+- Automatically generate descriptive titles and detailed descriptions based on your committed changes
+- Save time while providing reviewers with better context about your changes
+- Open a new PR with the generated content directly from GitLens
+
+#### AI Changelog Generation
+
+Need to generate a structured changelog for a group of commits? GitLens 17 makes it simple with AI-powered changelog generation.
+
+- Select multiple commits and generate a well-structured changelog in markdown format
+- Perfect for release notes, documentation, or communicating changes to your team
+
+### Bitbucket Integration
+
+GitLens now offers rich integration with Bitbucket repositories! Connect your Bitbucket account to gain access to issues and pull requests directly within GitLens.
+
+- Support for both Bitbucket Cloud and Bitbucket Data Center
+- Access Bitbucket issues and pull requests in Home View and Launchpad
+- See pull request information within the Commit Graph
+- Seamlessly incorporate Bitbucket into your GitLens workflows
+
+### Commit Graph Enhancements
+
+The Commit Graph now supports taking actions on multiple selected commits, starting with cherry-picking. This makes it easier to work with groups of related commits across branches.
+
+- Select multiple commits in the Graph view and cherry-pick them to your current branch
+- More multi-select actions coming soon, including AI changelog generation
+
+### Plan Updates
+
+We've refreshed GitKraken plans to better reflect how devs and teams work:
+
+- Pro plan remains "Pro" and is limited to 1-2 seats
+- 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.
+
+### 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
+
+### 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 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 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
+ - Adds _Delete Branches..._, _Open Branches on Remote_, _Add to Favorites_, and _Remove from Favorites_ actions to multi-selected branches in GitLens views
+ - Adds _Delete Tags..._ action to multi-selected tags in GitLens views
+ - Adds _Drop Stashes..._ action to multi-selected stashes in GitLens views
+ - Adds _Delete Worktrees..._ and _Open Worktrees in New Window_ actions to multi-selected worktrees in GitLens views
+- 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))
+- 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 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_
+ - Allows the provider to be selected before displaying a list of models
+ - Adds inline actions to reset or configure a provider at the provider step
+- Curated the list of AI models available for GitLens' AI features
+- Improves behavior when opening multiple file changes simultaneously
+- Improves accuracy of file lists and stats for uncommitted changes
+- Changes AI features (stash description, changelog generation) to honor organization settings
+
+### 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 autolinks sometimes not shown in the Inspect view when integrations were disconnected
+- Fixes an issue with overlapping popover UI elements
+
+
+
+## Version 16.3
+
+#### Tuesday, February 11, 2025
+
+GitLens 16.3 brings powerful new integration support, enhanced AI capabilities, and broader editor support to streamline your Git workflows. Here’s what’s new:
+
+
+
+### Azure DevOps Integration
+
+GitLens now supports Azure DevOps! Connect your Azure DevOps account to access issues and pull requests from Azure DevOps directly in Home View, Launchpad, and the Commit Graph, and seamlessly incorporate Azure DevOps into your GitLens workflows.
+
+### Expanded VS Code Editor Support
+
+GitLens now works better in alternative VS Code-based editors, bringing more of its powerful features to IDEs like Cursor and Windsurf.
+
+### Home View Improvements
+
+The Home View is now more responsive to changes in the git state of your active repositories, active and recent branches, and connected integrations. It displays the correct actions when you create branches, merge changes, or modify your working state.
+
+### AI Enhancements
+
+GitLens AI features now include support for the latest AI models from OpenAI, Gemini, DeepSeek, and more. You can now also auto-generate stash messages using AI, in addition to commit messages and commit explanations.
+
+### 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 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 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)
+
+### Changed
+
+- Improves performance of updates to active and recent branches on the _Home_ view
+
+### 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
+
+
+
+## Version 16.2
+
+#### Friday, January 17, 2025
+
+GitLens 16.2 brings support for self-hosted GitHub Enterprise and GitLab Self-Managed integrations, introduces expanded merge target status tracking, and improves search and navigation features in Launchpad and the Home View. New and improved visualizations for file & folder history and improved merge request search make it easier to track changes and manage Git workflows.
+
+
+
+### Self-Hosted GitHub and GitLab Integration Support
+
+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.
+
+### Home View Enhancements
+
+#### Git Action States
+
+Home View now shows when Git actions (such as merge, rebase, cherry-pick, and revert) are paused due to conflicts, or when you're in the middle of a rebase or merge. The indicator lets you continue or skip steps, open the GitLens rebase editor, or abort the operation.
+
+
+
+#### Merge Target Status
+
+In GitLens 16.1, we introduced merge targets in the Home View to display the status of the current branch relative to its merge target and proactively highlights potential conflicts. In 16.2, we've expanded this feature to include status indicators for branches that have already been merged—either locally or into the upstream branch.
+
+This can help identify branches that have been merged but not yet pushed, or branches that have been merged into the upstream branch but not yet deleted.
+
+#### Improved GitLens View Navigation
+
+Home View can now be accessed directly from the Commit Graph, improving context switching between GitLens views.
+
+
+
+### Merge Request Search for GitLab
+
+GitLab and GitLab Self-Managed users can now search for specific merge requests in Launchpad by title, PR number, or URL—even for merge requests they aren't assigned to.
+
+### 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.
+
+### 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.
+
+
+
+### 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 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 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
+ - 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 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 statistics to contributors in the GitLens views when enabled
+- Adds AI model name in commit message generation notifications
+
+### Changed
+
+- Improves branch status icons/indicators on the _Home_ view
+- 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 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
+ Adds Open Visual Folder History to explorer folders
+ 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 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
+- Fixes issues with incorrect aggregate contributor stats
+
+
+
+## Version 16.1
+
+#### Thursday, December 18, 2024
+
+GitLens 16.1 introduces further refinements to the Home View launched in version 16.0, with improved integration and account management, expanded issue association capabilities, and streamlined branch creation. Performance optimizations, proactive conflict detection, and enhanced PR search functionality aim to boost productivity and deliver a more intuitive developer workflow experience.
+
+
+
+### Home View
+
+#### UI/UX Improvements
+
+Branch cards have been redesigned to more clearly display important status information and clearly list associated work items like issues and pull requests. Branch owners are now prominently displayed so you can quickly identify who the primary contributor of a branch is.
+
+#### Integrations & Account Bar
+
+The new integrations and account bar at the top of the Home View provides clear indicators for connecting to and monitoring integration statuses for GitHub, GitLab, and Jira. It also defines account types and states with convenient actions for managing accounts.
+
+### Issue Association
+
+GitLens now offers enhanced support for Issues, allowing you to associate them with branches and pull requests directly from the Home View. This feature streamlines the process of completing units of work and now includes the ability to link issues to existing branches.
+
+### Start Work
+
+The Start Work Flow has been redesigned to simplify and streamline the process of beginning new tasks. Separate flows are now available for starting work from an issue and for creating a new branch. Additionally, the number of steps required to start work on an issue has been reduced, enabling faster transitions from planning to execution.
+
+### Launchpad
+
+Launchpad now offers expanded functionality, allowing you to search for pull requests beyond those directly associated with you or currently in the Launchpad. This expanded capability improves flexibility and access to relevant PRs for better workflow management.
+
+### Merge Target Status `PRO`
+
+GitLens now provides a visual indicator of the status of branches relative to their merge targets. This feature helps you quickly identify branches that are up-to-date, behind, or ahead of their merge targets, streamlining the process of managing and merging branches.
+
+### Conflict Detection `PRO`
+
+GitLens now includes proactive Conflict Detection to help you avoid merge issues. During rebase and merge operations, Pro users will receive warnings about potential conflicts. The Home View will also alert you when the current branch is likely to conflict during rebasing or merging, along with actions to initiate a rebase or merge to proactively resolve conflicts.
+
+### Added
+
+- Remodels and polishes the _Home_ view:
+ - Adds a new header bar with information, controls, and management for your account and integrations
+ - Branch cards are now grouped, expandable sets which include information on the branch, its associated pull requests and issues
+ - Adds "merge target" status to the active branch
+ - Includes the status of the branch relative to the branch that it is most likely to be merged into (its "merge target")
+ - Includes pre-emptive conflict detection with the merge target and _Merge_ and _Rebase_ actions
+ - Adds merge and rebase status to the active branch while in a merge or rebase
+ - Adds a _Commit_ action which automatically generates a commit message and focuses the SCM commit box
+ - Integrates Launchpad status directly into pull requests and adds colored indicators reflecting Launchpad statuses: "Mergeable", "Blocked", and "Needs Attention"
+ - Adds upstream status information to branch cards
+ - Adds more pull request actions:
+ - _Open Pull Request Changes_ which opens a pull request's changes in a multidiff editor tab
+ - _Compare Pull Request_ which opens a pull request in the _Search & Compare_ view
+ - _Open Pull Request Details_ which opens a pull request in the _Pull Request_ view
+ - Adds the ability to share your working changes with teammates
+ - Increases the prominence of the "branch owner's" avatar
+ - 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)
+ - 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)
+ - 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 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)
+
+### Changed
+
+- 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)
+ - 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))
+
+### 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 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_
+- Fixes Jira integration failing to fetch issues for all organizations when there is an issue with one of the organizations
+- Fixes duplicate generic autolinks appearing in _Commit Details_ when the enriched version is shown
+- Fixes the worktree icon in the _Commit Graph_
+- Fixes hovers in the _Commit Graph_ to correctly show branch/tag tips and additions/deletions when the _Changes_ column is enabled
+- Fixes incorrect subscription label in the _Account_ section when signed out
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributor from a recent patch release!
+
+- Emmanuel Ferdman ([@emmanuel-ferdman](https://github.com/emmanuel-ferdman))
+
+
+
+## Version 16.0
+
+#### Thursday, November 14, 2024
+
+GitLens 16 brings a reimagined Home View, streamlined Source Control grouping, improved branch workflows, enhanced graph filtering, new pull request search capabilities, and AI-powered features to boost your productivity.
+
+
+
+### New Home View
+
+GitLens 16 introduces a completely reimagined Home View (accessible via the GitLens icon in the VS Code activity bar) to streamline your development workflow.
+
+The new Home View helps guide your daily workflow by answering key questions: "What am I working on now?", "What do I need to do next?", and "What have I worked on recently?" These answers are provided in the three main sections of the Home View:
+
+#### Repository
+
+Shows your current repository and branch, alongside the repository state and actions for syncing (push, pull, fetch), switching repos/branches, and viewing working directory changes.
+
+If your branch is tied to a pull request or issue, GitLens surfaces those details so you can check PR status, continue reviews, or revisit issue specs. GitLens will also guide you to start a PR from your current branch if it can't find one.
+
+#### Launchpad
+
+Unblocks you and your team by showing pull requests that need your review, are blocked, or are ready to merge. Quickly jump to PRs to review, comment, or merge.
+With the new Start work action, you can easily begin a new branch or worktree, or generate one from an existing issue.
+
+> 💡 Connect integrations to view pull request and issue information in GitLens
+
+#### Recent
+
+Lets you quickly return to previous work by showing recent branches, worktrees, and PRs with activity for your chosen timeframe.
+
+#### 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).
+
+### Consolidated GitLens Source Control Views
+
+GitLens Source Control Views (Commits, Branches, Remotes, etc.) can now be grouped under a unified "GitLens" view. You can navigate grouped views by clicking the icons in the new "GitLens" view, or detach them to be displayed as individual views in Source Control. This should reduce clutter in your workspace and give you more control over which views are prominently displayed.
+
+### "Start Work" Workflow
+
+The new Start Work feature allows you to quickly create a branch or worktree, either from scratch or from an existing GitHub or Jira issue. GitLens will even name your branch based on the issue title and number, making it easy to stay organized. Access it from the Home View or via the command palette `GitLens: Start work`.
+
+### Graph Filtering
+
+We’ve added a toggle to filter the commit graph, allowing you to hide non-matching commits during a search. This makes it easy to focus only on relevant changes.
+
+### Launchpad PR Search
+
+Search pull requests directly from Launchpad—whether they’re included in the default Launchpad filters or not. Search by title, PR number, or URL for quick access. (GitHub support only for now.)
+
+### AI Updates
+
+AI features are now in preview! You’ll see improved UX, support for new models from Anthropic, Open AI, GitHub Copilot, and more. Access to AI features requires a free account.
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributor from a recent patch release!
+
+- Dawn Hwang ([@hwangh95](https://github.com/hwangh95))
+
+### Added
+
+- Adds the ability to group GitLens views into a single GitLens view in the Source Control sidebar
+ - Includes Commits, Branches, Remotes, Stashes, Tags, Worktrees, Contributors, Repositories, Search & Compare, and Launchpad views
+ - Switch views by clicking on the specific view icons in the grouped GitLens view header
+ - Grouped views can be separated (detached) from the grouped GitLens view via context menu commands from the view header
+ - Detached views can be regrouped by clicking the close (`x`) icon in the view header
+ - Adds a new `gitlens.views.scm.grouped.default` setting to specify the default view to show in the grouped GitLens view on new workspaces/folders (otherwise the last selected view is remembered)
+ - Adds a new `gitlens.views.scm.grouped.views` setting to specify which views to show in the grouped GitLens view
+- Adds a completely reimagined Home view
+ - Active section:
+ - Shows your current repository, branch, and repository state
+ - Actions for syncing (push, pull, fetch), switching repos/branches, and viewing working directory changes
+ - Launchpad section:
+ - 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)
+ - 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)
+ - 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):
+ - 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 _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
+
+### Changed
+
+- 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):
+ - 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 _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)
+- Improves quick pick workflows when no repositories are open
+- Renames _GK Workspaces_ (GitKraken Workspaces) to _Cloud Workspaces_
+- Improves revealing items in the GitLens views
+- Limits buffering during logging to reduce memory usage
+
+### 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 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
+- Fixes issues with failing to delete stored state
+- Fixes issues with logging on some failure cases
+- Fixes issues with log scope tracking
+
+### Removed
+
+- Removes the GitLens Welcome view in favor of the new onboarding walkthrough experience
+
+
+
+## Version 15.6
+
+#### Monday, October 7, 2024
+
+GitLens 15.6 arrives with easier branch workflows from within the Commit Graph, Account View integrated into the Home View, improved Cursor support, and a host of other improvements and bug fixes.
+
+
+
+### Commit Graph Improvements
+
+GitLens 15.6 includes several new features and improvements for the Commit Graph:
+
+The graph toolbar now includes a new _Create New Branch_ button in the upper-right corner that allows you to conveniently create a new branch (and worktree, if you prefer) from the current branch or commit. Furthermore, when your current branch is both ahead and behind its upstream, we've added a new _Force Push_ button to the toolbar next to the _Pull_ button that allows you to force push your current branch to its upstream (always force push with caution, as you may lose commits). These new buttons allow for easier entry into common branch workflows directly from the Commit Graph.
+
+The Commit Graph sidebar is now enabled by default. You can disable it by setting `gitlens.graph.sidebar.enabled` to `false` in your settings.
+
+Finally, we've improved the integration indicator and connection button on the upper left corner of the graph toolbar. The icon now more accurately reflects the hosting service for the current repository, and hovering over the connect button now provides some more context on the benefits of connecting the integration.
+
+### Account View moved into Home View
+
+The Account View has been moved into the bottom of the Home View as a new collapsible section. You can quickly jump into the Home View with the _GitLens: Show Home View_ command and expand the Account section to manage your account, cloud integrations and active organization, or leave it collapsed to view account status at a glance.
+
+### Cursor Support
+
+GitLens 15.6 improves support for GitLens in the Cursor editor. Cursor users can now take full advantage of GitLens commands, views and functionality, including account login and sign-up, within Cursor.
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- 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 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)
+- 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 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)
+ - 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)
+
+### 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 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
+- Fixes _Open in Worktree_ command sometimes showing an unnecessary worktree confirmation step
+- Fixes some instances where the progress notification lingers after canceling when connecting an integration
+
+### 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)
+
+
+
+## Version 15.5
+
+#### Thursday, September 12, 2024
+
+GitLens 15.5 brings a few notable changes for the Commit Graph, current branches and worktree creation.
+
+
+
+### Launchpad Preview Ending
+
+Preview access to Launchpad ends on September 27th. After this date, GitLens users will need a Pro account to continue accessing Launchpad and Launchpad View. The Launchpad status bar summary will continue to be free for everyone.
+
+### Commit Graph Sidebar
+
+We've equipped the Commit Graph with a sidebar which gives you quick and convenient access to branches, remotes, stashes, tags, and worktrees from within the graph. Clicking an icon from the sidebar will take you to its respective view. You can enable the new sidebar by setting `gitlens.graph.sidebar.enabled` to `true` in your settings.
+
+### Current Branch Visibility
+
+You now have the option to see your current branch at the top of the list anywhere local branches are shown in views. To enable this feature, turn on `gitlens.views.showCurrentBranchOnTop` in settings.
+
+### Simplified Worktree Creation
+
+We've streamlined the Create Worktree command flow, now prompting for a new branch name only when necessary. This simplifies the creation of worktrees from different sources.
+
+### 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 sidebar to the _Commit Graph_
+ - Shows counts of branches, remotes, stashes, tags, and worktrees
+ - Clicking an item reveals it's corresponding view
+ - Try out this new feature by enable the setting `gitlens.graph.sidebar.enabled` to `true`
+
+### Changed
+
+- Preview access of Launchpad is ending on September 27th
+- Improves the branch comparisons in views to automatically select the base or target branch
+
+### 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
+
+### Removed
+
+- Removes (disables) legacy "focus" editor
+
+
+
+## Version 15.4
+
+#### Wednesday, September 4, 2024
+
+GitLens 15.4 focuses on branches and worktrees, with icon, action, and tooltip upgrades that make the association between branches and worktrees clearer, improved cleanup when deleting a branch with a worktree or a worktree with a branch, improvements to comparisons, and more.
+
+
+
+### Worktee Enhancements
+
+Branches in views and quick pick menus have received a few visual improvements to reduce clutter and make it easier to understand branch state. Branches with worktrees now display a repository icon instead of the typical branch icon, and the tooltip now also indicates that the branch is in a worktree. Branch tooltips now also split out information in a way that is easier to read.
+
+### Branch & Worktree Cleanup Improvements
+
+When a branch has an associated worktree, it is now easier to clean up the associated branch when deleting the worktree, and vice versa. Using the _Git Delete Worktree_ command on a worktree now also includes options to delete or force-delete both the worktree and its associated branch. Similarly, when deleting a branch that has a worktree, the user is first presented with options for deleting the branch's worktree before deleting the branch itself.
+
+### Branch Comparison Improvements
+
+On the _Commits_ view and nested within branches on the _Branches_ view, there is a comparison item to quickly compare the branch with another reference (branch, commit, tag, etc). In GitLens 15.4, we now automatically pick the "best" target branch as the default reference to compare with. Expand the _Ahead_ item to review your changes as they would be applied to the target branch.
+
+### Commit Graph Search Additions
+
+On the _Commit Graph_ (and commit search from the _Search & Compare_ view) you can now limit a search to only search within stashes. Use `type:stash` (or `is:stash`) to highlight all your stashes, or add it to a search query to limit the results to stashes.
+
+### Added
+
+- Adds better support for branches in worktrees
+ - Changes the branch icon to a "repo" icon when the branch is in a worktree in views, quick pick menus, and the _Commit Graph_
+ - Adds an _Open in Worktree_ inline and context menu command and an _Open in Worktree in New Window_ context menu command to branches and pull requests in views and on the _Commit Graph_
+ - Removes the _Switch to Branch..._ inline and context menu command from branches in views and on the _Commit Graph_ when the branch is in a worktree
+- Adds ability to only search stashes when using `type:stash` (or `is:stash`) in commit search via the _Commit Graph_, _Search & Compare_ view, or the _Search Commits_ command
+- Adds `...` inline command for stashes on the _GitLens Inspect_ view
+- Adds an "up-to-date" indicator dot to the branch icon of branches in views
+- Adds an "alt" _Pull_ command for the inline _Fetch_ command on branches in views
+- Adds an "alt" _Fetch_ command for the inline _Pull_ command on branches in views
+- Adds _Open Comparison on Remote_ command to branch comparisons in views
+- Adds new options to the _Git Delete Worktree_ command to also delete the associated branch along with the worktree
+
+### Changed
+
+- Improves the branch comparisons in views to automatically select the base or target branch
+- Improves tooltips on branches, remotes, and worktrees in views
+- _Upgrade to Pro_ flows now support redirects back to GitLens
+
+### 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 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
+- Fixes cloud integrations remaining disconnected after disconnecting and reconnecting to a GitKraken account
+- Fixes "switch" deep links sometimes failing to complete in cases where the switch occurs in the current window
+
+### Removed
+
+- Removes status (ahead, behind, etc) decoration icons from branches in views
+
+
+
+## Version 15.3
+
+#### Tuesday, August 13, 2024
+
+GitLens 15.3 arrives with a host of improvements to popular GitLens features and commands. New branch filtering in the commit graph makes it easier to review history for branches with upstreams to improve pull request reviews. Launchpad has been expanded with GitLab support and is experimentally available as a view. GitHub virtual repositories now support comparisons, and some comparison commands now take a smarter approach to determining directionality of comparison, providing more relevant and useful results.
+
+
+
+### Commit Graph Branch Visibility
+
+The Commit Graph now adds a third branch visibility option: Smart Branches. Existing options allowed you to show all branches or only the current branch (and its upstream). The new Smart Branches option shows the current branch, its upstream, and its base or target branch. This provides enough history to compare local branch changes with upstream changes on your current branch, and against changes with the merge base to determine, for example, whether a rebase is needed or if conflicts might occur. This option is particularly useful for workflows like pull request reviews.
+
+Branch visibility options have now moved out of the graph filter dropdown and into a new branch visibility dropdown to the left of it in the graph header bar.
+
+### Launchpad Improvements
+
+#### GitLab in Launchpad
+
+Launchpad now includes GitLab support! You can connect your GitLab integration and see GitLab merge requests alongside GitHub pull requests. We've also added a new _Connect Additional Integrations_ button to the titlebar of Launchpad that lets you easily connect additional integrations.
+
+#### Launchpad View (Experimental)
+
+We're experimenting with bringing Launchpad into a view so that you can keep it open and view pull request details at a glance, in a tree format. You can enable this experimental feature either by running the _Show Launchpad View_ command or setting `gitlens.views.launchpad.enabled` to `true` in your settings file.
+
+### Comparison Improvements
+
+When comparing commits, stashes, and tags with the HEAD commit via context menu commands, the comparison now uses a combination of commit topology and the timestamp of the reference and HEAD commit in order to determine the directionality of the comparison.
+
+When comparing a commit with the HEAD commit, for example, we order the comparison from the HEAD commit to the chosen commit if it is ahead in time from the HEAD commit, and from the chosen commit to the HEAD commit if it is behind. This ensures that this command, now called _Compare to/from HEAD_, is more useful in general since the revision history within the comparison is always forward-looking.
+
+Virtual repositories, such as GitHub repositories opened locally with the GitHub Repositories extension or on vscode.dev or github.dev, now also support comparison commands within views and the Commit Graph.
+
+### Added
+
+- Adds improvements and enhancements to _Launchpad_ to make it easier to manage and review pull requests
+ - 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!
+ - 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 pull request information to branches with missing upstreams
+- 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
+
+### Changed
+
+- Improves the _Compare to/from HEAD_ command (previously _Compare with HEAD_) to compare commits, stashes, and tags with the HEAD commit where directionality is determined by topology and time
+- Improves the messaging of the merge and rebase commands
+- Renames _Compare with Working Tree_ command to _Compare Working Tree to Here_
+- Renames _Compare Common Base with Working Tree_ command to _Compare Working Tree to Common Base_
+- Renames _Open Worktree in New Window_ Launchpad command to _Open in Worktree_
+- Renames _Open Directory Compare_ command to _Open Directory Comparison_
+- Renames _Open Directory Compare with Working Tree_ command to _Directory Compare Working Tree to Here_
+- Improves some messaging on _Switch_ and _Checkout_ commands
+
+### 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 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
+- Fixes an error with queries that can cause Jira Cloud and other cloud integrations to stop working
+- Fixes issues with some directory comparison commands
+
+
+
+## Version 15.2
+
+#### Wednesday, July 10th, 2024
+
+GitLens 15.2 introduces several new features and improvements. This release focuses on enhancing the Commit Graph and Launchpad, expanding AI-generated messaging, and additional AI support for the latest Anthropic models.
+
+
+
+### Commit Graph Improvements
+
+The Commit Graph now provides rich hovers on commit rows. These hovers include detailed commit information and links to related pull requests, issues, and linking to Inspect. We've also added pull request markers to the graph scroll and minimap, offering visual queues of PR activity in your repo history.
+
+### Launchpad Improvements
+
+We've added a new "Open Worktree in New Window" action to the Launchpad. This feature allows you to quickly open specific branches of pull requests in a separate VS Code window, minimizing context switching when working on multiple tasks.
+
+### AI-Generated Descriptions
+
+You can now generate titles and descriptions for Cloud Patches and Code Suggest. This is available using the "Generate Title & Description" button within the title input of the _Create Cloud Patch_ view and in the _Changes to Suggest_ section of the Inspect Overview tab. It uses the AI provider of your choice, helping to save time in creating meaningful titles and descriptions.
+
+### Claude 3.5 Sonnet Support
+
+GitLens now supports Anthropic's latest Claude 3.5 Sonnet model for our experimental AI features. You can switch to this version by selecting `GitLens: Switch AI Model` from the command palette.
+
+### Added
+
+- Adds a _Generate Title & Description_ button to the title input in _Create Cloud Patch_ and in _Changes to Suggest_ of the _Inspect Overview_ tab
+- Adds support for Anthropic's Claude 3.5 Sonnet model for GitLens' experimental AI features
+- Adds a new `counts` option to the `gitlens.launchpad.indicator.label` setting to show the status counts of items which need your attention in the _Launchpad_ status bar indicator
+- Adds _Search for Commits within Selection_ command to the editor context menu when there is a selection
+- Adds a `gitlens.launchpad.ignoredOrganizations` setting to specify an array of organizations (or users) to ignore in the _Launchpad_
+- Improves the tooltips of stashes in GitLens views
+ - Adds a `gitlens.views.formats.stashes.tooltip` setting to specify the tooltip format of the stashes in GitLens views
+- Improves the display of branch and tag tips in the _File History_ and _Line History_ and in commit tooltips in GitLens views
+ - Adds provider-specific icons to tips of remote branches
+- Adds Commit Graph improvements:
+ - Adds pull request markers to the graph scroll and minimap
+ - Adds rich hovers on commit rows which include detailed commit information and links to pull requests, issues, and inspect
+- Adds Launchpad improvements:
+ - Truncates long titles for Pull Requests so that the repository label is always visible
+ - Adds _Open on GitHub_ button to other relevant rows in the action step
+ - Adds a new _Open Worktree in New Window_ action and button to Launchpad items to more easily view the item in a worktree
+
+### Changed
+
+- Renames `Reset Stored AI Key` command to `Reset Stored AI Keys...` and adds confirmation prompt with options to reset only the current or all AI keys
+- Renames _Open Inspect_ to _Inspect Commit Details_
+- Renames _Open Line Inspect_ to _Inspect Line Commit Details_
+- Renames _Open Details_ to _Inspect Commit Details_
+- Replaces _Open in Editor_ link in the Launchpad with a link to _gitkraken.dev_
+- The _Manage Account_ button in the GitKraken Account view and the _GitLens: Manage Your Account_ command now use the account management page at _gitkraken.dev_
+- Fixes some cases where worktree state can be out-of-date after creation/deletion of a worktree
+
+### 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 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_
+- Fixes deep links failing to cancel in the remote add stage
+
+
+
+## Version 15.1
+
+#### Wednesday, June 5th, 2024
+
+We're excited to announce the latest release of GitLens, bringing you expanded AI capabilities, a better Launchpad experience, and bug fixes reported by our community.
+
+
+
+### GitHub Copilot and AI Model Integration
+
+
+
+GitLens now supports integration with GitHub Copilot and other VS Code extension-provided AI models for its experimental AI features. Simply select a model from the quickpick after choosing a GitLens AI action.
+
+> You can also specify the AI model you want to use through the new `gitlens.ai.experimental.model` setting. When the model is set to `vscode`, specifying the `gitlens.ai.experimental.vscode.model` setting will target the VS Code extension-provided AI model you want to use.
+
+To simplify the overall configuration of AI models, we have unified all settings under: `gitlens.ai.experimental.model`. This replaces the previous provider-specific settings, making it more straightforward to specify the AI model you want to use.
+
+### Launchpad Enhancements
+
+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!
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- bm-w ([@bm-w](https://github.com/bm-w))
+
+### Added
+
+- Adds support for GitHub Copilot and other VS Code extension-provided AI models for GitLens' experimental AI features
+ - Adds a `gitlens.ai.experimental.model` setting to specify the AI model to use
+ - Adds a `gitlens.ai.experimental.vscode.model` setting to specify the VS Code extension-provided AI model to use when `gitlens.ai.experimental.model` is set to `vscode`
+- Adds new Launchpad improvements:
+ - Collapsed state of Launchpad groups are now saved between uses
+ - The _Draft_ and _Pinned_ categories in the Launchpad now always sort their items by date
+ - The Launchpad and Launchpad status bar indicator now indicate when there is an error loading data
+ - The Launchpad indicator now shows the Launchpad icon next to the loading spinner when the Launchpad is loading
+
+### Changed
+
+- Changes the settings used to configure the AI models for GitLens' experimental AI features
+ - Adds a `gitlens.ai.experimental.model` setting to specify the AI model to use
+ - Removes the `gitlens.ai.experimental.provider`, `gitlens.ai.experimental.openai.model`, `gitlens.ai.experimental.anthropic.model`, and `gitlens.ai.experimental.gemini.model` settings in favor of the above
+
+### 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
+
+
+
+## Version 15.0
+
+#### Tuesday, May 14th, 2024
+
+With the release of GitLens 15 comes some of GitLens' most exciting features yet, Launchpad, Code Suggest, Jira integration and so much more. This release is packed with tools and enhancements to improve code review workflows and makes it easier than ever to keep your team unblocked.
+
+
+
+### Launchpad
+
+GitLens 15 introduces a preview of the Launchpad, a new Pro feature that brings your GitHub pull requests into a unified, categorized list. The Launchpad categorizes pull requests by status, making it easy to see which pull requests are ready to merge, blocked, need your review, and more. Use the Launchpad to quickly action on the highest priority pull requests and keep your team unblocked.
+
+Once you've selected a pull request in the Launchpad, you can choose from a list of actions to take on that pull request, including merging the pull request, opening the pull request on GitHub, switching to or creating a branch or worktree for the pull request, viewing the pull request's changes, and more.
+
+Also included is a Launchpad status bar icon which provides a pulse on the most critical pull request needing your attention, and a summary of your most critical pull requests on hover.
+
+You can open the new Launchpad directly from its status bar icon by clicking the icon or by using the new _GitLens: Open Launchpad_ command. Clicking a category in the Launchpad status bar icon tooltip will open the Launchpad directly to that category.
+
+### Code Suggest
+
+Code Suggest is a new cloud feature that frees your code reviews from the unnecessary restrictions of GitHub's comment-style code suggestions. Code suggestions can be created from any code and right from inside the convenience of your IDE.
+
+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.
+
+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.
+
+### Jira Integration
+
+GitLens 15 introduces rich Jira Cloud integration, enabling automatic, rich Jira autolinks in commit messages wherever autolinks are supported in GitLens. You can connect to Jira by clicking the _Cloud Integrations_ button in the GitKraken Account view or by using the new _GitLens: Manage Cloud Integrations_ command. Once connected, rich autolinks will automatically populate for Jira issues in your commit messages.
+
+Support for more cloud integrations and other Jira integration features are coming soon.
+
+### Gemini and Latest OpenAI & Anthropic Model Support
+
+This release also adds support for Google Gemini for GitLens' experimental AI features. You can specify the Gemini model to use with the new `gitlens.ai.experimental.gemini.model` setting.
+
+We've also expanded our OpenAI and Anthropic model support to include the latest models.
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- 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
+ - Open using the new _GitLens: Open Launchpad_ command
+ - Categorizes pull requests by status
+ - _Current Branch_: Pull requests associated with your current branch
+ - _Ready to Merge_: Pull requests without conflicts, ci failures, change suggestions or other issues preventing merge
+ - _Blocked_: Pull requests with conflicts, CI failures, or that have no reviewers assigned
+ - _Needs Your Review_: Pull requests waiting for your review
+ - _Requires Follow-Up_: Pull requests that have been reviewed and need follow-up
+ - _Draft_: Draft pull requests
+ - _Pinned_: Pull requests you have pinned
+ - _Snoozed_: Pull requests you have snoozed
+ - _Other_: Other pull requests
+ - Action on a pull request directly from the Launchpad:
+ - Merge a pull request
+ - Open a pull request on GitHub
+ - Switch to or create a branch or worktree for a pull request to review changes
+ - Display a pull request's details in the _Overview_
+ - Open a pull request's changes in the multi-diff editor
+ - View a pull request's branch in the _Commit Graph_
+ - View or create code suggestions for a pull request
+ - Pin or snooze a pull request in the Launchpad
+ - Adds a status bar indicator of the _Launchpad_
+ - Opens the Launchpad when clicked
+ - Shows the top pull request and its status in the status bar
+ - Also highlights your top pull request in the launchpad when opened from the indicator
+ - Provides a summary of your most critical pull requests on hover
+ - Each summary line includes a link to open the Launchpad to that category
+ - Adds new settings for the Launchpad and indicator
+ - `gitlens.launchpad.ignoredRepositories`: Array of repositories with `owner/name` format to ignore in the Launchpad
+ - `gitlens.launchpad.staleThreshold`: Value in days after which a pull request is considered stale and moved to the _Other_ category
+ - `gitlens.launchpad.indicator.enabled`: Specifies whether to show the Launchpad indicator in the status bar
+ - `gitlens.launchpad.indicator.icon`: Specifies the style of the Launchpad indicator icon
+ - `gitlens.launchpad.indicator.label`: Specifies the style of the Launchpad indicator label
+ - `gitlens.launchpad.indicator.groups`: Specifies which critical categories of pull requests to summarize in the indicator tooltip
+ - `gitlens.launchpad.indicator.useColors`: Specifies whether to use colors in the indicator
+ - `gitlens.launchpad.indicator.openInEditor`: Specifies whether to open the Launchpad in the editor when clicked
+ - `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
+ - 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.
+ - 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
+ - Adds a _Pull Request_ badge to the Graph and the Inspect Overview
+- Adds rich Jira Cloud integration
+ - Enables rich automatic Jira autolinks in commit messages everywhere autolinks are supported in GitLens
+ - Adds a _Cloud Integrations_ button to the GitKraken Account view and a new `GitLens: Manage Cloud Integrations` command to manage connected cloud integrations
+ - Adds a _Manage Jira_ button to _Inspect_ and a link in Autolink settings to connect to Jira
+- Adds support for Google Gemini for GitLens' experimental AI features
+ - Adds a `gitlens.ai.experimental.gemini.model` setting to specify the Gemini model
+- Adds support for the latest OpenAI and Anthropic models for GitLens' experimental AI features
+- Adds a new `gitlens.views.collapseWorktreesWhenPossible` setting to specify whether to try to collapse the opened worktrees into a single (common) repository in the views when possible
+
+### Changed
+
+- Reworks _Commit Details_, now called the _Inspect_ view
+ - Revamps the _Working Changes_ tab into the _Overview_ tab
+ - Provides richer branch status information and branch switching
+ - Adds Push, Pull, and Fetch actions
+ - Richer Pull Request Information
+ - Open details in the Pull Request view
+ - Links to open and compare changes
+ - List of the PR's Code Suggestions
+ - Create a Code Suggestion by clicking the _Suggest Changes for PR_ button
+- Improves contributor and team member picking for the adding co-authors, _Code Suggest_, and _Cloud Patches_
+- Improves performance when creating colors derived from the VS Code theme
+- Changes the command to open the Launchpad in the editor (formerly _Focus View_) from _GitLens: Show Focus_ to _GitLens: Open Launchpad in Editor_
+- Renames the setting `gitlens.focus.allowMultiple` to `gitlens.launchpad.allowMultiple`
+- Updates most deep link prompts to quick picks or quick inputs, moves most prompts to before a repository is opened.
+- Updates Pro upgrade links to use the newer gitkraken.dev site
+
+### 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...
+
+
+
+## Version 14.9
+
+#### Wednesday, March 6, 2024
+
+The 14.9 release of GitLens brings improved reviewing of branch changes and new Anthropic Claude models along with general fixes and improvements.
+
+
+
+### Improved reviewing of Branch Changes
+
+Two new commands were added to branches in the _Commit Graph_ and views. The `Compare with Common Base` enables reviewing changes as if the selected branch were to be merged by comparing the common ancestor (merge base) with the current branch to the selected branch. Use the new `Open All Changes with Common Base` command to review the changes as if the selected branch were to be merged in the multi-diff editor.
+
+### Anthropic Claude Models
+
+We've added support for Anthropic's Claude 3 Opus & Sonnet models for GitLens' experimental AI features. You can select these models from the `GitLens: Switch AI Model` command in the Command Palette. You can then use these models with the `GitLens: Generate Commit Message (Experimental)...` command in the Command Palette or in the `Explain (AI)` panel of _Commit Details_ and _Cloud Patch Details_ views.
+
+### Added
+
+- Adds support for Anthropic's Claude 3 Opus & Sonnet models for GitLens' experimental AI features
+- Adds a _Compare with Common Base_ command to branches in the _Commit Graph_ and views to review the changes if the selected branch were to be merged by comparing the common ancestor (merge base) with the current branch to the selected branch
+- Adds an _Open All Changes with Common Base_ command to branches in the _Commit Graph_ and views to review the changes if the selected branch were to be merged in the multi-diff editor
+- Adds a _Stash All Changes_ command to Source Control repository toolbar (off by default)
+- Adds the repository name as a prefix to worktree name when adding to the current workspace
+- Adds a better message when stashing only untracked files without including untracked files
+
+### 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)
+- 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 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
+
+
+
+## Version 14.8
+
+#### Thursday, February 8, 2024
+
+The 14.8 release of GitLens features several enhancements to make it easier to use worktrees, view diffs and pull-requests, and includes enterprise improvements for Cloud Patches.
+
+
+
+### Worktree Workflow Improvements `PRO`
+
+We've improved and streamlined the process of creating and opening worktrees. This includes new options for creating a worktree when switching branches as well as skipping prompts for remote creating and just auto-adding them. We've also added a command for copying your current working changes to an existing worktree.
+
+### VS Code Multi-diff Support
+
+VS Code's new multi-diff editor is out of experimental, so we've enabled it in our commands by default for VS Code 1.86 and above. The multi-diff editor allows you to view changes across multiple files in a single tab, instead of switching between tabs. This makes comparing a set of changes across files much easier.
+
+### 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.
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- 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
+ - 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
+ - Avoids prompt to add a (required) remote and instead auto-adds the remote during worktree creation from a pull request
+- Adds ability to open multiple changes in VS Code's new multi-diff editor, previously experimental and now enabled by default
+ - Adds an inline _Open All Changes_ command to commits, stashes, and comparisons in the views
+ - Changes _Open All Changes_ & _Open All Changes with Working Tree_ commands to use the new multi-diff editor when enabled
+ - Adds _Open All Changes, Individually_ & _Open All Changes with Working Tree, Individually_ commands to provide access to the previous behavior
+ - Renames the `gitlens.experimental.openChangesInMultiDiffEditor` setting to `gitlens.views.openChangesInMultiDiffEditor`, which is enabled by default, to specify whether to open changes in the multi-diff editor (single tab) or in individual diff editors (multiple tabs)
+ - Requires VS Code `1.86` or later, or VS Code `1.85` with `multiDiffEditor.experimental.enabled` enabled
+- Adds new comparison features to pull requests in GitLens views
+ - Adds an _Open Pull Request Changes_ context menu command on pull requests in the _Commit Graph_ and other GitLens views to view pull request changes in a multi-diff editor (single tab)
+ - Requires VS Code `1.86` or later, or VS Code `1.85` with `multiDiffEditor.experimental.enabled` enabled
+ - Adds a _Compare Pull Request_ context menu command on pull requests in the _Commit Graph_ and other GitLens views to open a comparison between the head and base of the pull request for easy reviewing
+- Adds an _Open in Commit Graph_ context menu command on pull requests in GitLens view to open the tip commit in the _Commit Graph_
+- Adds ability to copy changes, commits, stashes, and comparison as a patch to the clipboard
+ - Adds a _Copy as Patch_ context menu command on files, commits, stashes, and comparisons in GitLens views
+ - Adds a _Copy as Patch_ context menu command on files in the _Changes_ and _Staged Changes_ groups as well as the groups themselves in the _Source Control_ view
+ - Adds a _Apply Copied Patch_ command in the command palette to apply a patch from the clipboard
+- 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)
+ - 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 _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 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
+
+### Changed
+
+- Changes adds avatars to commits in quick pick menus
+- Changes the pull request to be first item in the _Commits_ view, when applicable
+- Changes the branch comparison to be below the branch status in the _Commits_ view to keep top focus on the status over the comparison
+- Renames "Open Worktree for Pull Request via GitLens..." to "Checkout Pull Request in Worktree (GitLens)..."
+- Renames the `gitlens.experimental.openChangesInMultiDiffEditor` setting to `gitlens.views.openChangesInMultiDiffEditor` as it is no longer experimental and enabled by default
+
+### Fixed
+
+- 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))
+
+
+
+## Version 14.7
+
+#### Wednesday, January 16, 2024
+
+With GitLens 14.7, we're kicking off 2024 with some bugfixes and some new features for Cloud Patches and Deep Links, and more.
+
+
+
+### Cloud Patch Collaboration ☁️
+
+You can now add members of your GitKraken organization as collaborators on cloud patches you created or maintain as an admin. To invite a collaborator, click on one of your cloud patches in the _Cloud Patches_ view to open its patch details, and then click on the _Invite_ button. You can then select one or more members of your organization to add as collaborators on the patch. Once selected, you can choose a role for each collaborator, and click _Update Patch_ when done to finish adding collaborators.
+
+Cloud patches you've been invited to as a collaborator appear under the _Shared with Me_ category in the _Cloud Patches_ view.
+
+### Deep Links to Files and Code
+
+You can now create (and use) deep links to files and code in GitLens. Create links to files using the new _Copy Link to File_ and _Copy Link to File at Revision..._ commands in the _Copy As_ submenu of the editor context menu and in the _Share_ submenu of files in GitLens views.
+
+If you have code selected in an editor tab, you'll also have the option to link to the selected lines using the new _Copy Link to Code_ command in the _Copy As_ submenu of that tab's context menu.
+Use or share these links to quickly and easily open the referenced file or code in an editor tab.
+
+### Thank you to our contributors
+
+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))
+
+### Added
+
+- Adds the ability to share Cloud Patches with specific members of your GitKraken organization
+ - You can now share Cloud Patches exclusively with specific members of your organization by selecting _Collaborators Only_ when viewing or creating a Cloud Patch
+ - Click the _Invite_ button at the bottom of the _Patch Details_ view to add members of your organization to collaborate and click _Update Patch_ to save your changes
+ - Cloud Patch collaborators will see these Patches under the _Shared with Me_ section of the _Cloud Patches_ view
+- 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 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)
+ - 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)
+
+### Changed
+
+- 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 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)
+
+
+
+## Version 14.6
+
+#### Wednesday, December 13, 2023
+
+GitLens 14.6 marks our last release of 2023 and with it some great enhancements to Cloud Patches, Focus View and much more!
+
+
+
+### Cloud Patch Sharing Options ☁️
+
+Users can now specify who can access shared Cloud Patches, choosing between anyone with a link or only members of your GitKraken organization with the link.
+
+Coming soon is the ability to explicitly select individuals from your organization as collaborators. Cloud Patches explicitly shared to you, i.e. you are a collaborator, will appear in the Cloud Patches view under "Shared with Me".
+
+> Note: If you have multiple organizations, you can easily switch between them from the GitKraken Account view.
+
+### Focus View Timed Snoozing
+
+The focus view now supports timed snoozing of items. Select a duration like 1 hour or 4 hours when snoozing a focus item and then that item will automatically move back when the time expires.
+
+### Experimental Multi-diff Editor
+
+You can now open changes in VS Code's new multi-diff editor. This requires VS Code 1.85 or later with the `multiDiffEditor.experimental.enabled` and `gitlens.experimental.openChangesInMultiDiffEditor` settings enabled.
+
+#### Commands using Multi-diff
+
+- `Open Folder Changes with Revision...` and `Open Folder Changes with Branch or Tag...` commands using the Command Palette as well as the Explorer and Source Control views
+- An inline `Open All Changes` command for commits, stashes, and comparisons in the views
+- `Open All Changes` and `Open All Changes with Working Tree` will use the new multi-diff editor when enabled
+
+> Note: `Open All Changes, Individually` and `Open All Changes with Working Tree, Individually` commands were added to provide access to the previous behavior.
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributor for this release!
+
+- 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
+ - (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 _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 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
+ - Changes _Open All Changes_ & _Open All Changes with Working Tree_ commands to use the new multi-diff editor when enabled
+ - Adds _Open All Changes, Individually_ & _Open All Changes with Working Tree, Individually_ commands to provide access to the previous behavior
+ - 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 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.
+
+### Changed
+
+- Improves AI model choice selection for GitLens' experimental AI features
+- Improves performance when logging is enabled
+- Changes the contextual view title from GL to GitLens
+
+### 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 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
+- Fixes issues with _Contributors_ view updating when changing toggles
+- Fixes issues with _Open [Previous] Changes with Working File_ command in comparisons
+- Fixes banner styling on the _Commit Graph_
+
+
+
+## Version 14.5
+
+#### Monday, November 13, 2023
+
+GitLens 14.5 features the all new Cloud Patches preview ☁️, which allows you to easily share changes with other developers by creating a Cloud Patch from your WIP, commit or stash and sharing the generated link with your teammates. Other notable enhancements include opening multiple tabs of Commit Graph & Focus.
+
+
+
+### 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.
+
+### Open Multiple Commit Graph & Focus Tabs
+
+Open multiple instances of the Commit Graph, Focus, and Visual File History views, side-by-side, to look at multiple repositories at once or just different visualizations of the same repository.
+
+### Thank you to our contributors
+
+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))
+
+### 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:
+ - 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
+ - Adds a _Share as Cloud Patch..._ command to the command palette and to the _Share_ submenu in applicable GitLens views
+ - Adds a `gitlens.cloudPatches.enabled` setting to specificy whether to enable Cloud Patches (defaults to `true`)
+- Adds support to open multiple instances of the _Commit Graph_, _Focus_, and _Visual File History_ in the editor area
+ - Adds a _Split Commit Graph_ command to the _Commit Graph_ tab context menu
+ - Adds a `gitlens.graph.allowMultiple` setting to specify whether to allow opening multiple instances of the _Commit Graph_ in the editor area
+ - Adds a _Split Focus_ command to the _Focus_ tab context menu
+ - Adds a `gitlens.focus.allowMultiple` setting to specify whether to allow opening multiple instances of the _Focus_ in the editor area
+ - 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)
+- 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 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 _Collapse_ command to many view nodes
+- Adds a `gitlens.liveshare.enabled` setting to specify whether to enable integration with Visual Studio Live Share
+
+### Changed
+
+- 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)
+- 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 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
+- Fixes issue when clicking on commits in the Visual File History to open the _Commit Details_ view
+- Fixes issue opening stashes in the _Commit Details_ view from the _Stashes_ view
+- Fixes issue where GitHub/GitLab enriched autolinks could incorrectly point to the wrong repository
+- Fixes issue showing folder history in the _File History_ view when there are uncommitted changes (staged or unstaged)
+- Fixes issue when pushing to a remote branch with different name than the local
+- Fixes tooltip styling/theming on the _Commit Graph_
+- Fixes issues staged files in repositories not "opened" (discovered) by the built-in Git extension
+
+
+
+## Version 14.4
+
+#### Friday, October 13, 2023
+
+GitLens 14.4 is here, featuring new enhancements to _Focus View_, the addition of _Working Changes_ to _Commit Details_ and _Graph Details_, and some performance improvements to _Inline_ and _Status Bar Blame_.
+
+
+
+### Focus View Enhancements
+
+_Focus View_ now includes the ability to pin and snooze items. These options appear as clickable icons in the new snooze/pin column in the view. Pinned issues and pull requests will always show at the top of the list, while snoozed items will be hidden and moved to the new Snoozed section. To unsnooze an item, simply click on the Snoozed section header and select the unsnooze icon for that item in the pin/snooze column.
+
+
+
+### Working Changes Tab
+
+_Commit Details_ and _Graph Details_ now include a separate _Working Changes_ tab. This allows you to view your work-in-progress changes any time without losing context on your current selected change. The tab includes the ability to stage and unstage changes, open files to view changes, and open the changes in the _Commit Graph_ and SCM view.
+
+
+
+### Inline and Status Bar Blame Performance Improvements
+
+Inline blame and status bar blame now appear faster on hover. This performance improvement is especially notable when using connected remote integrations.
+
+### Added
+
+- 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 `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}`
+ - Adds a _Share_ submenu with a _Copy Link to Workspace_ command to workspaces in the _GitKraken Workspaces_ view
+
+### 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 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 
+
+### Commit Graph Improvements
+
+
+
+You can now have a Commit Graph in the bottom Panel and one in the Editor Area open at the same time. This enables viewing more than repo at a time or different areas of the same repo at the same time.
+
+
+
+Additionally, you can also set a preference for which mode to use by default, which you can set from the gear icon on the Commit Graph or by adding `gitlens.graph.layout` in settings. _GitLens: Show Commit Graph_ from the command palette will honor that preference.
+
+### Search & Compare Review Checkboxes
+
+
+
+From the _Search & Compare_, you now have checkboxes next to each files to help keep track of files you've reviewed. This was an long sought after request by the community, you asked and we delivered!
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributor for this release!
+
+- 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)
+- 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))
+
+### Changed
+
+- Changes the `gitlens.graph.layout` setting to be a default preference rather than a mode change
+
+### Fixed
+
+- 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
+
+
+
+## Version 14.2
+
+#### Friday, August 4, 2023
+
+GitLens 14.2 arrives with a few hotly-requested improvements to the Focus View for even greater productivity in your daily workflow.
+
+
+
+## Focus View
+
+The Focus View has been improved with a new unified experience and includes a few new features to help you navigate pull requests and issues.
+
+
+
+Pull Requests and Issues have now been combined into a single view with tabs to quickly toggle between showing all items, pull requests, or issues only.
+
+You can also click on a branch name to show the branch on the Commit Graph, and if you don't already have a remote configured for that branch you'll be guided to add it.
+
+
+
+Furthermore, we've added a search bar to the Focus View to help you quickly find pull requests or issues by their title.
+
+### Thank you to our contributors
+
+Shout-out to all of our awesome contributors for this release!
+
+- Victor Hallberg ([@mogelbrod](https://github.com/mogelbrod))
+
+### Added
+
+- Improves the _Focus_ view experience
+ - Unifies pull requests and issues into a single view
+ - Adds tabs to switch between showing Pull Requests, Issues, or All
+ - Adds a filter/search box to quickly find pull request or issues by title
+ - Adds ability to click on a branch name to show the branch on the _Commit Graph_
+- Adds a new command _Open Changed & Close Unchanged Files..._ to the command palette, the context menu of the _Commit Graph_ work-in-progress (WIP) row, and the SCM group context menu to open all changed files and close all unchanged files.
+- Adds a new command _Reset Current Branch to Tip..._ to branch context menus in the _Commit Graph_ and in GitLens views to reset the current branch to the commit at the chosen branch's tip.
+
+### Changed
+
+- Changes _Compact Graph Column Layout_ context menu command to _Use Compact Graph Column_ for better clarity
+- Changes _Default Graph Column Layout_ context menu command to _Use Expanded Graph Column_ for better clarity
+- Improves remote parsing for better integration support for some edge cases
+
+### 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 issues with missing worktrees breaking the Worktrees view and Worktree quick pick menus
+
+
+
+## Version 14.1
+
+### Thursday, July 13, 2023
+
+We're delighted to introduce GitLens 14.1. We've enhanced integration between GitKraken Cloud and VS Code workspaces. You can now link a GitKraken Cloud workspace and VS Code workspace and GitLens can automatically update your VS Code workspace when new repositories are added to its linked counterpart.
+Additionally, we've added deep link support for comparisons in the _Search & Compare_ view, coupled with a new _Copy Link to Comparison_ command in a new _Share_ submenu, streamlining review and collaboration.
+
+We've also added support for Anthropic's new Claude 2 model for use with our experimental AI features. You can switch to it using the _Switch AI Model_ command from the Command Palette.
+
+
+
+## Workspace Linking
+
+When you create a VS Code workspace from a GitKraken Cloud workspace, the two are now linked. You can open a linked VS Code workspace from its cloud workspace using the new _Open VS Code Workspace in New Window_ option (hold alt to open in the current window).
+
+
+
+When repositories are added to a GitKraken Cloud workspace, you can automatically add those repositories to its linked VS Code workspace when that workspace is opened. You can choose to automatically add new repositories, be prompted to add them, or disable auto-adding repositories altogether for that workspace. You'll be prompted to choose your desired behavior when creating the VS Code workspace, but it can also be changed at any time via the _Change Linked Workspace Auto-Add Behavior..._ context menu command on the _Current Window_ item or its linked workspace in the _GitKraken Workspaces_ view.
+
+
+
+You can also manually add repositories to the VS Code workspace at any time using the new _Add Repositories from Linked Workspace..._ context menu command.
+
+
+
+## Comparison Deep Links
+
+You can now deep link directly into comparisons in the _Search & Compare_ view. This includes comparisons between branches, tags, and commits. You can also copy a deep link to a comparison to your clipboard using the new _Copy Link to Comparison_ context menu command on the _Share_ submenu.
+
+
+
+### Thank you to our contributors
+
+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))
+
+### Added
+
+- Adds the ability to link a GitKraken Cloud workspace with an associated VS Code workspace
+ - Adds ability to automatically add repositories to the current VS Code workspace that were added to its associated GitKraken Cloud workspace, if desired
+ - Adds a _Change Linked Workspace Auto-Add Behavior..._ context menu command on the _Current Window_ and linked workspace to control the desired behavior
+ - Adds an _Add Repositories from Linked Workspace..._ context menu command on the _Current Window_ item to trigger this manually
+ - Adds a new _Open VS Code Workspace_ command to open an existing VS Code workspace associated with a GitKraken Cloud workspace
+ - Adds a highlight (green) to the linked GitKraken Cloud workspace when the current VS Code workspace is associated with it in the _GitKraken Workspaces_ view
+- Adds deep link support for comparisons in the _Search & Compare_ view
+ - Deep link format: `vscode://eamodio.gitlens/r/{repoId}/compare/{ref1}[..|...]{ref2}?[url={remoteUrl}|path={repoPath}]`
+ - Adds a _Share_ submenu with a _Copy Link to Comparison_ command to comparisions in the _Search & Compare_ view
+- Adds support for Anthropic's Claude 2 AI model
+- Adds a progress notification while repositories are being added to a GitKraken Cloud workspace
+
+### Changed
+
+- Improves scrolling performance on the _Commit Graph_
+- Renames _Convert to VS Code Workspace_ to _Create VS Code Workspace_ for workspaces in the _GitKraken Workspaces_ view to better reflect the behavior of the action
+- Hides _Create VS Code Workspace_ and _Locate All Repositories_ commands on empty workspaces in the _GitKraken Workspaces_ view
+
+### 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 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
+
+### Wednesday, June 14, 2023
+
+We're thrilled to announce the release of GitLens 14 with a reimagined GitLens experience! We restructured our views layout to better enhance productivity and focus by grouping views contextually, giving you easy access to the right information when you need it. The commit graph has been moved to the (bottom) panel, providing convenient and persistent access to the graph and its details. We've also rethought and rebuilt our Welcome and Walkthrough as well as the Home view to provide a friendlier onboarding experience.
+
+The power of GitKraken Workspaces now in GitLens. Workspaces are an easy way to work with and manage multiple repositories and include the ability to convert to and from a VS Code workspace, with further improvements coming soon. Create workspaces just for yourself or share (coming soon to GitLens) them with your team for faster onboarding and better collaboration.
+
+
+
+## New Views layout
+
+We've grouped views contextually and introduced GitLens Inspect, giving you easy access to the right information when you need it. We've moved some of our views from their previous home, in Source Control, into either the GitLens or the new GitLens Inspect side bar.
+
+
+
+### GitLens Inspect side bar
+
+The all-new GitLens Inspect is like an x-ray or developer tools inspector into your code, which focuses on providing contextual information and insights to what you're actively working on.
+
+
+
+Views include:
+
+- Commit Details
+- Line History
+- File History
+- Visual File History
+- Search & Compare
+
+_Pro tip: you can drag the entire GitLens Inspect Side Bar onto your secondary Side Bar, without needing to arrange views on-by-one._
+
+### GitLens side bar
+
+We've re-focused this to be the home of GitKraken services (e.g. GitKraken Workspaces) as well as discovery, help, and support.
+
+
+
+Views include:
+
+- Home view
+- GitKraken Workspaces
+- GitKraken Account
+
+### Source Control side bar
+
+We've slimmed down this side bar to only contain views that are focused on your repositories.
+
+
+
+Views include:
+
+- Commits
+- Branches
+- Remotes
+- Stashes
+- Tags
+- Worktrees
+- Contributors
+- Repositories (hidden by default)
+
+### (Bottom) Panel
+
+The new home for the Commit Graph, providing convenient and easy access to the graph and the new Commit Graph Details view.
+
+
+
+Views include:
+
+- Commit Graph
+- Commit Graph Details
+
+_Pro tip: You can toggle the Commit Graph between Panel and Editor layouts by clicking the "cog" icon on the upper right corner of the Graph view._
+_Pro tip 2: When the Commit Graph is in the Panel Layout, you can quickly toggle it via the new **Toggle Commit Graph** and **Toggle Maximized Commit Graph** commands._
+
+### Adopting the new views layout
+
+Unless you opt into the new layout, which we recommend, your existing views will stay where they are. You can opt in at any time from _Reset Views Layout_ in the Command Palette.
+
+## New Onboarding Experience
+
+The rebuilt welcome goes beyond quick settings and now includes overviews of important features as well as bringing better visibility to the views and functionality GitLens offers. Along the same lines, we consolidated and streamlined our walkthroughs.
+
+Also, we've made significant changes to the home view, with the help of your feedback, to refocus on quick access and discovery of many GitLens features.
+
+## ☁️ GitKraken Workspaces
+
+GitKraken Workspaces are a convenient way to group and manage multiple repositories. Cloud workspaces store the metadata of the grouped repositories and can be accessed across machines and GitKraken products. They can easily be imported into or created from VS Code workspaces.
+
+
+
+Please note that while using cloud workspaces requires a free account, shared cloud workspaces, which are shared between GitKraken organizations and teams, require a trial or plan. Shared Workspaces functionality is coming soon to GitLens.
+
+Workspaces can be accessed in the new GitKraken Workspaces view in the GitLens side bar.
+
+## Commit Graph Enhancements `PRO`
+
+We’ve greatly improved the ease of access to the Commit Graph as well as additional change information and easy-to-use customization options.
+
+### New Home in (Bottom) Panel
+
+The Commit Graph has moved into the (bottom) panel, providing convenient and persistent access to the graph and its details. If you prefer the Graph in the editor area, you can toggle between Panel and Editor layouts by clicking the "cog" icon on the upper right corner of the Graph view.
+
+### Minimap and Markers
+
+The Minimap which shows an overview of commit activity, previously an experimental feature, is now on by default. You can now toggle between 'lines changed' and 'commits' in the minimap display.
+
+With both the Minimap and the Commit Graph scrollbar, you can toggle specific markers on and off, including local branch, remote branch, stash, and tag markers. For the minimap, use the split minimap button, and for the scrollbar use the `Scroll Markers` submenu from the "cog" icon at the top of the scrollbar.
+
+### New Column and Column Layout
+
+The _Changes_ column, which shows the size of commit changes, is now visible by default. The column now also includes a count of the changed files, helping you quickly grasp the scale of each change.
+
+Reset your columns between the _Default_ and the new _Compact_ set via the context menu on the graph column headers, making it easy to toggle into a more minimal experience.
+
+### 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 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
+ - 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
+- Adds an all-new _GitKraken Workspaces_ ☁️ feature as a side bar view, supporting interaction with local and cloud GitKraken workspaces, lists of repositories tied to your account.
+ - Create, view, and manage repositories on GitKraken cloud workspaces, which are available with a GitKraken account across the range of GitKraken products
+ - Automatically or manually link repositories in GitKraken cloud workspaces to matching repositories on your machine
+ - Quickly create a GitKraken cloud workspace from the repositories in your current window
+ - 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
+ - (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
+ - Adds two new options to the graph header context menu
+ - `Reset Columns to Default Layout` - resets column widths, ordering, visibility, and graph column mode to default settings
+ - `Reset Columns to Compact Layout` - resets column widths, ordering, visibility, and graph column mode to compact settings
+ - Adds a _Toggle Commit Graph_ command to quickly toggle the graph on and off (requires the _Panel_ layout)
+ - Adds a _Toggle Maximized Commit Graph_ command to maximize and restore the graph for a quick full screen experience (requires the _Panel_ layout)
+ - Enables the _Minimap_ by default, as its no longer experimental, to provide a quick overview of of commit activity above the graph
+ - Adds ability to toggle between showing commits vs lines changed in the minimap (note: choosing lines changed requires more computation)
+ - Adds a legend and quick toggles for the markers shown on the minimap
+ - Defers the loading of the minimap to avoid impacting graph performance and adds a loading progress indicator
+ - Adds a `gitlens.graph.minimap.enabled` setting to specify whether to show the minimap
+ - Adds a `gitlens.graph.minimap.dataType` setting to specify whether to show commits or lines changed in the minimap
+ - Adds a `gitlens.graph.minimap.additionalTypes` setting to specify additional markers to show on the minimap
+ - Makes the _Changes_ column visible by default (previously hidden)
+ - Defers the loading of the _Changes_ column to avoid impacting graph performance and adds a loading progress indicator to the column header
+ - Adds a changed file count in addition to the changed lines visualization
+ - Improves the rendering of the changed line visualization and adds extra width to the bar for outlier changes so that they stand out a bit more
+ - Adds an _Open Repo on Remote_ button to left of the repo name in the graph header
+ - Improves contextual help on the search input as you type
+ - Improves tooltips on _Branch/Tag_ icons to be more uniform and descriptive
+ - Adds new context menu options to the _Commit Graph Settings_ (cog, above the scrollbar) to toggle which scroll marker to show
+ - Improves alignment of scroll markers on the scrollbar, and adds a gap between the last column and the scrollbar
+- 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.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)
+- 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 loading progress indicator
+- Adds _Reveal in File Explorer_ command to repositories
+- Adds _Copy SHA_ command to stashes
+- Adds new icons for virtual repositories
+
+### Changed
+
+- Changes header on _GitLens Settings_ to be consistent with the new Welcome experience
+- Reduces the visual noise of currently inaccessible `PRO` features in the side bars
+- Performance: Improves rendering of large commits on the _Commit Details_ view
+- Performance: Defers possibly duplicate repo scans at startup and waits until repo discovery is complete before attempting to find other repos
+- Security: Disables Git access in Restricted Mode (untrusted)
+- Security: Avoids dynamic execution in string interpolation
+
+### 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 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
+- Fixes an issue where _Branch / Tag_ items on the _Commit Graph_ sometimes wouldn't expand on hover
+- Fixes an issue where some command were showing up on unsupported schemes
+- Fixes an issue where the file/line history views could break because of malformed URIs
+
+
+
+## Version 13.6
+
+### Thursday, May 11, 2023
+
+GitLens 13.6 brings a range of enhancements and additions to the Commit Graph and refinements to our context menus. We've made improvements to the layout, condensing author names and column titles into avatars and icons when sized to minimums, and added flexibility of rearranging and moving columns as desired. This allows for a more streamlined and personalized GitLens experience. We have also updated the Commit Graph's toolbar to dynamically show a Push or Pull action, depending on a branch's state in relation to its upstream remote.
+
+
+
+## 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.
+
+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.
+
+### Commit Graph Enhancements `PRO`
+
+We’ve made it easier to customize your Commit Graph experience as well as improvements for better readability when in compact layouts.
+
+#### Compact Graph Improvements
+
+
+
+Previously unmovable columns within the Commit Graph can now be rearranged and customized according to your preferences. This flexibility enables you to arrange the columns in a way that best suits their workflow and priorities.
+
+In addition, we have implemented a more compact layout by removing the commit icon when avatars are hidden. This optimization maximizes the utilization of screen space and results in a cleaner and more streamlined visual representation.
+
+Moreover, the Author column now displays avatars instead of text when sized to its minimum width. That combined with the compact layout for the Graph column provide a nice compact experience with no loss of fidelity.
+
+#### Column Headers
+
+
+
+Commit Graph column headers have received dynamic behavior for enhanced readability. When the Commit Graph columns are compacted, the column headers seamlessly switch from displaying text to icons. This adaptation ensures that crucial information remains visible, even in constrained display settings.
+
+### Stash Improvements
+
+We've added the ability to rename stashes. If you are like me and often stash changes in a rush with very poor names, e.g. "wip" and then kick yourself later for not providing a more descriptive name, the this feature is for you. You can now rename any stash at any time.
+
+You can now search within stashes using the Commit Graph, the Search & Compare view, or the Search Commits command. This improvement facilitates efficient navigation and retrieval of specific stash entries.
+
+### Added
+
+- 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 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
+- Adds the ability to search stashes when using the commit search via the _Commit Graph_, _Search & Compare_ view, or the _Search Commits_ command
+- Adds an _Open Visual File History_ command to the new _File History_ submenu on existing context menus
+- Allows the _Repositories_ view for virtual repositories
+- Honors the `git.repositoryScanIgnoredFolders` VS Code setting
+- Adds _Share_, _Open Changes_, and _Open on Remote (Web)_ submenus to the new editor line numbers (gutter) context menu
+- Adds an _Open Line Commit Details_ command to the _Open Changes_ submenus on editor context menus
+- Adds an _Open Changes_ submenu to the row context menu on the _Commit Graph_
+
+### Changed
+
+- Refines and reorders many of the GitLens context menus and additions to VS Code context menus
+ - Moves _Copy Remote \* URL_ commands from the _Copy As_ submenu into the _Share_ submenu in GitLens views
+ - Adds a _Share_ submenu to Source Control items
+ - Moves _Copy SHA_ and _Copy Message_ commands on commits from the _Copy As_ submenu into the root of the context menu
+ - Moves _Copy Relative Path_ command on files from the _Copy As_ submenu into the root of the context menu
+ - Moves file history commands into a _File History_ submenu
+ - Moves _Open \* on Remote_ commands into _Open on Remote (Web)_ submenu
+ - Renames the _Commit Changes_ submenu to _Open Changes_
+ - Renames _Show Commit_ command to _Quick Show Commit_ and _Show Line Commit_ command to _Quick Show Line Commit_ for better clarity as it opens a quick pick menu
+- Changes the file icons shown in many GitLens views to use the file type's theme icon (by default) rather than the status icon
+ - Adds a `gitlens.views.commits.files.icon` setting to specify how the _Commits_ view will display file icons
+ - Adds a `gitlens.views.repositories.files.icon` setting to specify how the _Repositories_ view will display file icons
+ - Adds a `gitlens.views.branches.files.icon` setting to specify how the _Branches_ view will display file icons
+ - Adds a `gitlens.views.remotes.files.icon` setting to specify how the _Remotes_ view will display file icons
+ - Adds a `gitlens.views.stashes.files.icon` setting to specify how the _Stashes_ view will display file icons
+ - Adds a `gitlens.views.tags.files.icon` setting to specify how the _Tags_ view will display file icons
+ - Adds a `gitlens.views.worktrees.files.icon` setting to specify how the _Worktrees_ view will display file icons
+ - Adds a `gitlens.views.contributors.files.icon` setting to specify how the _Contributors_ view will display file icons
+ - 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)
+
+### 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 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
+- Fixes getting the oldest unpushed commit when there is more than 1 remote
+- Fixes an issue with the quick input on the _Git Command Palette_ unexpectedly going back to the previous step
+- Fixes GitLens access tooltip not being visible when hovering in the _Commit Graph_
+
+### 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)
+
+
+
+## Version 13.5
+
+### Thursday, Apr 6, 2023
+
+With 13.5, we've added the ability to switch to an alternate panel layout for the Commit Graph, which moves the Commit Graph into the bottom panel and adds a new Commit Graph Details view alongside on the right, for more convenient and persistent access. You can now also switch to a compact layout for the Graph column and shrink the Branch / Tag column to a single icon to reduce the space and allow you to focus on what you deem most important. You can now take action on your pull requests in the Focus View, with the new ability to create or switch branches or worktrees. We've also heard your feedback that the Commit Details view pinning was confusing and hard to work with, so 13.5 includes many improvements to make that experience better. We've also continued our quest to reduce the size and improve performance of GitLens and have shaved another ~7% off the GitLens bundle.
+
+
+
+### Commit Graph Layouts `PRO`
+
+
+
+The new panel layout brings even more flexibility and customization options to GitLens. While using the panel layout, GitLens moves the Commit Graph into the bottom panel and adds a new Commit Graph Details view alongside on the right. If the layout in the bottom panel doesn't suit your needs you can move the Commit Graph around to other locations (side bar, secondary side bar, etc) to suit your preferences. Whether you prefer to have the Commit Graph in the editor or in a separate panel, GitLens makes it easy to switch and find the layout that works best for you.
+
+
+
+To switch to the panel layout, simply click on the Commit Graph settings cog located at the top right of the Commit Graph. From there, select the "Switch Commit Graph to Panel Layout" option, and if you want to switch back follow the same steps and choose "Switch Commit Graph to Editor Layout".
+
+#### Compact Graph Column Layout
+
+
+
+With the new compact Graph column layout, GitLens provides a more streamlined and compact layout to reduce the space required to visualize the commit history and branch relationships.
+
+To enable the new compact Graph Column layout, right click on the Graph column header, and select the "Compact Graph Column Layout" option. If you want to switch back follow the same steps and choose "Default Graph Column Layout".
+
+#### Pull Requests on Local Branches
+
+You can now see pull requests (PRs) for your local branch upstreams directly on the local branches themselves. You no longer have to hunt for the local branch's upstream on the Commit Graph to see the associated PR.
+
+#### Publish Local Branches from Commit Graph
+
+Publishing local branches directly from the Commit Graph is a nice productivity boost. You can quickly and easily publish your local changes without having to switch to the Branches view or use the command line.
+
+### Focus View Pull Request Actions `PRO`
+
+
+
+The Focus View is no longer read-only! We've introduced new actions within Focus View, aimed at enhancing your workflow and productivity. You can now easily create a branch or worktree, or switch/open an existing one, for a PR directly from the Focus View page, streamlining the process of reviewing or contributing to pull requests. As a quick worktree refresher, creating a worktree from the PR will let you review or contribute to multiple PRs simultaneously without affecting your current branch and working tree.
+
+### Commit Details Interaction Improvements
+
+
+
+We've heard your feedback on the Commit Details view and the confusion and difficulty with using the pinning feature. We updated the visual appearance of the pinned state, so its easier to know when Commit Details is pinned. Additionally, we've introduced navigation controls that enable you to move back and forth through the commits you've recently viewed, helping to avoid losing context as you navigate through your code.
+
+### Thank you to our contributors
+
+Shout-out to all of our awesome contributors for this release!
+
+- 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 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)
+ - 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)
+ - Lowers the minimum width of the "Branch / Tag" column
+- Adds actions to _Focus View_ Pull Requests
+ - Switch to or create a local branch
+ - Create or open a worktree from the branch
+- Adds a _Generate Commit Message (Experimental)..._ command to the SCM context menus
+
+### Changed
+
+- 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)
+- 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)
+
+### 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 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
+
+
+
+## Version 13.4
+
+### Thursday, Mar 16, 2023
+
+With 13.4, we've introduced an experimental new AI feature to assist with writing commit messages, improved GitLens performance by reducing its size, made improvements to the `PRO` Commit Graph, and accepted community contributions as well as many bug fixes from community feedback.
+
+
+
+### AI-Generated Commit Messages (Experimental)
+
+
+
+We’ve introduced a new experimental feature to assist with writing commit messages by leveraging OpenAI. To start, stage some changes you want to commit and generate a commit message for and then run the “Generate Commit Message (Experimental)” command from the Command Palette. From there you will be guided through the process of accepting to send the diff of your staged changes to OpenAI and the entry of your OpenAI key. Once completed, the generated commit message will be entered into the commit input box on the Source Control sidebar. You can also enter additional context about your changes in the commit box and those will also be sent to help generate a better message.
+
+Additionally, you can customize the `gitlens.experimental.generateCommitMessagePrompt` setting to control the prompt used to structure and format the generated commit message. You could have it structure commit messages in the conventional commit style, or you can have fun with it and make your commit messages in the style of a pirate, Shakespeare, etc.
+
+This is a very early peek into features and ideas that can leverage AI – look forward to much more in the near future!
+
+### GitLens Size Reduction
+
+Over the last couple releases we’ve made significant progress on optimizing the footprint of GitLens. We’ve focused a lot on the bundle sizes to allow for faster start-up times of both the extension itself and all of our webviews. These optimizations also help reduce our memory usage. We are continually looking for opportunities to optimize and reduce our footprint so look for more progress in the future!
+
+Here are some numbers:
+
+- GitLens desktop bundle has been reduced by ~37% from 1.91MB to 1.21MB
+- GitLens web bundle (for vscode.dev / github.dev) has been reduced by ~39% from 2.05MB to 1.24MB
+- GitLens Commit Graph webview has been reduced by ~27% from 1.03MB to 758KB and that is including the new minimap and rich scroll markers
+- GitLens Home view has been reduced by ~41% from 267KB to 160KB
+- GitLens Visual File History view has been reduced by ~9% from 508KB to 461KB
+
+### Commit Graph Enhancements `PRO`
+
+##### Upstream Tracking
+
+
+
+It's now possible to effortlessly keep track of upstreams of your local branches in the commit graph. The upstreams of visible local branches, along with their corresponding commit history, will be displayed in the graph even if other remote branches are filtered out from your settings.
+
+We've also revised the wording of the remote filter setting to "Hide Remote-only Branches.
+
+#### Graph Alignment
+
+
+
+The graph column is now more left-aligned, making it easier to read and follow the history of a branch at a glance.
+
+#### Branches and Tags on Remote Repositories
+
+
+
+You can now see the tips of your branches and tags in the Commit Graph on remote repositories! Previously, opening a remote repository in the graph would show only the current branch. Currently, we are still limited to only showing commits for the current branch, so the included branches and tags are ones pointing to commits in the current branch’s commit history.
+
+### Sunsetting GitLens Insiders (Replaced with Pre-release)
+
+
+
+We’ve deprecated the GitLens Insiders edition in favor of a Pre-release version which is directly supported inside VS Code and is much easier to opt-in to and out of. Existing users of GitLens Insiders should have been automatically migrated to the Pre-release version. The Pre-release version of GitLens is a nightly build of GitLens, just as the GitLens Insiders edition was.
+
+To opt-in to the Pre-release edition, select GitLens from the extensions sidebar and press “Switch to Pre-Release Version”.
+
+### Thank you to our contributors
+
+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))
+
+### 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 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
+- Adds the ability to see branches and tags on remote repositories (e.g. GitHub) on the _Commit Graph_
+ - Currently limited to only showing them for commits on the current branch, as we aren't yet able to show all commits on all branches
+
+### Changed
+
+- Improves the display of items in the _Commit Graph_
+ - When showing local branches, we now always display the upstream branches in the minimap, scrollbar markers, and graph rows
+ - When laying out lanes in the Graph column, we now bias to be left aligned when possible for an easier to read and compact graph visualization
+- Improves _Open Worktree for Pull Request via GitLens..._ command to use the qualified remote branch name, e.g. `owner/branch`, when creating the worktree
+- Removes Insiders edition in favor of the pre-release edition
+- Reduces the size of the GitLens bundle which improves startup time
+ - GitLens' extension bundle for desktop (node) is now ~24% smaller (1.58MB -> 1.21MB)
+ - GitLens' extension bundle for web (vscode.dev/github.dev) is now ~6% smaller (1.32MB -> 1.24MB)
+
+### 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 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.
+
+---
+
+
+
+## Version 13.3
+
+### Thursday, Feb 23, 2023
+
+Supercharge your Git game with GitLens 13.3: the latest update to help you master Git like a pro. With 13.3 we’re introducing Workspace Focus View, Deep Linking Support, and Commit Graph Improvements featuring the new (experimental) minimap and changes column.
+
+
+
+GitLens also just got a whole lot faster with the release of version 13.3! Thanks to some serious bundle slimming, the startup times have significantly improved.
+
+- GitLens' extension bundle for desktop (node) is now ~18% smaller
+- GitLens' extension bundle for web (vscode.dev/github.dev) is now ~37% smaller
+- GitLens' Commit Graph webview bundle is now ~31% smaller
+
+### Focus View (Preview) `PRO`
+
+
+
+With the preview of GitLens Focus View, you can streamline your workflow and prioritize your tasks with ease. The Focus View feature gives you a comprehensive list of all your most important work across all your GitHub repos. No more jumping back and forth between multiple pages or repos - GitLens Focus View makes it simple and efficient to keep track of and manage your work progress.
+
+The new Focus View will provide you with a summary of Pull Requests and Issues relevant to you for the repositories grouped in your Workspace.
+
+- My Pull Requests: shows all GitHub PRs opened by you, assigned to you, or awaiting your review
+- My Issues: shows all issues created by you, assigned to you, or that mention you.
+
+Instead of hunting for these pieces of information separately, you can get a holistic view of what you’re working on.
+
+\*_Note Focus View is currently in a Preview Only state, it is subject to change in the future._
+
+### Commit Graph improvements `PRO`
+
+#### Minimap (Experimental)
+
+
+
+Click the Toggle Minimap icon in the right corner of the Commit Graph top bar to toggle the Minimap on and off. As this is an experimental feature, it is off by default – and we would love to hear your feedback and suggestions.
+
+The idea behind the Minimap is to provide a whole new dimension to the Commit Graph. You can quickly see the activity of the repo, see HEAD/upstream, branches (local and remote), and easily jump to them.
+
+The green line showcases HEAD while search results are depicted by yellow lines. The highlighted region shows the Commit Graph area that is in view. Markers are arranged in two rows of stacked blocks:
+
+- 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).
+
+#### Changes column (lines added/deleted)
+
+
+
+Reduce time and effort required to navigate through code changes, with the changes column in GitLens. The changes column provides a visual representation of changes made to files in each commit, with green bars indicating added lines and red bars indicating deleted lines.
+
+This visual display allows you to quickly identify the extent of changes made to files across multiple commits, making it easier to pinpoint specific areas of code that have been modified.
+
+You can toggle the Change Column by right clicking the graph header and clicking "Show Changes".
+
+#### Scroll Markers (Rich scrollbar)
+
+
+
+Scroll Markers adds a rich layer of information to the Commit Graph scrollbar. Now you can quickly find and jump to checked-out branches, selected rows, search results, as well as important points such as HEAD and refs. Similar to Overview Ruler in VS Code, Scroll Markers provide a visual indicator on the scrollbar.
+
+Our intention with Scroll Markers is to save you time and effort by allowing you to quickly identify and jump to the relevant sections of your Git history. It's a powerful new addition to the Commit Graph to help streamline workflow.
+
+#### Branch upstream status
+
+
+
+The Commit Graph now shows the upstream status of local branches with an upstream. You'll be able to quickly identify when your local branch is out of sync with its upstream branch with the new indicator, which shows how many commits are ahead or behind your upstream branch.
+
+You can also double-click on the upstream indicator, to pull or push the pending commits to bring your local branch back in sync with its upstream. This makes it easy to keep track of upstream changes to your local branches and keep them up to date.
+
+#### Work In Progress Row improvements
+
+
+
+With the latest Work In Progress Row improvements, with a single right click, you can access the WIP contextual menu. Giving you access to a range of useful options, including Stash All Changes, Open Details, and Open Source Control. These features allow you to more effectively manage your WIP.
+
+### Deep linking support
+
+Deep linking provides you with the ability to easily share specific remote repositories, commits, branches, and tags by copying the link to your clipboard and pasting it into a Jira issue or a Slack conversation for example.
+
+The link will then open in the Commit Graph and can be used to quickly access and review relevant artifacts. With deep linking support, you can improve collaboration and communication by seamless sharing of important information related to your Git repos.
+
+### Added
+
+- Adds new _Commit Graph_ features and improvements
+ - Adds a new experimental minimap of commit activity to the _Commit Graph_
+ - Adds a new experimental _Changes_ column visualizing commit changes
+ - Adds markers to the _Commit Graph_ scroll area indicating the location of the selected row, search results, current branch, upstream, and more
+ - Adds the ability to show upstream (ahead/behind) status on local branches with an upstream
+ - Adds a double-click action on the status to pull (when behind) or push (when ahead) pending changes
+ - Adds context menu actions to _Push_, _Pull_, and _Fetch_ the local branch
+ - Adds a `gitlens.graph.showUpstreamStatus` setting to toggle upstream (ahead/behind) indicators on branches
+ - 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 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
+- Adds the ability to copy and share links directly to repositories, branches, commits, and tags in the _Commit Graph_
+ - Adds context menu actions to copy direct links in the _Share_ submenu
+- Improves the Worktree creation experience
+ - Adds a prompt after the worktree is created to choose how to open the worktree
+ - Adds a `worktrees.openAfterCreate` setting to specify how and when to open a worktree after it is created
+ - Ensures new worktrees are created from the "main" repo, if already in a worktree
+- Adds a new _remote_ command to the _Git Command Palette_ to add, prune, and remove remotes
+- Adds a _Open Worktree for Pull Request via GitLens..._ context menu command on pull requests in the _GitHub Pull Requests and Issues_ extension's views
+ - Opens an associated worktree, if one exists, otherwise it creates a new worktree for the pull request
+- Adds settings to control the format of commits in the GitLens views
+
+### Changed
+
+- Greatly reduces the size of many of GitLens' bundles which improves startup time
+ - GitLens' extension bundle for desktop (node) is now ~18% smaller
+ - GitLens' extension bundle for web (vscode.dev/github.dev) is now ~37% smaller
+ - GitLens' Commit Graph webview bundle is now ~31% smaller
+- Changes the _Contributors_ view to be shown by default on the _GitLens_ sidebar
+
+### Removed
+
+- 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 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
+
+---
+
+
+
+## Version 13.2
+
+### 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!
+
+
+
+### Filtering
+
+GitLens 13.2 introduces filtering , which allows you to display a subset of your graph’s information and helps you hone in on specific details of your graph that matter the most.
+
+
+
+#### Filtering Capabilities
+
+Use graph filtering in GitLens to get laser focused on the branch you're working on and its remote:
+
+- Only Show the Current Branch
+
+ - Display only the branch that you’re currently working on and it’s remote. In order to focus your attention on the things landing in this branch, and then quickly unfilter to "zoom" back out and see everything in flight.
+
+- Hide Remote Branches
+
+ - Hides commits from the graph view that are only on remote branches.
+
+- Hide Tags
+
+ - Hides all tags that point to commit rows.
+
+- Hide Stashes
+
+ - Hides all stash rows.
+
+- Dim Merge Commit Rows
+ - Deemphasizes merge commit rows.
+
+### Graph UX Improvements
+
+We've updated the user interface, so you can get to all your favorite features even faster. Now, you can access change repo, account status, and filtering from the top of the Commit Graph page.
+
+
+
+### Header Updates
+
+By merging the contextual information from the footer into the header, including the new Branch Picker and Fetch Action we’ve made it easier for you to manage your branches and work more effectively.
+
+
+
+- Branch Picker
+
+ - Save time, by easily selecting the branch you want from the drop down branch picker.
+
+- Fetch Action
+ - Easily keep your local repo up-to-date and in sync with the fetch action.
+
+### Shortcut Keys
+
+Using the new keyboard shortcuts, `SHIFT+UP` and `SHIFT+DOWN` on the Commit Graph helps you locate what you need more efficiently and effectively by staying within the branch and moving between graph rows. This can be particularly useful if you are working on a complex project with many branches.
+
+
+
+### Added
+
+- Adds many all-new _Commit Graph_ features and improvements
+ - Adds the ability to filter commits, branches, stashes, and tags
+ - Adds a new _Filter Graph_ dropdown button at the start of the search bar
+ - Adds ability to quickly switch between _Show All Local Branches_ and _Show Current Branch Only branch_ filtering options
+ - _Show All Local Branches_ — displays all local branches (default)
+ - _Show Current Branch Only_ — displays only the current branch and it's upstream remote (if exists and _Hide Remote Branches_ isn't enabled)
+ - Adds ability to hide all remote branches, stashes, and tags
+ - Adds the ability to dim (deemphasize) merge commits
+ - Adds a new header bar to provide quick access to common actions
+ - Shows the currently selected repository with the ability to switch repositories when clicked (if multiple repositories are open)
+ - Shows the current branch with the ability to switch branches when clicked
+ - Provides a fetch action which also shows the last fetched time
+ - Also moves GitLens Pro feature status and feedback links to the top right
+ - Adds new ability to reorder columns by dragging and dropping column headers (not all columns are reorderable)
+ - Adds new keyboard shortcuts
+ - Use `shift+down arrow` and `shift+up arrow` to move to the parent/child of the selected commit row
+ - Holding the `ctrl` key with a commit row selected will highlight rows for that commit's branch
+ - Adds new settings
+ - Adds a `gitlens.graph.dimMergeCommits` setting to specify whether to dim (deemphasize) merge commit rows
+ - Adds a `gitlens.graph.scrollRowPadding` setting to specify the number of rows from the edge at which the graph will scroll when using keyboard or search to change the selected row
+
+### Changed
+
+- In the _Commit Graph_, increases the time to highlight associated rows when hovering over a branch to 1s
+- Removes the status bar from the _Commit Graph_ as it was replaced by the new header bar
+
+### 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 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
+- Fixes graph issue with branches remaining hovered/extended when the mouse leaves the graph
+
+---
+
+
+
+## Version 13.1
+
+### 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).
+
+
+
+## Commit Graph Enhancements
+
+### Search History
+
+Find what you seek with ease! Quickly navigate through your search history by using the UP⇧ or DOWN⇩ arrow keys.
+
+
+
+### New Search Filter @me
+
+Want to see only your commits? Search For @me to highlight only your commits.
+
+
+
+## Faster Interactive Rebase Editor
+
+With GitLens 13.1, we overhauled the Interactive Rebase Editor. It is now dramatically faster, especially for large rebases. We also streamlined the user experience with a persistent header and footer to ensure you always have important context visible and can quickly start or abort the rebase. Also, anytime the commit author and committer are different, you will see both of their avatars.
+
+
+
+### Commit Details View Usage
+
+Need additional details to complete your rebase more efficiently? Now, as you navigate commits, we show the selected commit details in the Commit Details view.
+
+## Commit Details View Improvements
+
+### Custom Autolinks
+
+Custom and basic provider-based autolinks are now shown in the Autolinks section.
+
+### Customizable Settings
+
+You can now customize the Commit Details view from the GitLens Settings editor to personalize how it looks and behaves so you can focus on the most important details.
+
+
+
+## Terminal Links Can Use the Commit Details View
+
+Terminal Links for commits in VS Code’s integrated terminal now use the Commit Details view to provide rich details about the selected commit.
+
+## GitLens Home View Updates
+
+Keeping a home tidy is important! We’ve streamlined the Home view to make it even easier to get started with GitLens, learn about its features, and how to personalize your experience.
+
+
+
+## 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
+ {
+ "key": "ctrl+c",
+ "command": "gitlens.graph.copySha",
+ "when": "gitlens:webview:graph:focus && !gitlens:webview:graph:inputFocus"
+ }
+- Automatically selects the HEAD commit in the Commit Graph when switching branches
+- Improves performance of updating the Commit Graph when the repository changes
+- Improves performance by avoiding unnecessary updates to the Commit Details view when selection changes
+- 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 Interactive Rebase Editor performance and UX improvements
+ - Changes the header and footer to always be visible
+ - Shows the Commit Details view on commit selection
+ - Adds a gitlens.rebaseEditor.showDetailsView setting to specify when to show the Commit Details view for the selected row in the Interactive Rebase Editor
+ - 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)
+ - 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
+ - Improves performance by avoiding unnecessary updates
+ - Avoids "pinning" commits by default when opened from the Commit Graph, Visual File History, quick picks, etc
+ - Adds a Open in Commit Graph button even when showing uncommitted changes
+- Adds new sections and settings to the GitLens Interactive Settings
+ - Adds a new Commit Details view section
+ - Adds a new Terminal Links section
+ - Adds autolink configuration to the Hovers section
+- Adds a @me search filter to commit search in the Search & Compare view and quick pick
+- Adds product usage telemetry
+ - Honors the overall VS Code telemetry settings and add a gitlens.telemetry.enabled setting opt-out specifically for GitLens
+
+## 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)
+ - 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)
+ - 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 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
+- Fixes graph issue with merge commits not being hidden correctly in some cases
+- Fixes some graph issues with hover on branch/tag labels
+
+---
+
+
+
+## Version 13.0
+
+### Monday, October 17th, 2022
+
+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).
+
+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 - Now out of Preview! `PRO`
+
+We’re delighted to announce that the Commit Graph is out of Preview, and is full featured! This means you may now interact with the Commit Graph directly and take actions like:
+
+- Interact with branches, commits, tags and more with right-click context menus
+- Double click a branch to checkout a branch
+- Search and filter for commits
+- Get information about Pull Requests
+
+### Full context menu support
+
+Interact with your branches, commits, and more! Context menus are now available when you right click on any branch, tag, commit, or author in the Commit Graph. You may even interact with the Commit Graph column headers to the author, date or SHA columns. So much power!
+
+
+
+Context menu actions include but are not limited to:
+
+- Switch to Branch
+- Revert Commit
+- Switch to Commit
+- Create Branch
+- Merge
+- Rebase
+- Create Worktree
+- Create Pull Request
+
+### Rich commit search
+
+Find exactly what you are looking for with the rich search on the powerful new Commit Graph.
+
+Whether searching for a specific commit, message, author, a changed file or files, or even a specific code change, the Commit Graph will highlight matching results across your entire repository. Use shortcut keys or the up/down arrows on the search bar to navigate the search results; `F3` (also `Cmd+G` on macOS) goes to the next result from your selection while `Shift+F3` ( also `Shift+Cmd+G` on macOS) goes to the previous. Additionally you can quickly jump to the first or last result, by holding `Shift` while clicking on the up/down arrows respectively – to make it easy to see when a file or change was introduced into the codebase.
+
+
+
+Once you type search filtering criteria, use the arrow icons to move through each result.
+
+
+
+### PR information in form of icon
+
+Wait, which branch has that PR?
+
+If connected to one of the rich integrations with GitHub or GitLab, the Commit Graph will display a PR icon for any branch currently in PR. Right-click on the PR icon to open the PR on the GitHub or GitLab, or copy the URL.
+
+
+
+### Hiding remotes, branches or tags
+
+Need to focus and have too many remotes or just want to curate how much is shown in your Commit Graph? Now you can hide entire remotes, or specific branches and tags. Hover over any branch or tag to access the “Hide” button or right-click to hide the whole remote, or just the local or remote branch, to help focus your Commit Graph.
+
+
+
+### All new home view
+
+It’s a homecoming! Our GitLens home view has a new look, with quick links to our Getting Started guides, Integrations, Trial info, and Feature spotlights.
+
+
+
+### List or tree view in Commit Details View
+
+The Commit Details View, which gives you contextual change info about your code, got a new toggle for List and Tree view.
+
+
+
+To open the Commit Details view, open the command palette using Cmd+Shift+P and type: Show Commit Details view or navigate to the Commit Details view in the Side Bar.
+
+# Change Log
+
+### Added
+
+- `PRO` All GitLens Pro features on public and local repos are now available to everyone -- no account required!
+ - We want to bring the power of GitLens Pro features to more people without any gates.
+- `PRO` Commit Graph is out of preview!
+ - Rich search features to find exactly what you're looking for:
+ - Powerful filters to search by commit, message, author, a changed file or files, or even a specific code change
+ - Searches look at ALL commits in a repository, not just what's shown in the graph
+ - PR support for connected rich integrations (GitHub/GitLab)
+ - Contextual right-click menus with popular actions for commits, branches, tags, and authors
+ - Personalization of your graph experience
+ - Show and hide branches and columns
+ - Settings UI for easy fine-grain control over advanced settings
+- Adds `View as Tree` option for changed files in the _Commit Details_ view
+- Adds an `Open in Commit Graph` action to the hovers and commit quick pick menus
+
+### Changed
+
+- Updates the `Home View` with all new design and content
+- Changes the `Show Commit` action in the hovers to `Show Details` and opens the _Commit Details_ view
+
+### 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 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
+- Fixes Graph not showing account banners when access is not allowed and trial banners were previously dismissed
+
+---
+
+
+
+## Version 12.2
+
+### Tuesday, August 30th, 2022
+
+The new Commit Graph 🎨 in GitLens 12.2 will fix all your commitment problems...in your code 🥁 👩💻
+
+
+
+## Commit Graph - Preview `PRO`
+
+Users may now view the Commit Graph of their repository through GitLens.
+
+This beloved feature from GitKraken Desktop helps visualize your repo commit history and give you information about branches, commits, and collaborators all in one view — making it easier to see contributions and help you make faster, more informed decisions.
+
+
+
+To open the Commit Graph, open the command palette using the keyboard shortcut Cmd Shift P and type `Show Commit Graph`.
+
+
+
+This will open a new tab and render your current repo’s commit history, where you may scroll through your history and resize any of the columns widths.
+
+You may also access the Commit Graph by clicking this graph icon from the Source Control view in the Sidebar or Status Bar.
+
+
+
+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.
+
+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
+
+GitLens 12.2 also ships with a `Commit Details View`, which gives you contextual change info about your code.
+
+
+
+To open the `Commit Details View`, open the command palette using Cmd Shift P and this time type: `Show Commit Details View` or navigate to the Commit Details View in the Sidebar.
+
+
+
+The `Commit Details View` updates as you move your cursor throughout the file with information about the commit that modified that line of code. Get quick information about the commit author, commit ID, links to Pull Requests, files modified in the commit, and more.
+
+Click on a file to open the diff, and see what changed. You may also hover over the file name to access options like Open File, Open Changes with Working File, and Open Remote.
+
+## GitHub Enterprise Integration `PRO`
+
+Next, GitLens Pro now offers a richer integration with GitHub Enterprise.
+
+Once authenticated, GitLens will enrich GitHub autolinks in the hovers. You’ll see your GitHub Enterprise avatar, links to related pull requests, along with a footnote of the pull request or issue details.
+
+
+
+You’ll see similar details from the Sidebar views for any commit or branch associated with a pull request or issue.
+
+## Single Sign On `PRO`
+
+Single Sign On is here, providing GitLens Pro users with a more secure sign in method!
+
+### Requirements and configuration
+
+Your GitKraken account may now initiate an Oauth authentication flow with the following supported Identity Providers (IdPs):
+
+- Azure Active Directory
+- Okta
+- Google Identity Platform
+- Ping Identity
+
+
+
+Please note that your IdP will first need to be configured before setting up the connection in your GitKraken account. For assistance, please contact your IdP administrator or consult the IdP documentation for help.
+
+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/)
+
+### Signing in with SSO
+
+GitLens Pro users should see a new option to Sign in with SSO from the login screen.
+
+
+
+After clicking `Sign in with SSO`, the SSO form will open and ask for an email address to use for SSO login. The app will then check the email and determine whether the email address belongs to a single IdP for SSO. When the email address is successfully identified, the user will be taken to that IdP to login.
+
+Once authenticated, the user may use GitLens Pro
+
+## More improvements
+
+### Stash naming defaults
+
+When applying or popping a stash, GitLens will default the commit message input to the stash message.
+
+
+
+And when stashing changes, the stash name will now default to any entry in the commit message input.
+
+### Stats in comparisons
+
+There are now stats about additions & deletions in files nodes in comparisons. To get these stats, navigate to the `Search & Compare` view in the Sidebar and create a comparison between commits.
+
+
+
+### Search for text in Interactive Rebase Editor
+
+And users may now search for text on the `Interactive Rebase Editor` using Ctrl F.
+
+
+
+## Change Log
+
+### Added
+
+- 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 associated pull request to line annotations and hovers
+ 
+ - Adds associated pull request to status bar blame
+ 
+ - 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)
+ - 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 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 (/)
+- Adds owner avatars to remotes in the _Remotes_ view for GitHub remotes
+
+### Changed
+
+- Greatly improves performance of many view interactions when connected to a rich integration and pull request details are enabled, including:
+ - Showing and refreshing the _Commits_ view
+ - Expanding commits, branches, and worktrees
+- Remembers chosen filter on files nodes in comparisons when refreshing
+- 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))
+
+### 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 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-))
diff --git a/gitlens/GL-Visual-File-History.md b/gitlens/GL-Visual-File-History.md
index aabeb2a..d9e3f88 100644
--- a/gitlens/GL-Visual-File-History.md
+++ b/gitlens/GL-Visual-File-History.md
@@ -1,30 +1,63 @@
---
-
-title: Gitlens Visual File History
-description: Learn about Visual File History in Gitlens
+title: GitLens Visual File History
+description: Use GitLens Visual File History to explore file evolution, changes, and authorship over time in VS Code.
taxonomy:
category: gitlens
---
+Last updated: August 2025
-The Visual File History allows you to quickly see the evolution of a file, including when changes were made, how large they were, and who made them.
+## Visual File History
-To access the Visual File History view, open the GitLens Inspect sidebar. Once the sidebar is open, the view will be available. Alternatively, you can open Visual File History from the Command Palette by using (`cmd/ctrl + shift + P`) > GitLens: Show Visual File History View.
+The GitLens **Visual File History** shows how a file has evolved, including when changes were made, the size of those changes, and who made them.
-
+---
-Authors who have contributed changes to the file are on the left y-axis to create a swim-lane of their commits over time (the x-axis). Commit are plotted as color-coded (per-author) bubbles, whose size represents the relative magnitude of the changes.
+### Open Visual File History
-Additionally, each commit's additions and deletions are visualized as color-coded, stacked, vertical bars, whose height represents the number of affected lines (right y-axis). Added lines are shown in green, while deleted lines are red.
+You can open the Visual File History view in two ways:
+1. From the **GitLens Inspect** sidebar.
+ - Open the sidebar, then select the **Visual File History** view.
+2. From the **Command Palette**:
+ - macOS: Cmd + Shift + P
+ - Windows/Linux: Ctrl + Shift + P
+ - Search for **GitLens: Show Visual File History View**.
-Gain additional insights on hover.
+
+ 
+---
-Community plan is restricted to Public and Local Repositories only.
-
+ The Community plan supports Public and Local repositories only. A paid GitLens subscription is required for private repositories.
+
+Last updated: August 2025
+
+## Worktrees View
+
+
+ 
+
+### Commit Composer: Branch Recomposition
+
+Commit Composer now lets you clean up and reorganize commits on existing branches, making it perfect for preparing pull requests or refining your commit history before pushing.
+
+
+
+#### Recompose Entire Branches
+
+Open Commit Composer from any branch in the Commit Graph (or anywhere branches appear in GitLens) to inspect and reorganize its commits. The composer creates draft commits you can review before applying changes to your repository.
+
+**Auto-Recompose with AI**: Let AI analyze your branch and restructure commits into logical, well-documented units. Choose your preferred model and provide custom instructions to match your team's conventions. (Pro tip: Set default instructions in the "Generate Commits: Custom Instructions" setting to save time.)
+
+**Manual Control**: Review AI suggestions, regenerate specific commit messages, or manually edit messages and change organization. The composer gives you complete flexibility to craft the commit story that works best.
+
+
+
+#### Enhanced Composer Capabilities
+
+Commit Composer now handles edge cases that previously blocked composition:
+
+- **Untracked files**: Working changes now include untracked files, so all modifications can be composed together
+- **New repositories**: Compose your initial commits even before a base commit exists
+- **Performance boost**: Significantly faster rendering when working with changes across many files
+
+### Commit Graph Enhancements
+
+#### File History Visualization
+
+The Commit Graph now visualizes complete file histories, making it easy to understand how specific files evolved over time.
+
+Right-click any file in your IDE and select "File History > Open File History in Commit Graph" to filter the graph to commits that modified that file. Each commit displays the file's changes in the Commit Details panel, giving you a focused view of how the file developed.
+
+You can also manually filter using `file:"path/filename"` syntax.
+
+
+
+#### Search Enhancements
+
+**Reference and Range Searches**: The new `ref:` operator lets you search by references or commit ranges. Natural language search leverages this automatically, so queries like "show me all commits on debt/graph-selection-jump that aren't on main" or "commits after tag v17.6.0" work seamlessly.
+
+**Tip Filtering**: New `is:tip` and `type:tip` operators isolate branch and tag tips, helping you quickly identify meaningful entry points in your history without visual scanning.
+
+**Search History**: Arrow up/down through previous search queries to quickly revisit recent searches.
+
+
+
+#### Solo Branches and Tags
+
+Focus on a single branch or tag with the new "Solo" action, which automatically hides all other references using the `ref:` filter operator.
+
+#### Workflow Improvements
+
+- **Auto-select WIP**: The WIP row automatically selects when you have working changes, keeping your focus on current work
+- **Enhanced WIP row**: The WIP row now shows the number of changed files and lines, providing more context at a glance.
+- **Focused row preservation**: The graph maintains your selected row even when new data refreshes the view. This solved an annoying issue that resulted in losing context in the graph during updates.
+
+#### Commit Details
+
+**Commit Reachability**: Commit Details now display which branches and tags contain a specific commit, giving you instant visibility into how changes have propagated across your repository.
+
+
+
+**File List Actions**: Context menus now provide the full range of file operations you expect from other IDE file lists—opening files, viewing history, applying changes, and more—directly from Commit Details.
+
+
+
+----
+
+### 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 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 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 _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 _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))
+ - 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 `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 `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))
+ - 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 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 `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
+- Adds "inline" multiline commit message support to the _Commit Graph_
+- Adds _Next Change_ and _Previous Change_ navigation commands to the editor toolbar when the _Changes Annotations_ are active
+- Adds keybinding support for copy actions (Ctrl+C / Cmd+C) in the _Launchpad_ view
+- Adds _Quick Show Commit_ (`gitlens.showQuickCommitDetails`) command to the Command Palette
+
+### Changed
+
+- Improves performance and reduces overhead in many areas
+ - Faster/less intensive detection of 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))
+- 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 missing layout commands in view menus
+- Fixes stage/unstage failures with large file set by adding batching
+- Fixes copying untracked files as a patch
+- Fixes an issue where the "hidden references" control on the _Commit Graph_ could still receive focus
+- Fixes issues with inline versus block Markdown rendering
+- Fixes inconsistencies in the Work-in-Progress (WIP) statistics
+- Fixes an issue where the "visible day range" on the _Commit Graph_ minimap were not updating
+- Fixes showing overview mode when selecting a Work-in-Progress (WIP) row
+- Fixes path issues in untracked files and tree file parsing
+- Fixes action color on the merge/rebase status component
+- Fixes the copy shortcut key on grouped views
+- Fixes issue to ensure the immediate firing of repository close events to avoid potential deadlock issues
+
+
+
+## Version 17.6
+
+#### Tuesday, October 7, 2025
+
+GitLens 17.6 adds support for Claude Sonnet 4.5, delivers significant performance improvements when working with large changesets, and enhances Linear integration support.
+
+
+
+### Claude Sonnet 4.5 AI Model Support
+
+GitLens now supports Anthropic's Claude Sonnet 4.5 model for all AI-powered features, including:
+
+- Commit and message generation in the _Commit Composer_
+- Code explanations and summaries
+- Pull request descriptions
+- Changelog generation
+
+This latest model brings improved reasoning capabilities and more accurate, context-aware suggestions to your development workflow.
+
+### Large Changeset Performance Improvements
+
+Working with large changesets and complex commit histories is now significantly faster and more responsive across multiple GitLens views.
+
+#### Inspect and Graph Details Views
+
+The _Inspect_ and _Graph Details_ views now feature dramatically improved performance through virtualized tree rendering. This enhancement makes working with repositories with large commits significantly faster and more responsive.
+
+Along with the performance boost, keyboard navigation has been enhanced with comprehensive support for:
+
+- **Arrow keys** for navigating through items
+- **Home/End** keys for jumping to the first or last item
+- **Enter/Space** for selecting and activating items
+- **Tab** for moving between sections
+- **Type-ahead search** for quickly finding specific items
+
+These improvements make it easier to navigate and explore your repository's history, especially when working with a large number of files or reviewing detailed commit information.
+
+#### Commit Composer `PREVIEW`
+
+The _Commit Composer_ now handles large file diffs more efficiently, preventing performance degradation when working with substantial changes. This ensures a smooth composition experience regardless of the size of your working changes.
+
+### Linear Integration Enhancements `PRO`
+
+Introduced in GitLens 17.5, Linear issue trackering continues to evolve with autolinks for branches in Home and the Commit Graph. Along with some reliability and functionality improvements, these enhancements provide a more seamless experience when working with Linear issues in your GitLens workflows.
+
+
+### Thank you to our contributors
+
+Shout-out to our awesome contributors for this release!
+
+- Noritaka Kobayashi ([@noritaka1166](https://github.com/noritaka1166))
+
+---
+
+### Added
+
+- Adds support for Claude Sonnet 4.5 for GitLens' AI features
+
+### 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))
+ - 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))
+
+### 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 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))
+
+
+
+
+## Version 17.5
+
+#### Tuesday, September 23, 2025
+
+GitLens 17.5 introduces the GitKraken MCP for Git and integration enhanced AI chat workflows, expands integration support with Linear, and launches a new Student Plan for GitHub Student Developer Pack members.
+
+
+
+### GitKraken MCP: Git Intelligence for AI Chat
+
+GitLens 17.5 bundles the GitKraken Model Context Protocol (MCP) server, bringing Git and repository intelligence directly to AI chat interfaces in VS Code, Cursor, Windsurf, and other compatible IDEs.
+
+The GitKraken MCP transforms how you interact with Git through AI by surfacing repository information, issue tracking data, and pull request details—the same rich context that GitLens has provided in UI form for years—now accessible through conversational AI.
+
+
+
+
+
+#### Enhanced Developer Workflows
+
+The MCP enables powerful use cases through AI chat:
+
+**Issue and Branch Management**
+- List issues: *"List all open Jira issues assigned to me"*
+ - GitKraken MCP fetches and displays issue details from your connected trackers
+- Start work on an issue: *"Start work on Jira issue PROJ-123"*
+ - GitKraken MCP pulls issue details, stashes changes if needed, and creates a feature branch
+
+**Pull Request Assistance**
+- Create a pull request: *"Create a pull request for my current branch"*
+ - GitKraken MCP gathers branch diffs, generates a PR title and description, and opens the PR in your connected Git provider
+
+**Debug and Understand History**
+- 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/).
+
+#### 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/).
+
+We're just scratching the surface of what's possible with the GitKraken MCP. Future releases will expand capabilities, integrations, and IDE support.
+
+### Linear Integration `PRO`
+
+Teams using Linear for issue tracking can now connect to Linear and bring issue information directly into GitLens workflows.
+
+- **Start work seamlessly**: Create branches or worktrees directly from Linear issues
+- **Rich contextual information**: View Linear issue details in the Commit Graph, Home View, blame annotations, and Commit Details
+
+This integration follows the same pattern as GitLens' other issue tracker connections, providing a unified experience whether you're using GitHub Issues, Jira, or Linear.
+
+### Student Plan
+
+GitKraken now offers a Student Plan for members of the GitHub Student Developer Pack! This plan provides students with:
+
+- **Private repository access**: Use paid GitLens features like the Commit Graph and Visual File History on private repos
+- **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).
+
+---
+
+### Added
+
+- 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)
+
+### Changed
+
+- Improves AI provider/model fallback handling for better reliability
+
+### Fixed
+
+- Fixes connection flow when multiple integrations need to be connected
+
+
+
+## Version 17.4
+
+#### Thursday, August 21, 2025
+
+GitLens 17.4 transforms the Commit Composer experience with a powerful new composing view, introduces Azure DevOps Server integration for Pro users, enhances AI explanations, adds support for new AI models like GPT-5, and delivers significant improvements to worktree workflows.
+
+
+
+### New Commit Composer View `PREVIEW`
+
+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.
+
+
+
+#### Interactive Draft Commits
+
+When composing commits, GitLens now creates "draft" commits that you can review, modify, and refine before applying them to your repository. This new workflow lets you:
+
+- **Preview before committing**: See exactly what will be committed before it touches your repository
+- **Switch Models**: Try composition with different AI models
+- **Guide the AI**: Provide custom instructions to match your team's conventions and preferences
+- **Iterate and refine**: Regenerate individual messages or entire commit compositions
+- **Review and edit**: Manually tweak any commit message or approach
+
+
+
+You can launch the new Commit Composer view from several places in GitLens:
+
+- **GitLens commit details view**
+- **Context menu on the WIP row** in the GitLens Commit Graph
+- **Active branch card** in the GitLens Home View
+- **✨ icon in the SCM view header**
+- **Command palette**: Search for "Compose Commits"
+
+
+
+
+The foundation is now in place for even more powerful composition features in future releases, including intuitive drag-and-drop functionality for moving lines and hunks between commits, creating new draft commits on the fly, and reordering commit sequences.
+
+Whether you prefer to let AI handle the heavy lifting or want granular control over every detail, Commit Composer provides the flexibility to create well-structured commit histories that make code reviews more effective and repository history easier to understand.
+
+### Azure DevOps Server Integration `PRO`
+
+GitLens Pro now supports self-hosted Azure DevOps Server instances, bringing the same rich integration experience you know from cloud-hosted services to your on-premises environments.
+
+Connect your Azure DevOps Server to unlock:
+
+- **Streamlined issue workflows** - Start work on Azure issues by creating branches or worktrees directly from GitLens
+- **Rich blame and hover information** - View Azure issue and pull request details inline with your code
+- **Launchpad integration** - Monitor pull request blockers and review status from a unified view
+- **Native pull request creation** - Create Azure pull requests without leaving your IDE
+
+### New AI Model Support
+This release adds support for GPT-5 family (GPT-5, GPT-5 Mini, GPT-5 Nano), and Claude 4.1 Opus models
+
+### AI Explanation Improvements
+
+AI-powered explanations now provide immediate feedback with enhanced user experience improvements:
+
+- **Instant summary views** open immediately when generating explanations
+- **Clear progress indicators** show pending AI analysis status
+- **Streamlined presentation** focuses your attention on the generated content
+
+
+
+### Branch Upstream Management
+You can now easily modify the upstream for local branches in GitLens from places like the Branches view and Commit Graph.
+
+### 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:
+
+- **Repository filtering** - New header controls let you focus on specific repositories or worktrees
+- **Visual differentiation** - Improved icons help distinguish between repositories and worktrees
+- **Reduced interface noise** - Minimized flashing and blanking during worktree discovery
+- **Unified repository picker** - Visual grouping makes selecting repositories and worktrees more intuitive
+
+These enhancements work seamlessly with VS Code's native worktree support, providing a polished experience whether you're working with single repositories or complex multi-worktree setups.
+
+---
+
+### 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)
+ - 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
+ - Adds custom instruction support to guide AI output to match team conventions and preferences
+ - Adds integrated diff review for each proposed commit, and manual editing capabilities for any commit message or approach
+ - Adds manual commit composition support (no AI provider required for basic functionality)
+ - 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))
+ - 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 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))
+
+### 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))
+- 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))
+
+### 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))
+
## Version 17.3