diff --git a/CHANGELOG.md b/CHANGELOG.md index ead0333..c4ad88d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 diff --git a/README.md b/README.md index f68e628..57f5d16 100644 --- a/README.md +++ b/README.md @@ -21,13 +21,19 @@ - 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 diff --git a/package-lock.json b/package-lock.json index c0491b1..aa03f7d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,6 +1,6 @@ { "name": "gitlens", - "version": "8.5.3", + "version": "8.5.4", "lockfileVersion": 1, "requires": true, "dependencies": { diff --git a/package.json b/package.json index 9740e35..5c0b548 100644 --- a/package.json +++ b/package.json @@ -2,7 +2,7 @@ "name": "gitlens", "displayName": "GitLens — Git supercharged", "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", - "version": "8.5.3", + "version": "8.5.4", "author": { "name": "Eric Amodio", "email": "eamodio@gmail.com" diff --git a/src/ui/welcome/index.html b/src/ui/welcome/index.html index e6a5e66..49c2d4d 100644 --- a/src/ui/welcome/index.html +++ b/src/ui/welcome/index.html @@ -29,11 +29,15 @@
- Configure GitLens + Configure + GitLens +

Don't miss how easy it is to configure GitLens!

- Support GitLens ❤ + Support GitLens + ❤ +
@@ -55,8 +59,8 @@ GitLens File History, and GitLens Results explorers
-

The new view is enabled by default, but can easily be configured back to the existing locations - via the +

The new view is enabled by default, but can easily be configured back to the existing + locations via the GitLens interactive settings editor

@@ -106,17 +110,30 @@
  • NEW + Adds + Checkout Commit (via Terminal) command ( + gitlens.terminalCheckoutCommit) to commit node(s) of the GitLens explorer + — closes + #463 +
    +
  • +
  • + NEW Adds a - gitlens.hovers.avatars setting to specify whether to show avatar images in hovers — closes - #432 thanks to - PR #441 by + gitlens.hovers.avatars setting to specify whether to show avatar images in hovers + — closes + #432 + thanks to + PR #441 + by Segev Finer
  • NEW Adds - gitlens.historyExplorer.avatars setting to specify whether to show avatar images instead of status icons in the + 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
  • @@ -129,6 +146,17 @@
  • IMPROVED + Improves performance of providing blame annotations, especially for large files (a ~33% improvement on some files) +
    +
  • +
  • + IMPROVED + Changes commit search by sha to jump directly to the commit (if one is found), rather than having to click through to the + commit +
    +
  • +
  • + IMPROVED Renames the GitLens History explorer to GitLens File History explorer for better clarity @@ -137,7 +165,8 @@
  • IMPROVED Changes the - GitLens File History explorer to always show the full file history even when reviewing revisions + GitLens File History explorer to always show the full file history even when reviewing + revisions
  • @@ -151,6 +180,18 @@
  • IMPROVED + Changes Rebase to Commit (via Terminal) command (gitlens.terminalRebaseCommit) + to apply to all commit node(s) of the GitLens explorer +
    +
  • +
  • + IMPROVED + Changes Reset to Commit (via Terminal) command (gitlens.terminalResetCommit) + to apply to all commit node(s) of the GitLens explorer +
    +
  • +
  • + IMPROVED Removes gitlens:activeIsTracked, gitlens:activeIsBlameable, @@ -162,57 +203,96 @@
  • FIXED Fixes - #436 — Copy to clipboard not working + #436 + — Copy to clipboard not working
  • FIXED Fixes - #442 — GitLens File History fails if name (or path) starts with + #442 + — GitLens File History fails if name (or path) starts with -
  • FIXED Fixes - #440 — Searching for commits with an empty query yields to no results anymore + #440 + — Searching for commits with an empty query yields to no results anymore
  • FIXED Fixes - #444 — GitLens custom viewlet icon slightly larger than standard + #444 + — GitLens custom viewlet icon slightly larger than standard
  • FIXED Fixes - #437 — Remove + #437 + — Remove --first-parent from git commands to show file history from merged in
  • FIXED Fixes - #252 — Cannot read property 'push' of undefined + #252 + — Cannot read property 'push' of undefined +
    +
  • +
  • + FIXED + Fixes + #451 + — "apply Changes" has discarded all my changes +
    +
  • +
  • + FIXED + Fixes + #449 + — Stop hiding explorers by default when in Zen mode +
    +
  • +
  • + FIXED + Fixes + #454 + — Search for string returns merge commits (unlike raw `git log -S`)
  • +
  • FIXED Fixes - #451 — "apply Changes" has discarded all my changes + #462 + — Source Control shortcut on macOS (⌃⇧G) shouldn't be overridden
  • FIXED Fixes - #449 — Stop hiding explorers by default when in Zen mode + #457 + — Displays the wrong username (You) — thanks to + PR #460 + by + Zyck
  • FIXED Fixes - #454 — Search for string returns merge commits (unlike raw `git log -S`) + #459 + — File blame annotation text overflow with letter spacing setting +
    +
  • +
  • + FIXED + Fixes issues with GitLens Welcome and the interactive settings editor with light themes
  • @@ -223,15 +303,15 @@
  • FIXED Fixes issue where the - Compare File with Previous Revision command wouldn't work properly when the file had been - renamed in some cases + Compare File with Previous Revision command wouldn't work properly when the file had + been renamed in some cases
  • FIXED Fixes issue where the - Compare File with Next Revision command wouldn't work properly when the file had been renamed - in some cases + Compare File with Next Revision command wouldn't work properly when the file had been + renamed in some cases
  • @@ -282,8 +362,8 @@ NEW Adds completely revamped heatmap annotations
    -

    The indicator's color, now customizable, will either be hot or cold based on the age of the - most recent change (cold after 90 days by default) — closes +

    The indicator's color, now customizable, will either be hot or cold based on the age of + the most recent change (cold after 90 days by default) — closes #419

    Cold Heatmap @@ -303,15 +383,17 @@ NEW Adds GitLab and Visual Studio Team Services icons to the remote nodes in the GitLens explorer — thanks to - PR #421 by + PR #421 + by Maxim Pekurin
  • NEW 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.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)
    @@ -319,36 +401,40 @@
  • NEW 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.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
  • NEW 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.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
  • FIXED Fixes - #400 — GitLens logging to debug console when debugging different extension + #400 + — GitLens logging to debug console when debugging different extension
  • FIXED Fixes - #409 — Literal $(ellipsis) inserted into commit QuickPick menu entry placeholder text + #409 + — Literal $(ellipsis) inserted into commit QuickPick menu entry placeholder text
  • FIXED Fixes - #415 — Branch names get mangled by color escapes — thanks to - PR #416 by + #415 + — Branch names get mangled by color escapes — thanks to + PR #416 + by Roy Ivy III
  • @@ -481,7 +567,8 @@ NEW Adds Close Repository command ( - gitlens.explorers.closeRepository) to repository and repository status nodes in the + gitlens.explorers.closeRepository) to repository and repository status nodes in + the GitLens explorer — closes (hides) the repository in the GitLens explorer
    @@ -489,7 +576,8 @@
  • NEW Adds clipboard support for Linux without requiring any external dependencies — thanks to - PR #394 by + PR #394 + by Cédric Malard
  • @@ -497,7 +585,8 @@ NEW 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 + gitlens.openFileInRemote) when the current branch has no upstream tracking branch + — closes #209
    @@ -556,101 +645,117 @@
  • FIXED Fixes - #366 — Running a GitLens command from a keybinding fails + #366 + — Running a GitLens command from a keybinding fails
  • FIXED Fixes - #155 — Navigating file diffs with + #155 + — Navigating file diffs with alt+, gets stuck
  • FIXED Fixes - #359 — Show changes of an added file in the first commit + #359 + — Show changes of an added file in the first commit
  • FIXED Fixes - #372 — Wrong URL to VSTS work item when using hash work item id in commit + #372 + — Wrong URL to VSTS work item when using hash work item id in commit
  • FIXED Fixes - #362 — Too many code lenses in postcss files + #362 + — Too many code lenses in postcss files
  • FIXED Fixes - #381 — Can't stash single files with older versions of Git + #381 + — Can't stash single files with older versions of Git
  • FIXED Fixes - #384 — Absolute dates not always honored in + #384 + — Absolute dates not always honored in GitLens Results explorer
  • FIXED Fixes - #385 — Wrong git command to delete remote branch + #385 + — Wrong git command to delete remote branch
  • FIXED Fixes - #400 — Reset TO commit also resets chosen one + #400 + — Reset TO commit also resets chosen one
  • FIXED Fixes - #399 — "Open x in Remote" commands aren't always available + #399 + — "Open x in Remote" commands aren't always available
  • FIXED Fixes - #397 — Error while opening the gitlens view using + #397 + — Error while opening the gitlens view using Open View command
  • FIXED Fixes - #391 — GitLens adds some settings in settings.json + #391 + — GitLens adds some settings in settings.json
  • FIXED Fixes - #343 — Can't show blame when VSCode starts on branch without upstream — thanks - to - PR #390 by + #343 + — Can't show blame when VSCode starts on branch without upstream — thanks to + PR #390 + by ryenus
  • FIXED Fixes - #392 — unable to contribute if default script shell is sh — thanks to - PR #393 by + #392 + — unable to contribute if default script shell is sh — thanks to + PR #393 + by Cédric Malard
  • FIXED Fixes more instances of - #295 and - #318 — Any error encountered during the search for repositories could cause GitLens - to die + #295 + and + #318 + — Any error encountered during the search for repositories could cause GitLens to die
  • @@ -666,7 +771,8 @@ FIXED Fixes bronze typo thanks to - PR #361 by + PR #361 + by Cory Forsyth
  • @@ -674,7 +780,8 @@ FIXED Fixes individually typo thanks to - PR #364 by + PR #364 + by Brett Cannon
    @@ -737,8 +844,8 @@
  • NEW Adds an indicator to the - GitLens explorer's branch history to mark the synchronization point between the local and - remote branch (if available) + GitLens explorer's branch history to mark the synchronization point between the local + and remote branch (if available)
    Branch upstream indicator
    @@ -763,8 +870,8 @@
  • NEW Adds new - gitlens.currentLine.scrollable setting to specify whether the current line blame annotation can be scrolled into view when - it is outside the viewport — closes + gitlens.currentLine.scrollable setting to specify whether the current line blame + annotation can be scrolled into view when it is outside the viewport — closes #149, #290, #265 @@ -785,13 +892,15 @@
  • FIXED Fixes - #314 — Toggle line annotation doesn't work properly + #314 + — Toggle line annotation doesn't work properly
  • FIXED Fixes - #310 — "via Terminal" commands need quoting around work directory + #310 + — "via Terminal" commands need quoting around work directory
  • @@ -857,15 +966,16 @@ IMPROVED Renames Compare Selected Ancestor with Working Tree command to - Compare Ancestry with Working Tree and removes the need to select a branch first, since all - compares are performed with the working tree — closes + Compare Ancestry with Working Tree and removes the need to select a branch first, since + all compares are performed with the working tree — closes #279
  • FIXED Fixes - #294 — Keyboard shortcuts will now default to + #294 + — Keyboard shortcuts will now default to chorded to avoid conflicts. Only affects new installs or if you remove the gitlens.keymap setting
    @@ -884,7 +994,9 @@
  • NEW Brand new interactive - settings editor — GitLens is easier than ever to customize to suit your needs + settings + editor + — GitLens is easier than ever to customize to suit your needs
    @@ -892,7 +1004,8 @@
  • NEW Brand new - website — check it out! + website — check it + out!
  • @@ -915,7 +1028,9 @@

    See the - release notes for the full set of changes + release + notes + for the full set of changes

    @@ -933,10 +1048,14 @@

    - GitLens is an - open-source extension for Visual Studio Code created by - Eric Amodio. While GitLens is generously offered to everyone free of charge, if you find - it useful please consider + GitLens is + an + open-source + extension for Visual Studio Code created by + Eric + Amodio + . While GitLens is generously offered to everyone free of charge, if you find it useful please + consider supporting it.

    @@ -958,42 +1077,60 @@ GitLens Results explorer to navigate and explore commits, histories, and searches, or visualize comparisons between branches, tags, commits, and more

  • authorship - code lens showing the most recent commit and # of authors to the top of files and/or - on code blocks
  • + code + lens + showing the most recent commit and # of authors to the top of files and/or on code + blocks +
  • an unobtrusive - current line blame annotation at the end of the line
  • + current + line blame annotation at the end of the line
  • on-demand - gutter blame annotations, including a heatmap, for the whole file + gutter + blame + annotations, including a heatmap, for the whole file
  • on-demand - gutter heatmap annotations to show how recently lines were changed, relative to all - the other changes in the file and to now (hot vs. cold) + gutter + heatmap + annotations to show how recently lines were changed, relative to all the other changes + in the file and to now (hot vs. cold)
  • detailed blame information accessible via hovers
  • on-demand - recent changes annotations to highlight lines changed by the most recent commit
  • + recent + changes + annotations to highlight lines changed by the most recent commit
  • a - status bar blame annotation showing author and date for the current line + status + bar blame annotation showing author and date for the current line
  • - commit search — by message, author, filename, commit id, or code changes
  • -
  • many powerful commands for exploring commits and histories, comparing and navigating revisions, - stash access, repository status, etc
  • + commit + search + — by message, author, filename, commit id, or code changes +
  • many powerful commands for exploring commits and histories, comparing and navigating + revisions, stash access, repository status, etc
  • and so much more
  • -

    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 - GitLens Settings editor, an interactive editor covering many of GitLens' powerful settings. - While for more advanced customizations, refer to the - GitLens settings docs +

    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 + GitLens + Settings + editor, an interactive editor covering many of GitLens' powerful settings. While for more + advanced customizations, refer to the + GitLens + settings docs and edit your - User Settings. + User + Settings + .

    @@ -1005,9 +1142,10 @@ I've been building GitLens in my spare time 1 - 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. + 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.

    Show Your Support ❤

    @@ -1020,16 +1158,21 @@ 😉

    - Become a Sponsor - Donations via PayPal - Donations via Cash App + Become + a Sponsor + Donations + via PayPal + Donations + via Cash App