<atitle="Learn more about GitLens"href="https://gitlens.amod.io"><imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/gitlens-logo-anybg.png"alt="GitLens Logo"/></a>
<atitle="Learn more about GitLens"href="https://gitlens.amod.io"><imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/gitlens-logo-anybg.png"alt="GitLens Logo"/></a>
</p>
> GitLens **supercharges** Git inside VS Code. It helps you to **visualize code authorship** at a glance via Git blame annotations and CodeLens, **seamlessly navigate and explore** Git repositories, **gain valuable insights** via rich visualizations and powerful comparison commands, and so much more.
@ -18,7 +18,7 @@
</p>
<palign="center">
<atitle="What's New in GitLens 12"href="https://gitkraken.com/blog/gitlens-12"><imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/whats-new-button.png"alt="Open What's New in GitLens 12"/></a>
<atitle="What's New in GitLens 12"href="https://gitkraken.com/blog/gitlens-12"><imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/whats-new-button.png"alt="Open What's New in GitLens 12"/></a>
<br/>
or read the <ahref="https://gitlens.amod.io/#whats-new">release notes</a>
</p>
@ -74,7 +74,7 @@ Access to premium features requires a free account for public repos and a paid a
## Visual File History view [#](#visual-file-history-view- 'Visual File History view')
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/visual-file-history-hover.png"alt="Visual File History view"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/visual-file-history-hover.png"alt="Visual File History view"/>
</p>
The Visual File History view allows you to quickly see the evolution of a file, including when changes were made, how large they were, and who made them.
@ -86,7 +86,7 @@ Additionally, each commit's additions and deletions are visualized as color-code
Worktrees allow you to easily work on different branches of a repository simultaneously. You can create multiple working trees, each of which can be opened in individual windows or all together in a single workspace.
@ -96,7 +96,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds an _Open Changes with Previous Revision_ command (`gitlens.diffWithPrevious`) to compare the current file or revision with the previous commit revision
@ -110,7 +110,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
## Current Line Blame [#](#current-line-blame- 'Current Line Blame')
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/current-line-blame.png"alt="Current Line Blame"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/current-line-blame.png"alt="Current Line Blame"/>
</p>
- Adds an unobtrusive, [customizable](#current-line-blame-settings- 'Jump to the Current Line Blame settings'), and [themable](#themable-colors- 'Jump to the Themable Colors'), **blame annotation** at the end of the current line
@ -120,7 +120,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds Git authorship **CodeLens** to the top of the file and on code blocks ([optional](#git-codelens-settings- 'Jump to the Git CodeLens settings'), on by default)
@ -145,7 +145,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
## Status Bar Blame [#](#status-bar-blame- 'Status Bar Blame')
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/status-bar.png"alt="Status Bar Blame"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/status-bar.png"alt="Status Bar Blame"/>
</p>
- Adds a [customizable](#status-bar-settings- 'Jump to the Status Bar Blame settings') **Git blame annotation** showing the commit and author who last modified the current line to the **status bar** ([optional](#status-bar-settings- 'Jump to the Status Bar Blame settings'), on by default)
@ -168,7 +168,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
### Current Line Hovers
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/hovers-current-line.png"alt="Current Line Hovers"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/hovers-current-line.png"alt="Current Line Hovers"/>
</p>
- Adds [customizable](#hover-settings- 'Jump to the Hover settings') Git blame hovers accessible over the current line
@ -176,7 +176,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
#### Details Hover
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/hovers-current-line-details.png"alt="Current Line Details Hover"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/hovers-current-line-details.png"alt="Current Line Details Hover"/>
</p>
- Adds a **details hover** annotation to the current line to show more commit details ([optional](#hover-settings- 'Jump to the Hover settings'), on by default)
@ -187,7 +187,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
#### Changes (diff) Hover
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/hovers-current-line-changes.png"alt="Current Line Changes (diff) Hover"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/hovers-current-line-changes.png"alt="Current Line Changes (diff) Hover"/>
</p>
- Adds a **changes (diff) hover** annotation to the current line to show the line's previous version ([optional](#hover-settings- 'Jump to the Hover settings'), on by default)
@ -197,7 +197,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds a **details hover** annotation to each line while annotating to show more commit details ([optional](#hover-settings- 'Jump to the Hover settings'), on by default)
@ -216,7 +216,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds a **changes (diff) hover** annotation to each line while annotating to show the line's previous version ([optional](#hover-settings- 'Jump to the Hover settings'), on by default)
@ -226,7 +226,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds on-demand, [customizable](#gutter-blame-settings- 'Jump to the Gutter Blame settings'), and [themable](#themable-colors- 'Jump to Themable Colors'), **gutter blame annotations** to show the commit and author who last modified each line of a file
@ -239,7 +239,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
- Adds an on-demand, [customizable](#gutter-changes-settings- 'Jump to the Gutter Changes settings') and [themable](#themable-colors- 'Jump to Themable Colors'), **gutter changes annotation** to highlight any local (unpublished) changes or lines changed by the most recent commit
@ -249,7 +249,7 @@ Worktrees allow you to easily work on different branches of a repository simulta
A [customizable](#commits-view-settings- 'Jump to the Commits view settings') view to visualize, explore, and manage Git commits
@ -294,9 +294,9 @@ The _Commits_ view lists all of the commits on the current branch, and additiona
- **Changes to pull from <remote>**— lists all of the commits waiting to be pulled when the current branch has commits that are waiting to be pulled from the upstream remote
- **Changes to push to <remote>**— lists of all the files changed in the unpublished commits when the current branch has (unpublished) commits that waiting to be pushed to the upstream remote
- **Merging into <branch>** or **Resolve conflicts before merging into <branch>**— lists any conflicted files. Conflicted files show comparisons with the common base of the current and incoming changes to aid in resolving the conflict by making it easier to see where changes originated
- **Rebasing <branch>** or **Resolve conflicts to continue rebasing <branch>**— shows the number of rebase steps left, the commit the rebase is paused at, and lists any conflicted files. Conflicted files show comparisons with the common base of the current and incoming changes to aid in resolving the conflict by making it easier to see where changes originated
A hidden by default, [customizable](#repositories-view-settings- 'Jump to the Repositories view settings') view to visualize, explore, and manage Git repositories
@ -345,7 +345,7 @@ The Repositories view lists opened Git repositories, and additionally provides,
### File History view [#](#file-history-view- 'File History view')
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/file-history-view.png"alt="File History view"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/file-history-view.png"alt="File History view"/>
</p>
A [customizable](#file-history-view-settings- 'Jump to the File History view settings') view to visualize, navigate, and explore the revision history of the current file or just the selected lines of the current file
@ -359,14 +359,14 @@ The file history view lists all of the commits that changed the current file on
- (file history only) a toggle to show commits from all branches rather than just from the current base branch or reference
- merge conflict status when applicable
- **Merge Changes**— show comparisons with the common base of the current and incoming changes to aid in resolving the conflict by making it easier to see where changes originated
### Line History view [#](#line-history-view- 'Line History view')
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/line-history-view.png"alt="Line History view"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/line-history-view.png"alt="Line History view"/>
</p>
A hidden by default, [customizable](#line-history-view-settings- 'Jump to the Line History view settings') view to visualize, navigate, and explore the revision history of the selected lines of the current file
@ -383,7 +383,7 @@ The line history view lists all of the commits that changed the selected lines o
A hidden by default, [customizable](#contributors-view-settings- 'Jump to the Contributors view settings') view to visualize, navigate, and explore contributors
@ -480,7 +480,7 @@ The _Contributors_ view lists all of the contributors, and additionally provides
A hidden by default, [customizable](#search--compare-view-settings- 'Jump to the Search & Compare view settings') view to search and explore commit histories by message, author, files, id, etc, or visualize comparisons between branches, tags, commits, and more
@ -515,7 +515,7 @@ The _Search & Compare_ view lists pinnable (saved) results for searching commit
- Adds a [customizable](#git-command-palette-settings- 'Jump to the Git Command Palette settings') _Git Command Palette_ command (`gitlens.gitCommands`) to provide guided (step-by-step) access to many common Git commands, as well as quick access to commit history and search, stashes, and more
@ -528,13 +528,13 @@ The _Search & Compare_ view lists pinnable (saved) results for searching commit
- Adds a _Show Current Branch History_ command (`gitlens.showQuickRepoHistory`) to show a quick pick menu to explore the commit history of the current branch
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/menu-branch-history.png"alt="Branch History Quick Pick Menu"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/menu-branch-history.png"alt="Branch History Quick Pick Menu"/>
</p>
- Adds a _Show File History_ command (`gitlens.showQuickFileHistory`) to show quick pick menu to explore the commit history of the current file
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/menu-file-history.png"alt="File History Quick Pick Menu"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/menu-file-history.png"alt="File History Quick Pick Menu"/>
</p>
- Adds a _Search Commits_ command (`gitlens.showCommitSearch`) to show quick pick menu to search for commits
@ -545,19 +545,19 @@ The _Search & Compare_ view lists pinnable (saved) results for searching commit
- or, by changes — use `~<pattern>` to find commits with differences whose patch text contains added/removed lines that match `<pattern>`— See [Git docs](https://git-scm.com/docs/git-log#Documentation/git-log.txt--Gltregexgt 'Open Git docs')
- Adds a _Show Line Commit_ command (`gitlens.showQuickCommitFileDetails`) to show a quick pick menu to explore a file of a commit and take action upon it
- [Optionally](##terminal-links-settings- 'Jump to the Terminal Links settings') adds autolinks for branches, tags, and commit ranges in the integrated terminal to quickly explore their commit history
@ -666,7 +666,7 @@ Additionally, these integrations provide commands to copy the url of or open, fi
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/menus.png"alt="Menus & Toolbars"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/menus.png"alt="Menus & Toolbars"/>
</p>
GitLens provides [customizable](#menu--toolbar-settings-) menu and toolbar contributions to put you in control over where GitLens' commands are shown. The easiest way to configure these settings is via the GitLens [**interactive settings editor**](#configuration- 'Jump to Configuration').
@ -674,7 +674,7 @@ GitLens provides [customizable](#menu--toolbar-settings-) menu and toolbar contr
For example, if you uncheck the _Add to the editor group toolbar_ you will see the following items removed from the toolbar:
<palign="center">
<imgsrc="https://raw.githubusercontent.com/eamodio/vscode-gitlens/main/images/docs/menus-example.png"alt="Editor Group Toolbar example"/>
<imgsrc="https://raw.githubusercontent.com/gitkraken/vscode-gitlens/main/images/docs/menus-example.png"alt="Editor Group Toolbar example"/>
</p>
You can also expand each group to control each area more granularly.
@ -693,7 +693,7 @@ GitLens supports [user-defined](#modes-settings- 'Jump to the Modes settings') m
GitLens provides a rich **interactive settings editor**, an easy-to-use interface, to configure many of GitLens' powerful features. It can be accessed via the _GitLens: Open Settings_ (`gitlens.showSettingsPage`) command from the [_Command Palette_](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette).
@ -710,7 +710,7 @@ GitLens is highly customizable and provides many configuration settings to allow
| `gitlens.currentLine.dateFormat` | Specifies how to format absolute dates (e.g. using the `${date}` token) for the current line blame annotations. See the [Moment.js docs](https://momentjs.com/docs/#/displaying/format/) for valid formats |
| `gitlens.currentLine.enabled` | Specifies whether to provide a blame annotation for the current line, by default. Use the _Toggle Line Blame Annotations_ command (`gitlens.toggleLineBlame`) to toggle the annotations on and off for the current window |
| `gitlens.currentLine.format` | Specifies the format of the current line blame annotation. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.currentLine.dateFormat` setting |
| `gitlens.currentLine.format` | Specifies the format of the current line blame annotation. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.currentLine.dateFormat` setting |
| `gitlens.currentLine.pullRequests.enabled` | Specifies whether to provide information about the Pull Request (if any) that introduced the commit in the current line blame annotation. Requires a connection to a supported remote service (e.g. GitHub) |
| `gitlens.currentLine.scrollable` | Specifies whether the current line blame annotation can be scrolled into view when it is outside the viewport. **NOTE**: Setting this to `false` will inhibit the hovers from showing over the annotation; Set `gitlens.hovers.currentLine.over` to `line` to enable the hovers to show anywhere over the line. |
@ -735,10 +735,10 @@ GitLens is highly customizable and provides many configuration settings to allow
| `gitlens.statusBar.command` | Specifies the command to be executed when the blame status bar item is clicked<br/><br/>`gitlens.toggleFileBlame` - toggles file blame annotations<br/>`gitlens.toggleFileHeatmap` - toggles file heatmap<br/>`gitlens.toggleFileChanges` - toggles file changes since before the commit<br/>`gitlens.toggleFileChangesOnly` - toggles file changes from the commit<br/>`gitlens.diffWithPrevious` - opens changes with the previous revision<br/>`gitlens.revealCommitInView` - reveals the commit in the Side Bar<br/>`gitlens.showCommitsInView` - searches for commits within the range<br/>`gitlens.showQuickCommitDetails` - shows details of the commit<br/>`gitlens.showQuickCommitFileDetails` - show file details of the commit<br/>`gitlens.showQuickFileHistory` - shows the current file history<br/>`gitlens.showQuickRepoHistory` - shows the current branch history<br/>`gitlens.openCommitOnRemote` - opens the commit on the remote service (when available)<br/>`gitlens.copyRemoteCommitUrl` - copies the remote commit url to the clipboard (when available)<br/>`gitlens.openFileOnRemote` - opens the file revision on the remote service (when available)<br/>`gitlens.copyRemoteFileUrl` - copies the remote file url to the clipboard (when available) |
| `gitlens.statusBar.dateFormat` | Specifies how to format absolute dates (e.g. using the `${date}` token) in the blame information in the status bar. See the [Moment.js docs](https://momentjs.com/docs/#/displaying/format/) for valid formats |
| `gitlens.statusBar.enabled` | Specifies whether to provide blame information in the status bar |
| `gitlens.statusBar.format` | Specifies the format of the blame information in the status bar. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.statusBar.dateFormat` setting |
| `gitlens.statusBar.format` | Specifies the format of the blame information in the status bar. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.statusBar.dateFormat` setting |
| `gitlens.statusBar.pullRequests.enabled` | Specifies whether to provide information about the Pull Request (if any) that introduced the commit in the status bar. Requires a connection to a supported remote service (e.g. GitHub) |
| `gitlens.statusBar.reduceFlicker` | Specifies whether to avoid clearing the previous blame information when changing lines to reduce status bar "flashing" |
| `gitlens.statusBar.tooltipFormat` | Specifies the format (in markdown) of hover shown over the blame information in the status bar. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.statusBar.tooltipFormat` | Specifies the format (in markdown) of hover shown over the blame information in the status bar. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
@ -755,7 +755,7 @@ GitLens is highly customizable and provides many configuration settings to allow
| `gitlens.hovers.currentLine.details` | Specifies whether to provide a _commit details_ hover for the current line |
| `gitlens.hovers.currentLine.enabled` | Specifies whether to provide any hovers for the current line |
| `gitlens.hovers.currentLine.over` | Specifies when to trigger hovers for the current line<br/><br/>`annotation` - only shown when hovering over the line annotation<br/>`line` - shown when hovering anywhere over the line |
| `gitlens.hovers.detailsMarkdownFormat` | Specifies the format (in markdown) of the _commit details_ hover. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.hovers.detailsMarkdownFormat` | Specifies the format (in markdown) of the _commit details_ hover. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.hovers.enabled` | Specifies whether to provide any hovers |
| `gitlens.hovers.autolinks.enabled` | Specifies whether to automatically link external resources in commit messages |
| `gitlens.hovers.autolinks.enhanced` | Specifies whether to lookup additional details about automatically link external resources in commit messages. Requires a connection to a supported remote service (e.g. GitHub) |
@ -763,17 +763,17 @@ GitLens is highly customizable and provides many configuration settings to allow
| `gitlens.views.defaultItemLimit` | Specifies the default number of items to show in a view list. Use 0 to specify no limit |
| `gitlens.views.formats.commits.label` | Specifies the format of commits in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.commits.description` | Specifies the description format of commits in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.files.label` | Specifies the format of a file in the views. See [_File Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs |
| `gitlens.views.formats.files.description` | Specifies the description format of a file in the views. See [_File Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs |
| `gitlens.views.formats.stashes.label` | Specifies the format of stashes in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.stashes.description` | Specifies the description format of stashes in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.pageItemLimit` | Specifies the number of items to show in a each page when paginating a view list. Use 0 to specify no limit |
| `gitlens.views.showRelativeDateMarkers` | Specifies whether to show relative date markers (_Less than a week ago_, _Over a week ago_, _Over a month ago_, etc) on revision (commit) histories in the views |
| `gitlens.views.defaultItemLimit` | Specifies the default number of items to show in a view list. Use 0 to specify no limit |
| `gitlens.views.formats.commits.label` | Specifies the format of commits in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.commits.description` | Specifies the description format of commits in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.files.label` | Specifies the format of a file in the views. See [_File Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs |
| `gitlens.views.formats.files.description` | Specifies the description format of a file in the views. See [_File Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs |
| `gitlens.views.formats.stashes.label` | Specifies the format of stashes in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.formats.stashes.description` | Specifies the description format of stashes in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs |
| `gitlens.views.pageItemLimit` | Specifies the number of items to show in a each page when paginating a view list. Use 0 to specify no limit |
| `gitlens.views.showRelativeDateMarkers` | Specifies whether to show relative date markers (_Less than a week ago_, _Over a week ago_, _Over a month ago_, etc) on revision (commit) histories in the views |
| `gitlens.blame.dateFormat` | Specifies how to format absolute dates (e.g. using the `${date}` token) in gutter blame annotations. See the [Moment.js docs](https://momentjs.com/docs/#/displaying/format/) for valid formats |
| `gitlens.blame.format` | Specifies the format of the gutter blame annotations. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.blame.dateFormat` setting |
| `gitlens.blame.format` | Specifies the format of the gutter blame annotations. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `gitlens.blame.dateFormat` setting |
| `gitlens.blame.heatmap.enabled` | Specifies whether to provide a heatmap indicator in the gutter blame annotations |
| `gitlens.blame.heatmap.location` | Specifies where the heatmap indicators will be shown in the gutter blame annotations<br/><br/>`left` - adds a heatmap indicator on the left edge of the gutter blame annotations<br/>`right` - adds a heatmap indicator on the right edge of the gutter blame annotations |
| `gitlens.blame.highlight.enabled` | Specifies whether to highlight lines associated with the current line |
@ -1084,86 +1084,86 @@ GitLens defines a set of themable colors which can be provided by vscode themes
A big thanks to the people that have contributed to this project:
- Matt Cooper ([@vtbassmatt](https://github.com/vtbassmatt)) — [contributions](https://github.com/eamodio/vscode-gitlens/commits?author=vtbassmatt)
- Andrew Savage ([@andrewsavage1](https://github.com/andrewsavage1)) — [contributions](https://github.com/eamodio/vscode-gitlens/commits?author=andrewsavage1)
- Matt Cooper ([@vtbassmatt](https://github.com/vtbassmatt)) — [contributions](https://github.com/gitkraken/vscode-gitlens/commits?author=vtbassmatt)
- Andrew Savage ([@andrewsavage1](https://github.com/andrewsavage1)) — [contributions](https://github.com/gitkraken/vscode-gitlens/commits?author=andrewsavage1)
"default":"${author, }${agoOrDate}${' via 'pullRequest}${ • message|50?}",
"markdownDescription":"Specifies the format of the current line blame annotation. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.currentLine.dateFormat#` setting",
"markdownDescription":"Specifies the format of the current line blame annotation. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.currentLine.dateFormat#` setting",
"scope":"window",
"order":30
},
@ -484,7 +484,7 @@
"gitlens.statusBar.format":{
"type":"string",
"default":"${author}, ${agoOrDate}${' via 'pullRequest}",
"markdownDescription":"Specifies the format of the blame information in the status bar. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.statusBar.dateFormat#` setting",
"markdownDescription":"Specifies the format of the blame information in the status bar. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.statusBar.dateFormat#` setting",
"scope":"window",
"order":30
},
@ -552,7 +552,7 @@
"type":"string",
"default":"${avatar} __${author}__, ${ago}${' via 'pullRequest} _(${date})_ \n\n${message}${\n\n---\n\nfootnotes}\n\n${commands}",
"editPresentation":"multilineText",
"markdownDescription":"Specifies the format (in markdown) of hover shown over the blame information in the status bar. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the format (in markdown) of hover shown over the blame information in the status bar. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":60
},
@ -698,7 +698,7 @@
"type":"string",
"default":"${avatar} __${author}__, ${ago}${' via 'pullRequest} _(${date})_ \n\n${message}${\n\n---\n\nfootnotes}\n\n${commands}",
"editPresentation":"multilineText",
"markdownDescription":"Specifies the format (in markdown) of the _commit details_ hover. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the format (in markdown) of the _commit details_ hover. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":60
},
@ -748,42 +748,42 @@
"gitlens.views.formats.commits.label":{
"type":"string",
"default":"${❰ tips ❱➤ }${message}",
"markdownDescription":"Specifies the format of commits in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the format of commits in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":30
},
"gitlens.views.formats.commits.description":{
"type":"string",
"default":"${author, }${agoOrDate}",
"markdownDescription":"Specifies the description format of commits in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the description format of commits in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":31
},
"gitlens.views.formats.files.label":{
"type":"string",
"default":"${working }${file}",
"markdownDescription":"Specifies the format of a file in the views. See [_File Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs",
"markdownDescription":"Specifies the format of a file in the views. See [_File Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs",
"scope":"window",
"order":32
},
"gitlens.views.formats.files.description":{
"type":"string",
"default":"${directory}${ ← originalPath}",
"markdownDescription":"Specifies the description format of a file in the views. See [_File Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs",
"markdownDescription":"Specifies the description format of a file in the views. See [_File Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#file-tokens) in the GitLens docs",
"scope":"window",
"order":33
},
"gitlens.views.formats.stashes.label":{
"type":"string",
"default":"${message}",
"markdownDescription":"Specifies the format of stashes in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the format of stashes in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":34
},
"gitlens.views.formats.stashes.description":{
"type":"string",
"default":"${agoOrDate}",
"markdownDescription":"Specifies the description format of stashes in the views. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"markdownDescription":"Specifies the description format of stashes in the views. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs",
"scope":"window",
"order":35
},
@ -1847,7 +1847,7 @@
"gitlens.blame.format":{
"type":"string",
"default":"${message|50?} ${agoOrDate|14-}",
"markdownDescription":"Specifies the format of the gutter blame annotations. See [_Commit Tokens_](https://github.com/eamodio/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.blame.dateFormat#` setting",
"markdownDescription":"Specifies the format of the gutter blame annotations. See [_Commit Tokens_](https://github.com/gitkraken/vscode-gitlens/wiki/Custom-Formatting#commit-tokens) in the GitLens docs. Date formatting is controlled by the `#gitlens.blame.dateFormat#` setting",
Eric Amodio
hace 2 años