Releases: microsoft/vscode-pull-request-github
0.8.0
Changes
Bug fixes
- Do not show commands before extension has fully activated #1198
- Description page is blank after 0.7.0 upgrade #1175
- Change "wants to merge" text when viewing merged PR #1027
- Correct text alignment in merged timeline events #1199
- Update UI after adding reviewers or labels #1191
- Update PR details after merge #1183
- Display a message before opening file diffs in the browser #442, thank you @malwilley!
- Swap order of PR branch and target branch #784
0.7.0
0.6.0
0.5.0
0.5.0
Breaking Changes
- From 0.5.0, you at least need VSCode 1.32 to install and run the extension.
Changes
- Add support for reacting to comments #46
- Display reviewers on the description page, and support adding and removing them #412
- Support adding and removing labels from the description page #933
- Fix #936, pending review not correctly detected in "Changes in Pull Request" tree
- Fix #929, description textarea not cleared when approving or requesting changes
- Fix #912, approving the PR scrolls to the top of the page
New settings
githubPullRequests.showInSCM
can be used to configure where theGitHub Pull Requests
tree is shown, either the new GitHub viewlet or
the SCM viewlet where it was before. By default, the tree is shown in the GitHub viewlet.
Thank You
- Disable not available merge methods #946 by @IllusionMH
- Fix LGTM.com alerts #948 by @samlanning
0.4.0
0.4.0
Breaking Changes
- From 0.4.0, you at least need VSCode 1.31 to install and run the extension.
Changes
- Display mergeability on PR description page #773
- Add an inline action to open the description to the side #310
- Add refresh button to the description page #771
- Improve performance of checkout by minimally fetching data and lazily loading #796
- Update the styling of the description page #763
- Support navigating to a file from the description page #750
- Linkify issue references on the description page #566
- Show user's role (collaborator, contributor, etc.) by comments on the description #303
- Support starting, deleting, and finishing a complete review #546
- Allow selecting the merge method on the description page #826
- Autocompletions for usernames within editor comments #842
As part of this release, we have begun adopting GitHub's GraphQL API in some places to support new features and improve performance. The reviews feature and linkifying of issue references depend on the GraphQL API. This API is not available for GitHub Enterprise, so please note that these features will not be available for those projects.
New settings
githubPullRequests.remotes
can be used to configure what remotes pull requests should be displayed from. By default, the extension will look forupstream
andorigin
remotes
by convention and fetch from these, or will fetch from any other remotes if these are not present.githubPullRequests.defaultMergeMethod
specifies which merge method (merge
,rebase
, orsquash
) to select by default, both on the description page and when using theMerge Pull Request
command.
This is set tomerge
by default.
Thank You
0.3.2
0.3.2
- Honor the new
git.openDiffOnClick
setting #753 - Prompt to stage all changes when running the suggest changes with nothing staged #744
- Add an inline "Open File" action in the "Changes in Pull Request" tree and match styling of git changes #738
- Display the full file path using the tree item's description, matching other views #730
- Parse auth callback state parameter on client side instead of mkaing a request to the auth server #715
- Fix #735, ensure correct head parameter is used when creating PR
- Fix #727, make sure review state is always cleared when switching branches
- Fix #728, keep description page data up to date when updating title and description
0.3.1
- Add status check information on PR description page #713
- Add button for creating a pull request on PR tree view #709
- Add "Suggest Edit" command #688
- Fix #689, by [@JeffreyCA], do not render markdown block comments
- Fix #553, don't prevent checkout when there are unrelated working tree changes
- Fix #576, handle GitHub enterprise behind a SSO wall
0.2.3
- Fix [#607], read
~/.ssh/config
to resolve hosts - Fix [#572], by [@yoh1496], add support for GitHub Enterprise behind a proxy
- Fix [#658], ensure correct button enablement when reloading pending comment from cache
- Fix [#649], make sure selecting a different folder is responsive after adding it to the workspace
0.2.2
- Add support for editing and deleting comments #107
- Fix #110, by [@JeffreyCA], add hyperlinks to timestamps
- Fix #624, by [@JeffreyCA], improve comment header wording
- Fix #568, by [@jerrymajewski], show author information in PR tooltip
- Fix #543, by [@malwilley], preserve description page scroll position when focus changes
- Fix #587, by [@mmanela], show correct error message for empty comment case
- Migrate hosts setting to
githubPullRequests
namespace, by [@wyze] - Fix #573, provide auth fallback when protocol handler fails
0.2.1
Noteworthy
Telemetry opt-out setting is now named under namespace github
to help differentiate itself from VSCode or other extension's telemetry opt setting. Now it's named as githubPullRequests.telemetry.enabled
, we still support telemetry.optout
but it will be deprecated in the future.
Fixes