Linking to issues in source code is a normal part of our workflow, especially when there's some logic that's difficult to understand or when there's a //TODO comment that needs action. We do want to make connections that aren't already there. We don't want to reinvent UI that GitHub already does well. For example, giving more context for an issue in a code comment is part of that goal, but adding full issue management into VS Code doesn't fit as well. Instead, our goal was to bring issues into the inner development loop in a flexible way. It was important that we not prescribe overly specific workflows. By working with our own extension API, we ensure the API has the features that extension authors need, and other repository providers can implement similar integration. Instead, we will recommend the extension when we detect that a user's open repository uses GitHub. We did not want to add GitHub functionality directly to the core VS Code editor because there are many source control options. Issues and pull requests often go hand in hand, so including them in the same GitHub Pull Requests and Issues extension was a logical step as much of the same GitHub API is needed for both issues and pull requests.

Starting with VS Code version 1.45, this new support to move the issues and source code closer together will be available in the GitHub Pull Requests and Issues extension (formerly named GitHub Pull Requests). This addition complemented the GitHub Pull Request work we announced over a year ago.

Given how important issues are to our team and other GitHub projects, we wanted to add GitHub issues integration to VS Code. From our detailed iteration plans to individual bugs, we track everything as GitHub issues.

Node.js Development with Visual Studio Code and Azureīy Alex Ross, the Visual Studio Code team, we use GitHub issues to track all of our work.

Moving from Local to Remote Development.

Visual studio code and github