GitHub Pull Requests for Visual Studio Code
Experimental conflict resolution for non-checked out PRs is available when enabled by the hidden setting "githubPullRequests.experimentalUpdateBranchWithGitHub": true
. This feature allows you to resolve conflicts in a PR without checking out the branch locally. The feature is still experimental and will not work in all cases.
There's an Accessibility Help Dialog that shows when "Open Accessibility Help" is triggered from the "Pull Requests" and "Issues" views.
All review action buttons will show in the Active Pull Request sidebar view when there's enough space.
The new auto
value for githubPullRequests.createDefaultBaseBranch
will use the upstream's default branch as the base branch for fork repositories.
Outdated comments now show a badge in the Comments view.
Colors for checks and Xs on PR page. https://github.com/microsoft/vscode-pull-request-github/issues/5754
Comment threads in the Comments view now have inline actions and context menu actions. Outdated comments have a "Diff Comment with HEAD" action which is particularly useful for understanding what changed on an outdated comment.
Thank You
review.openLocalFile
support triggering from the keyboard. PR #5840
There is an option to choose which email to associate a merge or squash commit with.
The setting githubPullRequests.labelCreated
can be used to configure the labels that are automatically added to PRs that are created.
When the cursor is in a comment widget input, the keybinding ctrl+k m
or (cmd+k m
on mac) can be used to insert a suggestion.
Video previews now show in the PR description.
The activity bar entry has been renamed from "GitHub" to "GitHub Pull Requests". The extension has been renamed from "GitHub Pull Requests and Issues" to "GitHub Pull Requests".
"Owner level" PR templates are now supported. This means that a PR template can be defined in the .github
repository of an organization or user and it will be used for all repositories owned by that organization or user which do not have a repository-specific PR template.
Projects can be added to a PR from the "Create" view. Projects can also be added to new issues.
Thank You
Issue queries shown in the "Issues" view can be grouped by repository and milestone using the new groupBy
property in the githubIssues.queries
setting.
"githubIssues.queries": [
{
"label": "Current",
"query": "assignee:alexr00 is:open sort:updated-desc milestone:\"February 2024\" sort:updated-desc",
"groupBy": [
"milestone",
"repository"
]
}
],
The setting githubPullRequests.createDefaultBaseBranch
can be used to set the default base branch when creating a PR. By default, the branch that the current branch was created from is used (so long as that branch exists on the remote). Setting repositoryDefault
will cause the repository's default branch to be used instead.
Added files are opened in a regular editor instead of a diff editor when viewing changes in a PR.
Merge commits are skipped when choosing a default PR title and description. This is to avoid the case where the merge commit message is used as the PR title and description.
GitHub permalinks in comments for a checked out PR can now be opened in VS Code instead of just taking you to the browser.
The base branch can be merged into a checked out PR branch from the Pull Request Description.
-The setting githubPullRequests.pullPullRequestBranchBeforeCheckout
also has new options to automatically fetch the base and merge it into the PR branch at checkout time.
Merge conflicts can be resolved from the Pull Request Description when the PR is checked out.
The hover on reactions now shows who left the reaction.
Issue templates are now available when creating an issue.
Setting "githubPullRequests.focusedMode": "multiDiff"
will open the multi-diff editor with all the files in the PR upon checkout.
Thank You
Merge queues are now supported in the PR description and create view.
The new setting "githubPullRequests.allowFetch": false
will prevent fetch
from being run.
Projects are now cached for quicker assignment from the PR description.
Merge commit message uses the message configured in the GitHub repository settings.
Clicking on the filename of a comment in the PR description will open at the correct line.
The repository name is shown in the "Changes in PR" view when there are PRs from multiple repositories shown in the view.
Thank You
githubIssues.useBranchForIssues
setting description as markdown (fix #5506) PR #5508
Integration with the GitHub Copilot Chat extension provides PR title and description generation.
"Project" can be set from the PR description webview.
Pull requests checked out using the GitHub CLI (gh pr checkout
) are now recognized.
The new "none"
value for the setting "githubPullRequests.pullRequestDescription"
will cause the title and description of the Create view to be empty by default.