bc2ac764dd
* sessions: do not force-open managed tabs when opening a file in single-pane layout Rework the single-pane managed docked tabs (Changes + Files placeholder) so they are only opened into an *empty* editor group on a view-open trigger, removing the fragile dismissal bookkeeping and aux-bar-visibility inference. - Add layout-service events `onDidRevealSidePane` (side pane goes fully hidden -> visible) and `onDidEndSessionLayoutRestore` (restore epoch settles) and drive the managed-tabs strategy off named triggers A-D. - Open default tabs only when the group is empty, so closing a managed tab sticks and closing a file no longer re-forces the tabs open / leaves the side pane un-closable. - Ensure Changes (opened active) on new-session submit; ensure all docked inputs on a details-only reveal. - Scope pending reconcile intents to their session so a superseded reconcile cannot leak its intent onto a switched-to session. - Gate responsive sessions-list auto-collapse on small windows (<= 1800px). - Only collapse editors on a details-only hide (aux still visible), not when the whole side pane closes. - Tests + docs (SINGLE_PANE_SCENARIOS.md, sessions SKILL.md) updated. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * sessions: address CCR review feedback on single-pane managed tabs - Guard the Files-tab tidy on onWillOpenEditor: resolve the event group via mainPart.getGroup and skip re-activations (already-open editors) and non-main-part groups, so selecting/closing-to-reveal an existing file no longer removes a user-added Files tab. - Open the submit Changes tab with preserveFocus so activating it for detail mapping never steals focus from the just-submitted chat. - Remove the now-dead internallyClosingEditors bookkeeping from the coordinator and both docked-tab strategies (no readers after dismissal tracking was removed). - Trim the SinglePaneManagedTabsStrategy class JSDoc to the ownership contract. - Tests: model production onWillOpenEditor ordering (fire before insert) and add a re-activation case; add onDidRevealSidePane transition assertions. - Docs: fix stale/nonexistent API references in the sessions SKILL.md pitfalls. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- 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 Visual Studio Code's 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 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 code base, 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.