GitHub Pull Requests for Visual Studio Code
MIT License
Review and manage your GitHub pull requests and issues directly in VS Code
This extension allows you to review and manage GitHub pull requests and issues in Visual Studio Code. The support includes:
It's easy to get started with GitHub Pull Requests for Visual Studio Code. Simply follow these steps to get started.
githubPullRequests.remotes
setting, by default the extension will look for PRs for origin
and upstream
. If you have different remotes, add them to the remotes list.Check out https://www.youtube.com/watch?v=LdSwWxVzUpo for additional getting started tips!
There are several settings that can be used to configure the extension.
As mentioned above, githubPullRequests.remotes
is used to specify what remotes the extension should try to fetch pull requests from.
To customize the pull request tree, you can use the githubPullRequests.queries
setting. This setting is a list of labels and search queries which populate the categories of the tree. By default, these queries are "Waiting For My Review", "Assigned To Me", and "Created By Me". An example of adding a "Mentioned Me" category is to change the setting to the following:
"githubPullRequests.queries": [
{
"label": "Waiting For My Review",
"query": "is:open review-requested:${user}"
},
{
"label": "Assigned To Me",
"query": "is:open assignee:${user}"
},
{
"label": "Created By Me",
"query": "is:open author:${user}"
},
{
"label": "Mentioned Me",
"query": "is:open mentions:${user}"
}
]
Similarly, there is a setting to configure your issues queries: githubIssues.queries
.
Queries use GitHub search syntax.
To view additional settings for the extension, you can open VS Code settings and search for "github pull requests".
This extension is still in development, so please refer to our issue tracker for known issues, and please contribute with additional information if you encounter an issue yourself.
See our wiki for our FAQ.
If you're interested in contributing, or want to explore the source code of this extension yourself, see our contributing guide, which includes: