microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2025-12-10 00:27:05 -06:00
Code Issues Packages Projects Releases 177 Wiki Activity
Page: Community Issue Tracking
Pages
Accessibility Guidelines Adopting Multi Root Workspace APIs Automated Issue Triaging Build Champion Build and run 32bit Code OSS on Windows Code Editor Roadmap Coding Guidelines Color customization color id changes Commit Signing Community Issue Tracking Contributor License Agreement Copilot Issues Cross Compiling for Debian Based Linux Custom eslint rules Dealing with Test Flakiness December Pre Release December Test Plan Design Goals Development Process Differences between the repository and Visual Studio Code Editor decorations & colors Endgame testing and verification Explain extension causes high cpu load Extension API guidelines Extension API process Feature Areas Feedback Channels File Watcher Internals File Watcher Issues Git & SCM Issues Home How to Contribute IME Test Insiders Release Notes Interactive Window Documentation Inventory of performance marks Issue Grooming Issue Tracking Issues Triaging Iteration Plans Keybinding Issues Known issues Lists And Trees Native Crash Issues Notebook Smoke Test Notebook documentation Notebook layout November Plan Performance Issues (old) Performance Issues Pointer Device & Touch support Publish vscode types Related Projects Release Process Removing Insiders Roadmap 2017 Roadmap 2018 Roadmap 2019 Roadmap 2020 Roadmap Roadmap‐2021‐2022 Running the Endgame Runtime debugging Sanity Check Screen Reader Test Search Issues Selfhosting on Windows WSL Semantic Highlighting Overview Setting Descriptions Smoke Test Source Code Organization Submitting Bugs and Suggestions Terminal Issues TypeScript Issues UX VS Code Speech Virtual Workspaces Working Copies Working with xterm.js Writing Test Plan Items Writing Tests [DEV] Perf Tools for VS Code Development [DEV] Programming advice and tips & tricks [WIP] Code Editor Design Doc [WIP] Design Checklist [WIP] Design Principles [dev perf] PerformanceError and unresponsive renderer telemetry
Clone
10
Community Issue Tracking
John Murray edited this page 2025-08-11 12:53:05 +01:00

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 /needsMoreInfo (or /needsPerfInfo for performance issues) and maybe explain what is missing:

    • Does it reproduce with all extensions disabled (--disable-extensions or Reload Window With Extensions Disabled)?
    • 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.

  • If a screenshot would be useful, mark it with /gifPlease.

  • 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.

  • If it is an issue with an extension from the Marketplace (i.e., not a built-in one), use /causedByExtension and optionally point the user to the repository where they can file the issue for the extension. For some extensions you can do this by using a specific response instead of /causedByExtension:

    • /extC
    • /extC#
    • /extC++
    • /extDocker
    • /extGo
    • /extJava
    • /extJavaDebug
    • /extJS
    • /extJupyter
    • /extLiveShare
    • /extPowershell
    • /extPython
    • /extTS

  • If it is a bug you can reproduce, /confirm it and add any additional info that might help the dev team reproduce it.

    • If it is thought to be a regression, get bonus points by using npx --yes @vscode/vscode-bisect@latest in conjunction with your repro steps to try and identify the commit which caused it.

  • If it is a bug you cannot reproduce, use /confirmationPending to label it and add any info that might help the author clarify the steps to reproduce.

  • If you know which team member should look at it, use /assign @XYZ.

  • If it is a question that is better asked on StackOverflow, use /question to label and close it as such.

Project Management

Contributing

Documentation

Want to contribute to this Wiki?

Fork it and send a pull request.