Document your code
Every project on GitHub comes with a version-controlled wiki to give your documentation the high level of care it deserves. It’s easy to create well-maintained, Markdown or rich text documentation alongside your code.
Sign up for free See pricing for teams and enterprisesCommunity Issue Tracking
Welcome, and thank you for your interest in contributing to VS Code!
We have started to involve the most active members of the community in our issue tracking to better load-balance the work and allow for quicker feedback on new issues. The following are the guidelines and extra powers for our community trackers:
Check our "inbox" for new issues and see if any can be helped with:
- If it needs more information, mark it as such with
/needsMoreInfoand maybe explain what is missing:- Does it reproduce with all extensions disabled (
--disable-extensionsorReload Window With Extensions Disabled)? - For performance issues ask them to follow https://github.com/Microsoft/vscode/wiki/Performance-Issues.
- For native crashes ask them to follow https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues.
- For non-English reports, ask them to describe the issue in English and suggest a machine translator.
- Does it reproduce with all extensions disabled (
- If it is a duplicate of an existing issue, mark it as such with
/duplicate #12345.- Optionally let the bot search for duplicates (if it hasn't done so already) with
/findDuplicates.
- Optionally let the bot search for duplicates (if it hasn't done so already) with
- If it is a bug you can reproduce,
/confirmit and add any additional info that might help the dev team reproduce it. - If it is a bug you cannot reproduce, use
/confirmationPendingto label it and add any info that might help the author clarify the steps to reproduce. - If it is a question that is better asked on StackOverflow, use
/questionto label and close it as such.
