- The indicator's, now customizable, color will either be hot or cold based on the age of the most recent change (cold after 90 days by default) — closes [#419](https://github.com/eamodio/vscode-gitlens/issues/419)
- The indicator's brightness ranges from bright (newer) to dim (older) based on the relative age, which is calculated from the median age of all the changes in the file
- Adds `gitlens.heatmap.ageThreshold` setting to specify the age of the most recent change (in days) after which the gutter heatmap annotations will be cold rather than hot (i.e. will use `gitlens.heatmap.coldColor` instead of `gitlens.heatmap.hotColor`)
- Adds `gitlens.heatmap.coldColor` setting to specify the base color of the gutter heatmap annotations when the most recent change is older (cold) than the `gitlens.heatmap.ageThreshold` setting
- Adds `gitlens.heatmap.hotColor` setting to specify the base color of the gutter heatmap annotations when the most recent change is newer (hot) than the `gitlens.heatmap.ageThreshold` setting
- Adds new branch history node under the **Repository Status** node in the *GitLens* explorer
- Adds new branch history node under the *Repository Status* node in the *GitLens* explorer
- Adds GitLab and Visual Studio Team Services icons to the remote nodes in the *GitLens* explorer — thanks to [PR #421](https://github.com/eamodio/vscode-gitlens/pull/421) by Maxim Pekurin ([@pmaxim25](https://github.com/pmaxim25))
- Adds the ability to control where the *GitLens*, *GitLens History*, and *GitLens Results* explorers are shown 🎉 — closes [#213](https://github.com/eamodio/vscode-gitlens/issues/213), [#377](https://github.com/eamodio/vscode-gitlens/issues/377)
- Adds `gitlens.gitExplorer.location` setting to the interactive settings editor to specify where the *GitLens* explorer is shown — either in the *Explorer* or *Source Control* view
- Adds `gitlens.historyExplorer.location` setting to the interactive settings editor to specify where the *GitLens History* explorer is shown — either in the *Explorer* or *Source Control* view
- Adds `gitlens.resultsExplorer.location` setting to the interactive settings editor to specify where the *GitLens Results* explorer is shown — either in the *Explorer* or *Source Control* view
- Adds user-defined modes for quickly toggling between sets of settings
- Adds `gitlens.settings.mode` setting to specify the display mode of the interactive settings editor
- Adds (re-adds) support for handling single files — closes [#321](https://github.com/eamodio/vscode-gitlens/issues/321)
- Adds a tree layout option to tags in the *GitLens* explorer — closes [#358](https://github.com/eamodio/vscode-gitlens/issues/358)
- Adds *Show GitLens Explorer* (`gitlens.showGitExplorer`) command — shows/expands the *GitLens* explorer
- Adds *Show History Explorer* (`gitlens.showHistoryExplorer`) command — shows/expands the *GitLens History* explorer
- Adds *Show Results Explorer* (`gitlens.showResultsExplorer`) command — shows/expands the *GitLens Results* explorer
- Adds *Close Repository* (`gitlens.explorers.closeRepository`) command to repository and repository status nodes in the *GitLens* explorer — closes (hides) the repository in the *GitLens* explorer
- Adds clipboard support for Linux without requiring any external dependencies — thanks to [PR #394](https://github.com/eamodio/vscode-gitlens/pull/394) by Cédric Malard ([@cmalard](https://github.com/cmalard))
- Adds a select branch quick pick menu to the *Open File in Remote* command (`gitlens.openFileInRemote`) when the current branch has no upstream tracking branch — closes [#209](https://github.com/eamodio/vscode-gitlens/issues/209)
- Showing results in the *GitLens Results* explorer now properly shows the explorer first
- Renames *Compare Line Revision with Previous* command (`gitlens.diffLineWithPrevious`) to *Compare Commit with Previous* for consistency with other commands
- Renames *Compare Line Revision with Working File* command (`gitlens.diffLineWithWorking`) to *Compare Commit with Working File* for consistency with other commands
- Renames *Show Commit File Details* command (`gitlens.showQuickCommitFileDetails`) to *Show Commit Details* for consistency with other commands
- Reworks GitLens menu contributions and configuration — see menu settings above
- Renames the `gitlens.advanced.menus` setting to `gitlens.menus`
- Uses the new Webview API for better interactions and behavior with the interactive settings editor and welcome page
- Moves the *Open Working File* command (`gitlens.openWorkingFile`) to the right of the *Compare File with * Revision* commands in the editor toolbar
- Fixes [#366](https://github.com/eamodio/vscode-gitlens/issues/366) - Running a GitLens command from a keybinding fails
- Fixes [#400](https://github.com/eamodio/vscode-gitlens/issues/400) - Reset TO commit also resets chosen one
- Fixes [#399](https://github.com/eamodio/vscode-gitlens/issues/399) - "Open x in Remote" commands aren't always available
- Fixes [#397](https://github.com/eamodio/vscode-gitlens/issues/397) - Error while opening the gitlens view using `Open View` command
- Fixes [#391](https://github.com/eamodio/vscode-gitlens/issues/391) - GitLens adds some settings in settings.json
- Fixes another case of [#343](https://github.com/eamodio/vscode-gitlens/issues/343) - Can't show blame when VSCode starts on branch without upstream — thanks to [PR #390](https://github.com/eamodio/vscode-gitlens/pull/390) by ryenus ([@ryenus](https://github.com/ryenus))
- Fixes [#392](https://github.com/eamodio/vscode-gitlens/issues/392) - unable to contribute if default script shell is sh — thanks to [PR #393](https://github.com/eamodio/vscode-gitlens/pull/393) by Cédric Malard ([@cmalard](https://github.com/cmalard))
- Fixes more instances of [#295](https://github.com/eamodio/vscode-gitlens/issues/295) and [#318](https://github.com/eamodio/vscode-gitlens/issues/318) - Any error encountered during the search for repositories could cause GitLens to die
- Fixes issue with the `chorded` keyboard shortcut for the *Compare File with Previous Revision* command (`gitlens.diffWithPreviousInDiff`) — from [#395](https://github.com/eamodio/vscode-gitlens/issues/395)
- Fixes *bronze* typo thanks to [PR #361](https://github.com/eamodio/vscode-gitlens/pull/361) by Cory Forsyth ([@bantic](https://github.com/bantic))
- Fixes *individually* typo thanks to [PR #364](https://github.com/eamodio/vscode-gitlens/pull/364) by Brett Cannon ([@brettcannon](https://github.com/brettcannon))
- Fixes issue where comparing previous revision during a merge/rebase conflict failed to show the correct contents
- Fixes issue with the current line blame toggle not working when current line blame starts disabled
- Fixes various issues when not on a branch
- Fixes many issues where commands wouldn't work if the active file wasn't part of an open repository — now GitLens will try to find the best repository otherwise it will open a repository quick pick menu if there is more than one
- Fixes the *Open Working File* command (`gitlens.openWorkingFile`) not always showing in the editor toolbar when appropriate
- The indicator's, now customizable, color will either be hot or cold based on the age of the most recent change (cold after 90 days by default) — closes [#419](https://github.com/eamodio/vscode-gitlens/issues/419)
- The indicator's brightness ranges from bright (newer) to dim (older) based on the relative age, which is calculated from the median age of all the changes in the file
- Adds `gitlens.heatmap.ageThreshold` setting to specify the age of the most recent change (in days) after which the gutter heatmap annotations will be cold rather than hot (i.e. will use `gitlens.heatmap.coldColor` instead of `gitlens.heatmap.hotColor`)
- Adds `gitlens.heatmap.coldColor` setting to specify the base color of the gutter heatmap annotations when the most recent change is older (cold) than the `gitlens.heatmap.ageThreshold` setting
- Adds `gitlens.heatmap.hotColor` setting to specify the base color of the gutter heatmap annotations when the most recent change is newer (hot) than the `gitlens.heatmap.ageThreshold` setting
- Adds new branch history node under the *Repository Status* node in the *GitLens* explorer
- Adds GitLab and Visual Studio Team Services icons to the remote nodes in the *GitLens* explorer — thanks to [PR #421](https://github.com/eamodio/vscode-gitlens/pull/421) by Maxim Pekurin ([@pmaxim25](https://github.com/pmaxim25))
- Fixes [#400](https://github.com/eamodio/vscode-gitlens/issues/412) - GitLens logging to debug console when debugging different extension
- Fixes [#409](https://github.com/eamodio/vscode-gitlens/issues/409) - Literal $(ellipsis) inserted into commit QuickPick menu entry placeholder text
- Fixes [#415](https://github.com/eamodio/vscode-gitlens/issues/415) - Branch names get mangled by color escapes — thanks to [PR #416](https://github.com/eamodio/vscode-gitlens/pull/416) by Roy Ivy III ([@rivy](https://github.com/rivy))
See the [release notes](https://github.com/eamodio/vscode-gitlens/blob/master/CHANGELOG.md "Open Release Notes") for the full set of changes
"description":"Supercharge the Git capabilities built into Visual Studio Code \u2014 Visualize code authorship at a glance via Git blame annotations and code lens, seamlessly navigate and explore Git repositories, gain valuable insights via powerful comparison commands, and so much more",
<atitle="Open Issue #400"href="https://github.com/eamodio/vscode-gitlens/issues/400">#400</a>— GitLens logging to debug console when debugging different extension
<atitle="Open Issue #409"href="https://github.com/eamodio/vscode-gitlens/issues/409">#409</a>— Literal $(ellipsis) inserted into commit QuickPick menu entry placeholder text
<atitle="Open Issue #415"href="https://github.com/eamodio/vscode-gitlens/issues/415">#415</a>— Branch names get mangled by color escapes — thanks to
<atitle="Pull Request #416"href="https://github.com/eamodio/vscode-gitlens/pull/416">PR #416</a> by
<atitle="Roy Ivy III (@rivy)"href="https://github.com/rivy">Roy Ivy III</a>
Adds the ability to control where the <i>GitLens</i>, <i>GitLens History</i>, and <i>GitLens Results</i> explorers are shown 🎉 — closes <atitle="Open Issue #213"href="https://github.com/eamodio/vscode-gitlens/issues/213">#213</a>, <atitle="Open Issue #377"href="https://github.com/eamodio/vscode-gitlens/issues/377">#377</a>
Adds (re-adds) support for handling single files — closes <atitle="Open Issue #321"href="https://github.com/eamodio/vscode-gitlens/issues/321">#321</a>
Adds a tree layout option to tags in the <i>GitLens</i> explorer — closes <atitle="Open Issue #358"href="https://github.com/eamodio/vscode-gitlens/issues/358">#358</a>
Adds <i>Close Repository</i> command (<code>gitlens.explorers.closeRepository</code>) to repository and repository status nodes in the <i>GitLens</i> explorer — closes (hides) the repository in the <i>GitLens</i> explorer
Adds clipboard support for Linux without requiring any external dependencies — thanks to <atitle="Pull Request #394"href="https://github.com/eamodio/vscode-gitlens/pull/394">PR #394</a> by Cédric Malard (<atitle="Cédric Malard"href="https://github.com/cmalard">@cmalard</a>)
Adds a select branch quick pick menu to the <i>Open File in Remote</i> command (<code>gitlens.openFileInRemote</code>) when the current branch has no upstream tracking branch — closes <atitle="Open Issue #209"href="https://github.com/eamodio/vscode-gitlens/issues/209">#209</a>
Moves the <i>Open Working File</i> command (<code>gitlens.openWorkingFile</code>) to the right of the <i>Compare File with * Revision</i> commands in the editor toolbar
Fixes <atitle="Open Issue #366"href="https://github.com/eamodio/vscode-gitlens/issues/366">#366</a>— Running a GitLens command from a keybinding fails
Fixes <atitle="Open Issue #359"href="https://github.com/eamodio/vscode-gitlens/issues/359">#359</a>— Show changes of an added file in the first commit
Fixes <atitle="Open Issue #372"href="https://github.com/eamodio/vscode-gitlens/issues/372">#372</a>— Wrong URL to VSTS work item when using hash work item id in commit
<atitle="Open Issue #372"href="https://github.com/eamodio/vscode-gitlens/issues/372">#372</a>— Wrong URL to VSTS work item when using hash work item id in commit
Fixes <atitle="Open Issue #381"href="https://github.com/eamodio/vscode-gitlens/issues/381">#381</a>— Can't stash single files with older versions of Git
<atitle="Open Issue #381"href="https://github.com/eamodio/vscode-gitlens/issues/381">#381</a>— Can't stash single files with older versions of Git
Fixes <atitle="Open Issue #384"href="https://github.com/eamodio/vscode-gitlens/issues/384">#384</a>— Absolute dates not always honored in <i>GitLens Results</i> explorer
Fixes <atitle="Open Issue #399"href="https://github.com/eamodio/vscode-gitlens/issues/399">#399</a>— "Open x in Remote" commands aren't always available
<atitle="Open Issue #399"href="https://github.com/eamodio/vscode-gitlens/issues/399">#399</a>— "Open x in Remote" commands aren't always available
Fixes <atitle="Open Issue #397"href="https://github.com/eamodio/vscode-gitlens/issues/397">#397</a>— Error while opening the gitlens view using <code>Open View</code> command
Fixes <atitle="Open Issue #343"href="https://github.com/eamodio/vscode-gitlens/issues/343">#343</a>— Can't show blame when VSCode starts on branch without upstream — thanks to <atitle="Pull Request #390"href="https://github.com/eamodio/vscode-gitlens/pull/390">PR #390</a> by ryenus (<atitle="ryenus"href="https://github.com/ryenus">@ryenus</a>)
<atitle="Open Issue #343"href="https://github.com/eamodio/vscode-gitlens/issues/343">#343</a>— Can't show blame when VSCode starts on branch without upstream — thanks
to
<atitle="Pull Request #390"href="https://github.com/eamodio/vscode-gitlens/pull/390">PR #390</a> by
Fixes <atitle="Open Issue #392"href="https://github.com/eamodio/vscode-gitlens/issues/392">#392</a>— unable to contribute if default script shell is sh — thanks to <atitle="Pull Request #393"href="https://github.com/eamodio/vscode-gitlens/pull/393">PR #393</a> by Cédric Malard (<atitle="Cédric Malard"href="https://github.com/cmalard">@cmalard</a>)
<atitle="Open Issue #392"href="https://github.com/eamodio/vscode-gitlens/issues/392">#392</a>— unable to contribute if default script shell is sh — thanks to
<atitle="Pull Request #393"href="https://github.com/eamodio/vscode-gitlens/pull/393">PR #393</a> by
Fixes more instances of <atitle="Open Issue #295"href="https://github.com/eamodio/vscode-gitlens/issues/295">#295</a> and <atitle="Open Issue #318"href="https://github.com/eamodio/vscode-gitlens/issues/318">#318</a>— Any error encountered during the search for repositories could cause GitLens to die
<atitle="Open Issue #295"href="https://github.com/eamodio/vscode-gitlens/issues/295">#295</a> and
<atitle="Open Issue #318"href="https://github.com/eamodio/vscode-gitlens/issues/318">#318</a>— Any error encountered during the search for repositories could cause GitLens
Fixes issue with the <code>chorded</code> keyboard shortcut for the <i>Compare File with Previous Revision</i> command (<code>gitlens.diffWithPreviousInDiff</code>) — from <atitle="Open Issue #395"href="https://github.com/eamodio/vscode-gitlens/issues/395">#395</a>
Fixes many issues where commands wouldn't work if the active file wasn't part of an open repository — now GitLens will try to find the best repository otherwise it will open a repository quick pick menu if there is more than one
Adds new stand-alone <i>GitLens History</i> explorer to visualize the history of the current file — undocked version of the <i>GitLens</i> explorer history view
Adds richer tooltips to the <i>GitLens</i> and <i>GitLens Results</i> explorers, and richer working tree and upstream status to the <i>GitLens</i> explorer
Adds ability to easily switch between relative and absolute dates via the <code>gitlens.defaultDateStyle</code> settings — closes <atitle="Open Issue #312"href="https://github.com/eamodio/vscode-gitlens/issues/312">#312</a>
Adds new <code>gitlens.currentLine.scrollable</code> setting to specify whether the current line blame annotation can be scrolled into view when it is outside the viewport — closes <atitle="Open Issue #149"href="https://github.com/eamodio/vscode-gitlens/issues/149">#149</a>, <atitle="Open Issue #290"href="https://github.com/eamodio/vscode-gitlens/issues/290">#290</a>, <atitle="Open Issue #265"href="https://github.com/eamodio/vscode-gitlens/issues/265">#265</a>
Fixes <atitle="Open Issue #314"href="https://github.com/eamodio/vscode-gitlens/issues/314">#314</a>— Toggle line annotation doesn't work properly
Fixes <atitle="Open Issue #310"href="https://github.com/eamodio/vscode-gitlens/issues/310">#310</a>— "via Terminal" commands need quoting around work directory
<atitle="Open Issue #310"href="https://github.com/eamodio/vscode-gitlens/issues/310">#310</a>— "via Terminal" commands need quoting around work directory
Adds support to toggle annotations for each file individually or for all files at once — closes <atitle="Open Issue #289"href="https://github.com/eamodio/vscode-gitlens/issues/289">#289</a>
Adds multi-cursor support to current line annotations — closes <atitle="Open Issue #291"href="https://github.com/eamodio/vscode-gitlens/issues/291">#291</a>
Renames <i>Compare Selected Ancestor with Working Tree</i> command to <i>Compare Ancestry with Working Tree</i> and removes the need to select a branch first, since all compares are performed with the working tree — closes <atitle="Open Issue #279"href="https://github.com/eamodio/vscode-gitlens/issues/279">#279</a>
Fixes <atitle="Open Issue #294"href="https://github.com/eamodio/vscode-gitlens/issues/294">#294</a>— Keyboard shortcuts will now default to <i>chorded</i> to avoid conflicts. Only affects new installs or if you remove the <spanclass="setting-key">gitlens.keymap</span> setting
Brand new interactive <aclass="command"title="Open GitLens Settings"href="command:gitlens.showSettingsPage">settings editor</a>— GitLens is easier than ever to customize to suit your needs
<aclass="command"title="Open GitLens Settings"href="command:gitlens.showSettingsPage">settings editor</a>— GitLens is easier than ever to customize to suit your needs
Previous settings will now be migrated properly — sorry everyone 😢
</li>
</ul>
</div>
<pclass="changelog__hint">
See the <atitle="Open Release Notes"href="https://github.com/eamodio/vscode-gitlens/blob/master/CHANGELOG.md">release notes</a> for the full set of changes
See the
<atitle="Open Release Notes"href="https://github.com/eamodio/vscode-gitlens/blob/master/CHANGELOG.md">release notes</a> for the full set of changes
</p>
<divclass="settings-group__setting nowrap ml-1">
@ -406,8 +698,9 @@
<p>
<aclass="bold"title="Learn more about GitLens"href="http://gitlens.amod.io">GitLens</a> is an
<aclass="bold"title="Open GitLens on GitHub"href="https://github.com/eamodio/vscode-gitlens">open-source</a> extension for Visual Studio Code created by
<aclass="bold"title="Learn more about Eric"href="http://www.amod.io/?utm_source=gitlens">Eric Amodio</a>.
While GitLens is generously offered to everyone free of charge, if you find it useful please consider <aclass="bold"title="Support GitLens"href="#support-gitlens">supporting</a> it.
<aclass="bold"title="Learn more about Eric"href="http://www.amod.io/?utm_source=gitlens">Eric Amodio</a>. While GitLens is generously offered to everyone free of charge, if you find
it useful please consider
<aclass="bold"title="Support GitLens"href="#support-gitlens">supporting</a> it.
</p>
<p>
GitLens simply helps you understand code better. Quickly glimpse into whom, why, and when a line or code block was changed.
@ -416,26 +709,50 @@
</p>
<p>Here are just some of the features that GitLens provides,
<ulclass="section-list">
<li>a <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-explorer"><i>GitLens</i> explorer</a> to navigate and explore repositories</li>
<li>a <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-history-explorer"><i>GitLens History</i> explorer</a> to navigate and explore file histories</li>
<li>an on-demand <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-results-explorer"><i>GitLens Results</i> explorer</a> to navigate and explore commits, histories, and searches, or visualize comparisons between branches, tags, commits, and more</li>
<li>authorship <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#code-lens">code lens</a> showing the most recent commit and # of authors to the top of files and/or on code blocks</li>
<li>an unobtrusive <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#current-line-blame">current line blame</a> annotation at the end of the line</li>
<li>on-demand <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gutter-blame">gutter blame</a> annotations, including a heatmap, for the whole file</li>
<li>detailed blame information accessible via <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#hovers">hovers</a></li>
<li>on-demand <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#recent-changes">recent changes</a> annotations to highlight lines changed by the most recent commit</li>
<li>a <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#status-bar-blame">status bar blame</a> annotation showing author and date for the current line</li>
<li><atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#commit-search">commit search</a>— by message, author, filename, commit id, or code changes</li>
<li>many powerful commands for exploring commits and histories, comparing and navigating revisions, stash access, repository status, etc</li>
<li>and so much <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#features">more</a></li>
<li>a
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-explorer">
<i>GitLens</i> explorer</a> to navigate and explore repositories</li>
<li>a
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-history-explorer">
<i>GitLens History</i> explorer</a> to navigate and explore file histories
</li>
<li>an on-demand
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-results-explorer">
<i>GitLens Results</i> explorer</a> to navigate and explore commits, histories, and
searches, or visualize comparisons between branches, tags, commits, and more</li>
<li>authorship
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#code-lens">code lens</a> showing the most recent commit and # of authors to the top of files and/or
on code blocks</li>
<li>an unobtrusive
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#current-line-blame">current line blame</a> annotation at the end of the line</li>
<li>on-demand
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gutter-blame">gutter blame</a> annotations, including a heatmap, for the whole file
</li>
<li>detailed blame information accessible via
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#hovers">hovers</a>
</li>
<li>on-demand
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#recent-changes">recent changes</a> annotations to highlight lines changed by the most recent commit</li>
<li>a
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#status-bar-blame">status bar blame</a> annotation showing author and date for the current line
</li>
<li>
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#commit-search">commit search</a>— by message, author, filename, commit id, or code changes</li>
<li>many powerful commands for exploring commits and histories, comparing and navigating revisions,
stash access, repository status, etc</li>
<li>and so much
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#features">more</a>
</li>
</ul>
</p>
<pclass="mb-2">GitLens is powerful, feature rich, and highly customizable to meet your specific needs
— find code lens intrusive or the current line blame annotation distracting —
no problem, it is quick and easy to turn them off or change how they behave via the built-in <aclass="command"title="Open GitLens Settings"href="command:gitlens.showSettingsPage">GitLens Settings</a> editor,
an interactive editor covering many of GitLens' powerful settings.
While for more advanced customizations, refer to the <atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-settings">GitLens settings docs</a>
and edit your <aclass="command"title="Open User Settings"href="command:workbench.action.openGlobalSettings">User Settings</a>.
<pclass="mb-2">GitLens is powerful, feature rich, and highly customizable to meet your specific needs — find
code lens intrusive or the current line blame annotation distracting — no problem, it is
quick and easy to turn them off or change how they behave via the built-in
<aclass="command"title="Open GitLens Settings"href="command:gitlens.showSettingsPage">GitLens Settings</a> editor, an interactive editor covering many of GitLens' powerful settings.
While for more advanced customizations, refer to the
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gitlens-settings">GitLens settings docs</a>
and edit your
<aclass="command"title="Open User Settings"href="command:workbench.action.openGlobalSettings">User Settings</a>.
While GitLens is generously offered to everyone free of charge, if you find it useful please consider supporting it.
</p>
<p>
I've been building GitLens in my spare time<sup><atitle="nights and weekends, i.e. trading sleep for time">1</a></sup> for almost 2 years now.
From its very humble beginnings, GitLens has grown wildly beyond my expectations — in both its reach as well as its demands on my time and attention.
While I enjoy giving my free time and attention to GitLens' development and growth, I would like to do even more.
I've been building GitLens in my spare time
<sup>
<atitle="nights and weekends, i.e. trading sleep for time">1</a>
</sup> for almost 2 years now. From its very humble beginnings, GitLens has grown wildly beyond my expectations
— in both its reach as well as its demands on my time and attention. While I enjoy giving
my free time and attention to GitLens' development and growth, I would like to do even more.
</p>
<h3>Show Your Support ❤</h3>
<p>
To my incredible backers — thank you so much for your contributions.
I am truly humbled by your generosity and support.
Please know that your support plays a important role in helping me realize GitLens' potential in making developer's lives easier.
To my incredible backers — thank you so much for your contributions. I am truly humbled by your generosity and support.
Please know that your support plays a important role in helping me realize GitLens' potential
in making developer's lives easier.
</p>
<p>
If you'd like to join them in supporting GitLens, please consider the following — feel free to choose more than one. 😉
If you'd like to join them in supporting GitLens, please consider the following — feel free to choose more than one.
<h3class="list-button__title">Open User Settings</h3>
<spanclass="list-button__detail"title="Find and customize all GitLens settings">Search for <b><i>gitlens</i></b> to find and customize all GitLens settings</span>
<spanclass="list-button__detail"title="Find and customize all GitLens settings">Search for
<b>
<i>gitlens</i>
</b> to find and customize all GitLens settings</span>
<spanclass="list-button__detail"title="Find and customize GitLens keyboard shortcuts">Search for <b><i>gitlens</i></b> to find and customize GitLens keyboard shortcuts</span>
<spanclass="list-button__detail"title="Find and customize GitLens keyboard shortcuts">Search for
<b>
<i>gitlens</i>
</b> to find and customize GitLens keyboard shortcuts</span>
<h3class="list-button__title">Find and run all GitLens commands</h3>
<spanclass="list-button__detail"title="Find and access GitLens commands from the Command Palette">Search for <b><i>gitlens</i></b> to find and access GitLens commands from the Command Palette</span>
<spanclass="list-button__detail"title="Find and access GitLens commands from the Command Palette">Search for
<b>
<i>gitlens</i>
</b> to find and access GitLens commands from the Command Palette</span>
</button>
</div>
</div>
@ -504,9 +840,15 @@
<aclass="button button--flat-primary"title="One-time donations via Cash App"href="https://cash.me/$eamodio"target="_blank">Donations via Cash App</a>
</div>
<ul>
<li><atitle="Write a review"href="https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens#review-details">Write a Review</a></li>
<li><atitle="Star or fork me on GitHub"href="https://github.com/eamodio/vscode-gitlens">Star or Fork me on GitHub</a></li>
<li><atitle="Follow me on Twitter"href="https://twitter.com/eamodio">Follow me on Twitter</a></li>
<li>
<atitle="Write a review"href="https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens#review-details">Write a Review</a>
</li>
<li>
<atitle="Star or fork me on GitHub"href="https://github.com/eamodio/vscode-gitlens">Star or Fork me on GitHub</a>
</li>
<li>
<atitle="Follow me on Twitter"href="https://twitter.com/eamodio">Follow me on Twitter</a>
Eric Amodio
há 6 anos
