@ -4,12 +4,12 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/).
## [Unreleased]
## [8.5.4] - 2018-07-31
### Added
- Adds *Checkout Commit (via Terminal)* command (`gitlens.terminalCheckoutCommit`) to commit node(s) of the *GitLens* explorer — closes [#463](https://github.com/eamodio/vscode-gitlens/issues/463)
### Changed
- Improves performance of blame annotation rendering
- Improves performance of providing blame annotations, especially for large files (a ~33% improvement on some files)
- Changes commit search by sha to jump directly to the commit (if one is found), rather than having to click through to the commit
- Updates settings descriptions to better support the new settings editor in vscode
- Changes *Rebase to Commit (via Terminal)* command (`gitlens.terminalRebaseCommit`) to apply to all commit node(s) of the *GitLens* explorer
- Adds tag annotations to the tag tooltips in the *GitLens* explorer — closes [#431](https://github.com/eamodio/vscode-gitlens/issues/431)
- Adds *Choose from Branch or Tag History...* to the quick pick menu shown by the *Show File History...* command (`gitlens.showQuickFileHistory`) — closes [#316](https://github.com/eamodio/vscode-gitlens/issues/316)
- Adds the *Compare File with Revision...* command (`gitlens.diffWithRevision`) as an alternate (`alt+click`) for the *Compare File with Previous Revision* command in the editor toolbar
- Adds *Checkout Commit (via Terminal)* command (`gitlens.terminalCheckoutCommit`) to commit node(s) of the *GitLens* explorer — closes [#463](https://github.com/eamodio/vscode-gitlens/issues/463)
- Adds `gitlens.historyExplorer.avatars` setting to specify whether to show avatar images instead of status icons in the *GitLens File History* explorer — allows for an independent value from the other explorers
- Adds a `gitlens.hovers.avatars` setting to specify whether to show avatar images in hovers — closes [#432](https://github.com/eamodio/vscode-gitlens/issues/432) thanks to [PR #441](https://github.com/eamodio/vscode-gitlens/pull/441) by Segev Finer ([@segevfiner](https://github.com/segevfiner))
- Adds the `gitlens.hovers.avatars` setting to the *GitLens* interactive settings editor to specify whether to show avatar images in hovers
- Improves performance of providing blame annotations, especially for large files (a ~33% improvement on some files)
- Changes commit search by sha to jump directly to the commit (if one is found), rather than having to click through to the commit
- Renames the *GitLens History* explorer to *GitLens File History* explorer for better clarity
- Changes the *GitLens File History* explorer to always show the full file history even when reviewing revisions
- Changes the behavior of and renames the *Show Branches and Tags* command and on the quick pick menu shown by the *Compare File with Revision...* command (`gitlens.diffWithRevision`) to *Choose from Branch or Tag History...*
- Changes the behavior of and renames the *Show Branches and Tags* command on the quick pick menu shown by the *Open Revision...* command (`gitlens.openFileRevision`) to *Choose from Branch or Tag History...*
- Changes *Rebase to Commit (via Terminal)* command (`gitlens.terminalRebaseCommit`) to apply to all commit node(s) of the *GitLens* explorer
- Changes *Reset to Commit (via Terminal)* command (`gitlens.terminalResetCommit`) to apply to all commit node(s) of the *GitLens* explorer
- Updates settings descriptions to better support the new settings editor in vscode
- Removes `gitlens:activeIsTracked`, `gitlens:activeIsBlameable`, `gitlens:activeIsRevision`, and `gitlens:activeHasRemotes` contexts and consolidates them into `gitlens:activeFileStatus` for better performance and UX
- Fixes [#436](https://github.com/eamodio/vscode-gitlens/issues/436) - Copy to clipboard not working
- Fixes [#442](https://github.com/eamodio/vscode-gitlens/issues/442) - GitLens File History fails if name (or path) starts with `-`
@ -38,6 +44,10 @@
- Fixes [#451](https://github.com/eamodio/vscode-gitlens/issues/451) - "apply Changes" has discarded all my changes
- Fixes [#449](https://github.com/eamodio/vscode-gitlens/issues/449) - Stop hiding explorers by default when in Zen mode
- Fixes [#454](https://github.com/eamodio/vscode-gitlens/issues/454) - Search for string returns merge commits (unlike raw `git log -S`)
- Fixes [#462](https://github.com/eamodio/vscode-gitlens/issues/462) - Source Control shortcut on macOS (⌃⇧G) shouldn't be overridden
- Fixes [#457](https://github.com/eamodio/vscode-gitlens/issues/457) - Displays the wrong username (You) — thanks to [PR #460](https://github.com/eamodio/vscode-gitlens/pull/460) by Zyck ([@qzyse2017](https://github.com/qzyse2017))
- Fixes [#459](https://github.com/eamodio/vscode-gitlens/issues/459) - File blame annotation text overflow with letter spacing setting
- Fixes issues with GitLens Welcome and the interactive settings editor with light themes
- Fixes issue where commands in the editor toolbar would flash unnecessarily when navigating history or switching tabs
- Fixes issue where the *Compare File with Previous Revision* command wouldn't work properly when the file had been renamed in some cases
- Fixes issue where the *Compare File with Next Revision* command wouldn't work properly when the file had been renamed in some cases
"description":"Supercharge the Git capabilities built into Visual Studio Code — 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 #442"href="https://github.com/eamodio/vscode-gitlens/issues/442">#442</a>— GitLens File History fails if name (or path) starts with
<atitle="Open Issue #440"href="https://github.com/eamodio/vscode-gitlens/issues/440">#440</a>— Searching for commits with an empty query yields to no results anymore
<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="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 #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 #399"href="https://github.com/eamodio/vscode-gitlens/issues/399">#399</a>— "Open x in Remote" commands aren't always available
<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
<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
<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
<atitle="Open Issue #310"href="https://github.com/eamodio/vscode-gitlens/issues/310">#310</a>— "via Terminal" commands need quoting around work directory
<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="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="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.
</p>
<p>
@ -958,42 +1077,60 @@
<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>
<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>
<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
<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>on-demand
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gutter-heatmap">gutter heatmap</a> annotations to show how recently lines were changed, relative to all
the other changes in the file and to now (hot vs. cold)
<atitle="Open the GitLens docs"href="https://github.com/eamodio/vscode-gitlens/#gutter-heatmap">gutter
heatmap
</a> annotations to show how recently lines were changed, relative to all the other changes
in the file and to now (hot vs. cold)
</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>
<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
<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>
<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
<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>
<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
<spanclass="list-button__detail"title="Customize common GitLens settings in an easy to use editor">Customize common GitLens settings in an easy to use editor</span>
<spanclass="list-button__detail"title="Customize common GitLens settings in an easy to use editor">Customize
common GitLens settings in an easy to use editor</span>
Eric Amodio
6 роки тому