Submitting Bugs and Suggestions

Submitting Bugs and Feature Requests

The Code project tracks issues and feature requests using the GitHub issue tracker for the vscode repository.

Search

First, please do a search to see if the issue or feature request has already exists. If it does and it is open, feel free to add more information that might be helpful in diagnosing or understanding the issue.

Writing Great Issues and Suggestions

The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. Consider the following:

• Version of Code
• Code that demonstrates the issue
• Description of what you expect to happen
• Animated GIFs
• Errors in the Dev Tools (Help | Toggle Developer Tools)

If you are submitting a feature request, please include the user scenario.

Don't feel bad if we can't reproduce the issue and ask for more information!

Workflow

When you submit an issue, here's what will happen.

We use Labels to track the status of suggestions or feature requests. You can expect to see the following:

• Empty

  Issues that have no label have not been looked at by a Code coordinator. You can expect to see them labelled within a few days of being logged.

• Bug

  Issues with the Bug label are considered to be defects. Once they have the Bug label, they'll either be assigned to a developer and assigned a milestone, or put in the Backlog milestone, indicating we know it's an issue but we don't know when we will fix it.

  The Backlog milestone is a good place to start if you're interested in making a contribution to Code.

• Feature Request

  We consider this issue to not be a bug, but rather a design change or feature of some sort.

• Everything Else

  Issues that are not bugs or suggestions will be labelled appropriately (Question, By Design, External, etc.) and closed.

Questions

Questions will be closed and be referred to Stack Overflow for Code questions.