Releases: microsoft/vscode-pull-request-github
0.21.2
- Revert previous changes for proposed API changes since the minimum engine version is currently set to 1.50.0.
0.21.1
- Adopt latest proposed API changes.
0.21.0
Changes
-
GitHub permalinks in issue hovers for files that exist in your current workspace will be opened locally.
-
We are trying out a new "focused review" mode which changes the layout when you checkout a PR. You can try it with the
githubPullRequests.focusedMode
setting. -
Issue suggestions are now shown in code comment editors.
-
When you Start Working on an issue, it will be assigned to you if you permissions in the repository allow it.
-
Thanks to @rishab-pdx, the description page of the pull request now has an action to copy the link to the PR.
Notable fixes
-
Instead of showing two login buttons (one each in the Pull Requests and Issues views), we now show a login view.
-
Editor tab titles are now shortened to the file name when viewing diffs from a pull request, and are suffixed with
(Pull Request)
.
0.20.1
- Fixes loading the extension in VSCode Insider's 1.50
0.20.0
Changes
- Pull requests and issues now follows a multi-repo model. This means that if you have folders in your workspace from different repositories you'll see the issues and pull requests from the repositories at the same time. You can also have pull requests checked out from multiple repositories.
- There is new setting,
githubPullRequests.pullRequestDescription
, to control how the description is set when creating a pull request. By default, this uses the pull request template in the repository if it exists, but can also be changed to use the latest commit message, a custom message input at create time, or to ask which of these options to use. Thank you to @heaths for this feature!
Notable fixes
- GitHub Action based status checks are now rendered on the description page.
- Commenting on stale pull requests is better handled.
0.19.0
Changes
-
When you try to Start Working on Issue in a repository where you don't have permission to push, you now have the option to fork the repository. This flow will fork the repository and configure your remotes.
-
When attempting to push changes to a repository that you do not have permissions to push to, the extension will now prompt you to fork the repository and push to that instead.
-
Updated the version of @octokit/rest to ^18.0.0. This is was a big refactor, but should result in better performance.
Notable fixes
- The setting
githubIssues.workingIssueBranch
is deprecated in favor of the better namedgithubIssues.issueBranchTitle
. - The
githubIssues.issueBranchTitle
setting is now validated.
0.18.1
0.18.1
Changes
- Adopt latest authentication provider API changes
0.18.0
0.18.0
Changes
- The Issues view now shows the markdown card on hover.
- Label suggestions are provided in the new issue editor.
- Hovers work for issues formatted as
GH-123
. - The
githubIssues.workingIssueBranch
setting can take the new variable${sanitizedIssueTitle}
. - If you have uncommitted changes in your issue branch when you try to create a pull request, you'll be prompted to commit them.
- Closed issues in the Issues view use the closed icon.
- The Pull Requests and Issues views use the visually appealing welcome mechanism to display the Sign in button.
Notable fixes
0.17.0
Changes
- Improved display of labels in issue hovers by swapping out the existing svg version of the labels for a newly supported html version.
- When creating a GitHub permalink, we now try to pick the "best" remote if the currently opened repository has several remotes. The priority of remote is
upstream
,ups
,origin
, then other names. The first remote from that ordering which contains the same commit that the current branch is on will be used in the permalink. - Issue creation now better takes into account the file that you're coming from when you create an issue instead of only listening for repository change when a different repository is selected in the SCM view.
- The new issue editor now lets you edit the title, assignees, labels, and description.
- User and issue completions now only show in plaintext and in comments! No more noisy issue suggestions when you trigger suggest in code.
Notable fixes
- Issues shown in the completion suggestion are now deduped, even when the
githubIssues.queries
result in having the same issue twice (1800). - There is not longer a notification shown when running GitHub Issues: Copy GitHub Permalink (1787).
- Comments are removed when showing issue hovers (1763).
- The Issues view now has a loading state that matches the Pull Requests view.
- Better support in multiroot workspaces (1741).