Benjamin Christopher SimmondsandCopilot
d9637b3f2f
The V3 new-session onboarding personalizes its 3 prompt options with GitHub items, falling back to standard options. Telemetry from experiment f716301b showed 61% of impressions timed out with zero GitHub options, and the existing events could not measure partial success: `fallbackReason` was only 'none' when all 3 slots were GitHub, so 2 real issues logged identically to zero. Telemetry (additive; existing field names and values unchanged): - promptStrategy gains gitHubOptionCount, candidatesFound, lookupDurationMs, per-stage durations and outcomes, and timedOutStage. - promptOptionInteraction gains optionIndex and optionKindsShown, so per-option CTR is computable rather than confounded with availability. - Both gain a shared impressionId, replacing lossy DevDeviceId joins. - New 'noComposer' fallback reason splits the infra-bug meaning out of the overloaded 'noCandidate'. - Bounded categories and counts only: no titles, URLs, numbers, repository names or prompt text. Latency, without raising the 10s total budget: - Publish issue candidates before the linkage lookup, which only filters out issues that already have linked pull requests and so must never hide them. - Keep review-thread enrichment off the critical path; it produced the least picked option while being the most expensive stage. - Rebalance sub-budgets to 4000/1500/3000 so the concurrent chains fit. - Stream options into the composer: paint the standard options immediately and replace slots as lookups land, instead of blocking first paint on the lookup. INewSessionPromptOptionsController.resolve gains an optional progress callback that reports whether an update was rendered, so the composer can refuse late updates while the user is acting on the options and telemetry still describes what was actually shown. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Visual Studio Code - Open Source ("Code - OSS")
The Repository
This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, but we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.
Visual Studio Code
Visual Studio Code is a distribution of the Code - OSS repository with Microsoft-specific customizations released under a traditional Microsoft product license.
Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on the Visual Studio Code website. To get the latest releases every day, install the Insiders build.
Contributing
There are many ways in which you can participate in this project, for example:
- Submit bugs and feature requests, and help us verify them as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to new content.
If you are interested in fixing issues and contributing directly to the codebase, please see the document How to Contribute, which covers the following:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Upvote popular feature requests
- File an issue
- Connect with the extension author community on GitHub Discussions or Slack
- Follow @code and let us know what you think!
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter repositories are separate from each other. For a complete list, please visit the Related Projects page on our wiki.
Bundled Extensions
VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features extension provides rich language support for JSON.
Development Container
This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
-
For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command, which creates a Docker volume for better disk I/O on macOS and Windows.
- If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
-
For Codespaces, install the GitHub Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.
Docker / the Codespace should have at least 4 cores and 6 GB of RAM (8 GB recommended) to run a full build. See the development container README for more information.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.