GitHub Pull Requests for Visual Studio Code
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE
.readme
.vscode
documentation/images
preview-src
resources/icons
src
.gitignore
.vscodeignore
CHANGELOG.md
LICENSE
README.md
ThirdPartyNotices.txt
ci.js
gulpfile.js
package.json
package.nls.json
tsconfig.json
tslint.json
webpack.config.js
yarn.lock

README.md

Review and manage your GitHub pull requests directly in VS Code

This extension allows you to review and manage GitHub pull requests in Visual Studio Code. The support includes:

  • Authenticating and connecting VS Code to GitHub.
  • Listing and browsing PRs from within VS Code.
  • Reviewing PRs from within VS Code with in-editor commenting.
  • Validating PRs from within VS Code with easy checkouts.
  • Terminal integration that enables UI and CLIs to co-exist.

Demo

Getting Started

It's easy to get started with GitHub Pull Requests for Visual Studio Code. Simply follow these steps to get started.

  1. Make sure you have VSCode version 1.27.0 or higher.
  2. Download the extension from the marketplace.
  3. Reload VS Code after the installation (click the reload button next to the extension).
  4. Open your desired GitHub repository.
  5. Go to the SCM Viewlet, and you should see the GitHub Pull Requests treeview. On the first load, it will appear collapsed at the bottom of the viewlet.
  6. A notification should appear asking you to sign in to GitHub; follow the directions to authenticate.
  7. You should be good to go!

Issues

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.

Questions? Authentication? GitHub Enterprise?

See our wiki for our FAQ.

Contributing

If you're interested in contributing, or want to explore the source code of this extension yourself, see our contributing guide, which includes: