The queries use the GitHub search syntax. The list of possible issues is configurable with the setting githubIssues.queries, so if you work across multiple repositories, you can include queries for those issues. In Markdown files, issues complete as a Markdown link, and in other files, issues complete as a simple issue number ( #1234). In the Git commit textbox, you can format your issue completion with the githubIssues.issueCompletionFormatScm setting. To easily add this context, we have added completion suggestions for issues and users. VISUAL STUDIO CODE GITHUB CODEIssue context is typically needed in commit messages to reference an issue the commit resolves, within source code files, and in Markdown (such as a changelog). The VS Code proposed API has many developer references to make it obvious who's responsible for the proposals. We also often reference users in our codebase. VISUAL STUDIO CODE GITHUB FULLIssue hovers work on full issue URLs, issue comment URLs, issues referenced by number ( #1234), and issues referenced by owner/repository#1234 (for example Microsoft/vscode#1234). Now, by gaining this issue context through hovers, you don't need to break your flow to learn more. While linking gives a pointer to more information, to actually learn more you need to leave the editor. If you do a search for issue references in the VS Code repo, you'll see plenty of issues mentioned. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |