0.5.1 **Changes** - Fix description not displaying after creating a pull request [#1041](https://github.com/Microsoft/vscode-pull-request-github/pull/1041) 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](https://github.com/Microsoft/vscode-pull-request-github/issues/46) - Display reviewers on the description page, and support adding and removing them [#412](https://github.com/Microsoft/vscode-pull-request-github/issues/412) - Support adding and removing labels from the description page [#933](https://github.com/Microsoft/vscode-pull-request-github/issues/933) - Fix [#936](https://github.com/Microsoft/vscode-pull-request-github/issues/936), pending review not correctly detected in "Changes in Pull Request" tree - Fix [#929](https://github.com/Microsoft/vscode-pull-request-github/issues/929), description textarea not cleared when approving or requesting changes - Fix [#912](https://github.com/Microsoft/vscode-pull-request-github/issues/912), approving the PR scrolls to the top of the page **New settings** - `githubPullRequests.showInSCM` can be used to configure where the `GitHub 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](https://github.com/Microsoft/vscode-pull-request-github/pull/946) by @IllusionMH - Fix LGTM.com alerts [#948](https://github.com/Microsoft/vscode-pull-request-github/pull/948) by @samlanning 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](https://github.com/Microsoft/vscode-pull-request-github/pull/773) - Add an inline action to open the description to the side [#310](https://github.com/Microsoft/vscode-pull-request-github/issues/310) - Add refresh button to the description page [#771](https://github.com/Microsoft/vscode-pull-request-github/pull/771) - Improve performance of checkout by minimally fetching data and lazily loading [#796](https://github.com/Microsoft/vscode-pull-request-github/pull/796) - Update the styling of the description page [#763](https://github.com/Microsoft/vscode-pull-request-github/pull/763) - Support navigating to a file from the description page [#750](https://github.com/Microsoft/vscode-pull-request-github/pull/750) - Linkify issue references on the description page [#566](https://github.com/Microsoft/vscode-pull-request-github/issues/566) - Show user's role (collaborator, contributor, etc.) by comments on the description [#303](https://github.com/Microsoft/vscode-pull-request-github/issues/303) - Support starting, deleting, and finishing a complete review [#546](https://github.com/Microsoft/vscode-pull-request-github/issues/546) - Allow selecting the merge method on the description page [#826](https://github.com/Microsoft/vscode-pull-request-github/pull/826) - Autocompletions for usernames within editor comments [#842](https://github.com/Microsoft/vscode-pull-request-github/pull/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 for `upstream` and `origin` 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`, or `squash`) to select by default, both on the description page and when using the `Merge Pull Request` command. This is set to `merge` by default. **Thank You** * Fix log output [PR #804](https://github.com/Microsoft/vscode-pull-request-github/pull/804) by @Ikuyadeu * Update setting description to use non deprecated key [PR #916](https://github.com/Microsoft/vscode-pull-request-github/pull/916) by @mkonikov 0.3.2 - Honor the new `git.openDiffOnClick` setting [#753](https://github.com/Microsoft/vscode-pull-request-github/pull/753) - Prompt to stage all changes when running the suggest changes with nothing staged [#744](https://github.com/Microsoft/vscode-pull-request-github/pull/744) - Add an inline "Open File" action in the "Changes in Pull Request" tree and match styling of git changes [#738](https://github.com/Microsoft/vscode-pull-request-github/pull/738) - Display the full file path using the tree item's description, matching other views [#730](https://github.com/Microsoft/vscode-pull-request-github/issues/730) - Parse auth callback state parameter on client side instead of mkaing a request to the auth server [#715](https://github.com/Microsoft/vscode-pull-request-github/pull/715) - Fix [#735](https://github.com/Microsoft/vscode-pull-request-github/issues/735), ensure correct head parameter is used when creating PR - Fix [#727](https://github.com/Microsoft/vscode-pull-request-github/issues/727), make sure review state is always cleared when switching branches - Fix [#728](https://github.com/Microsoft/vscode-pull-request-github/issues/738), keep description page data up to date when updating title and description 0.3.1 - Add status check information on PR description page [#713](https://github.com/Microsoft/vscode-pull-request-github/pull/713) - Add button for creating a pull request on PR tree view [#709](https://github.com/Microsoft/vscode-pull-request-github/pull/709) - Add "Suggest Edit" command [#688](https://github.com/Microsoft/vscode-pull-request-github/pull/688) - Fix [#689](https://github.com/Microsoft/vscode-pull-request-github/issues/689), by [@JefferyCA], do not render markdown block comments - Fix [#553](https://github.com/Microsoft/vscode-pull-request-github/issues/553), don't prevent checkout when there are unrelated working tree changes - Fix [#576](https://github.com/Microsoft/vscode-pull-request-github/issues/576), handle GitHub enterprise behind a SSO wall 0.3.0 **Breaking Changes** - From 0.3.0, you at least need VSCode 1.30 (including Insiders) to install and run the extension. **Thank You** * [Jeffrey (@JeffreyCA)](https://github.com/JeffreyCA) * Correct timestamp format [PR #686](https://github.com/Microsoft/vscode-pull-request-github/pull/686) * Render Markdown line breaks as
[PR #679](https://github.com/Microsoft/vscode-pull-request-github/pull/679) * Support absolute and relative timestamps [PR #644](https://github.com/Microsoft/vscode-pull-request-github/pull/644) 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](https://github.com/Microsoft/vscode-pull-request-github/issues/107) - Fix [#110](https://github.com/Microsoft/vscode-pull-request-github/issues/110), by [@JeffreyCA], add hyperlinks to timestamps - Fix [#624](https://github.com/Microsoft/vscode-pull-request-github/issues/624), by [@JeffreyCA], improve comment header wording - Fix [#568](https://github.com/Microsoft/vscode-pull-request-github/issues/568), by [@jerrymajewski], show author information in PR tooltip - Fix [#543](https://github.com/Microsoft/vscode-pull-request-github/issues/543), by [@malwilley], preserve description page scroll position when focus changes - Fix [#587](https://github.com/Microsoft/vscode-pull-request-github/issues/587), by [@mmanela], show correct error message for empty comment case - Migrate hosts setting to `githubPullRequests` namespace, by [@wyze] - Fix [#573](https://github.com/Microsoft/vscode-pull-request-github/issues/573), provide auth fallback when protocol handler fails **Breaking Changes** - From 0.2.0, you at least need VSCode 1.28 to install and run the extension. **Fixes** - Fix [#565](https://github.com/Microsoft/vscode-pull-request-github/issues/565), inline links in description page. - Fix [#531](https://github.com/Microsoft/vscode-pull-request-github/issues/531) by [@wyze](https://github.com/wyze), state is incorrectly shown as Closed when it should be Merged - Fix [#273](https://github.com/Microsoft/vscode-pull-request-github/issues/273), support ssh remotes. - Fix [#537](https://github.com/Microsoft/vscode-pull-request-github/issues/537) by [@justinliew](https://github.com/justinliew), show pull request id in title. - Fix [#491](https://github.com/Microsoft/vscode-pull-request-github/issues#491) by [@shatgupt](https://github.com/shatgupt), allow vertical resizing of comment box. - Fix [#319](https://github.com/Microsoft/vscode-pull-request-github/issues#319), improve keyboard focus. - Fix [#352](https://github.com/Microsoft/vscode-pull-request-github/issues/352) by [@Ikuyadeu](https://github.com/Ikuyadeu), support merging pull request - Fix [#464](https://github.com/Microsoft/vscode-pull-request-github/issues/464) by [@wyze](https://github.com/wyze), show labels on PR description - Fix [#562](https://github.com/Microsoft/vscode-pull-request-github/issues/562) by [@emtei](https://github.com/emtei), prevent PR creation date collision with subtitle 0.1.7 - Fix for native promise polyfill removal from VSCode extension host in Insiders 1.29 0.1.6 - Fix for [#500](https://github.com/Microsoft/vscode-pull-request-github/issues/500) and [#440](https://github.com/Microsoft/vscode-pull-request-github/issues/440), more lenient remote parsing - Fix for [#383](https://github.com/Microsoft/vscode-pull-request-github/issues/383), move to github.com domain for the authentication server - Fix for [#498](https://github.com/Microsoft/vscode-pull-request-github/issues/498), make sure comments gets updated on refresh event - Fix for [#496](https://github.com/Microsoft/vscode-pull-request-github/issues/496), linkify urls on the description page - FIx for [#507](https://github.com/Microsoft/vscode-pull-request-github/issues/507), loosen scope restrictions for older version of GitHub Enterprise 0.1.5 - Fix for [#449](https://github.com/Microsoft/vscode-pull-request-github/issues/449), authentication blocked when `docs-article-templates` extension is installed - Fix for [#429](https://github.com/Microsoft/vscode-pull-request-github/issues/429), avoid unneccessary refreshes of the tree view 0.1.4 - Do not ship `.vscode-test/**` files 0.1.3 - Fix for [#382](https://github.com/Microsoft/vscode-pull-request-github/issues/382), authentication on enterprise servers without a `/rate_limit` path - Fix for [#419](https://github.com/Microsoft/vscode-pull-request-github/issues/419), improve parsing of git remotes and show a warning if parse fails 0.1.2 - Fix for [#395](https://github.com/Microsoft/vscode-pull-request-github/issues/395), tree view not shown when the extension failed to parse a remote - [#399](https://github.com/Microsoft/vscode-pull-request-github/issues/399), use `badge.foreground` color for PR status badge - Fix for [#380](https://github.com/Microsoft/vscode-pull-request-github/issues/380), HTML content in diff on the overview was unescaped - Fix for [#375](https://github.com/Microsoft/vscode-pull-request-github/issues/375), appropriately fetch more changed files in the tree view