Releases: microsoft/vscode-pull-request-github
Releases · microsoft/vscode-pull-request-github
0.11.1
0.11.0
Changes
- Add support for deleting a PR after close or merge #350
- Update GraphQL timeline event query
- Update dependencies
Bug fixes
- Fix formatting of GitHub errors #1298
- Show error when user doesn't have permission to push to remote #1299
- Remove usage of rootPath and fix suggested edits #1312
- Disable 'Checkout' and 'Exit Review Mode' buttons while actions are in progress #1312
- Calculate unique branch name for PRs from forks #1294
- Fix 'Error: No matching file found' problem when adding comments #1308
- Initialize extension with repository that is currently selected in the source control view #1330
- Handle error on unshallow #1328
0.10.0
Changes
- Use pull request template when creating PR #798
- Improvements to pull request tree display message when loading or not signed in (#1269)(#1269)
- Change telemetry library to application insights [#1264)(https://github.com//issues/1264)
- Update icons to match new VSCode icon style (#1261)(#1261)
- Update dependencies
Bug fixes
- Set a default array for
githubPullRequests.remotes#1289 - Fix spacing between textbox and buttons on description page #1287
- Fix updates to comment thread cache when creating the first comment in a thread #1282
- Fix updates to outdated comments (#1279)[https://github.com//issues/1279]
- Ensure comment commands are limited to GitHub Pull Request comment widgets #1277
- Fix error when trying to add reviewers on description page #1181
- Enable removing a label on description page #1258
Thank You
0.9.1
0.9.0
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.showInSCMcan be used to configure where theGitHub Pull Requeststree 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.remotescan be used to configure what remotes pull requests should be displayed from. By default, the extension will look forupstreamandoriginremotes
by convention and fetch from these, or will fetch from any other remotes if these are not present.githubPullRequests.defaultMergeMethodspecifies which merge method (merge,rebase, orsquash) to select by default, both on the description page and when using theMerge Pull Requestcommand.
This is set tomergeby default.
Thank You