@ -4,7 +4,7 @@ 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]
## [11.2.0] - 2021-02-02
### Added
@ -12,10 +12,10 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
- **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
- Adds rebase and/or merge conflict status when applicable to the _File History_ and _Line History_ views
- **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
- Adds status indicator colors to pull request icons in GitLens views
- Adds a new _Quick Open File History_ command to all places where _Open File History_ already exists — closes [#1156](https://github.com/eamodio/vscode-gitlens/issues/1156)
- Adds the _Add Remote_ command to the branch status in the _Branches_, _Commits_, and _Repositories_ views when there are no Git remotes configured
@ -264,7 +264,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
- any associated pull request — shows any opened pull request associated with the current branch
---
@ -297,6 +299,8 @@ The Repositories view lists opened Git repositories, and additionally provides,
- **Up to date with <remote>**— shown when the current branch is up to date with the upstream remote
- **Changes to pull from <remote>**— lists all of the unpulled commits and all of the files changed in them, 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 unpublished commits and all of the files changed in them, when the current branch has 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
- any associated pull request — [optionally](#repositories-view-settings- 'Jump to the Repositories view settings') shows any opened pull request associated with the current branch
- **Commits**— [optionally](#repositories-view-settings- 'Jump to the Repositories view settings') shows the current branch commits, similar to the [Commits view](#commits-view- 'Commits view')
- **Branches**— [optionally](#repositories-view-settings- 'Jump to the Repositories view settings') shows the local branches, similar to the [Branches view](#branches-view- 'Branches view')
@ -325,6 +329,7 @@ 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
"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",
Eric Amodio
4 years ago