-
Notifications
You must be signed in to change notification settings - Fork 30.7k
Community Issue Tracking
Christof Marti edited this page Nov 9, 2018
·
9 revisions
Welcome, and thank you for your interest in contributing to VS Code!
We have started to involve 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
/needsMoreInfo
and maybe explain what is missing:- Does it reproduce with all extensions disabled (
--disable-extensions
orReload 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,
/confirm
it and add any additional info that might help the dev team reproduce it.
Project Management
- Roadmap
- Iteration Plans
- Development Process
- Issue Tracking
- Build Champion
- Release Process
- Running the Endgame
- Related Projects
Contributing
- How to Contribute
- Submitting Bugs and Suggestions
- Feedback Channels
- Source Code Organization
- Coding Guidelines
- Testing
- Dealing with Test Flakiness
- Contributor License Agreement
- Extension API Guidelines
- Accessibility Guidelines
Documentation