Weekly GitHub Report for Vscode: May 19, 2025 - May 26, 2025 (12:02:15)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
Released on March 12, 2025, this update for Visual Studio Code focuses on resolving issues identified in the February 2025 Recovery 2 milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
[Linux] MCP servers which require
nodeornpxcommand don't start up in fish shell: This issue involves a bug where MCP servers that require thenodeornpxcommand fail to start in the fish shell on Linux, despite these commands being available in the PATH by default. The error messages indicate that the system cannot find thenodecommand, and the user is unsure about the shell context in which the local process is spawned.- The comments discuss troubleshooting steps, including setting the log level to trace and sharing logs, which reveal a potential misconfiguration with bash. The user initially thought enabling a setting for fish shell integration in VS Code resolved the issue, but later realized it did not. The problem seems related to how VS Code resolves the shell environment when launched from a UI element versus a terminal, and there is a discussion about the PATH variable and default shell detection.
- Number of comments this week: 11
-
Wanted: Simple way to entirely disable copilot: This issue is about a user requesting a straightforward method to completely disable GitHub Copilot in Visual Studio Code, as their workplace prohibits the use of AI agents, and they are concerned about inadvertently enabling it due to persistent prompts. The user is seeking a future-proof solution that can be configured in
settings.jsonto prevent any AI-related features from appearing, as they have experienced unwanted prompts despite not having the Copilot extension installed.- The comments discuss various attempts to disable Copilot, including uninstalling extensions and modifying settings, but the user clarifies that they are still receiving prompts to enable AI features. Suggestions are provided to adjust specific settings in
settings.jsonand create anextensions.jsonfile to block recommendations, which the user implements with partial success. The discussion highlights the difficulty of automating these configurations due to non-settings.jsonbased storage, and a request is made for a comprehensive setting to disable all AI-related features in VS Code. - Number of comments this week: 9
- The comments discuss various attempts to disable Copilot, including uninstalling extensions and modifying settings, but the user clarifies that they are still receiving prompts to enable AI features. Suggestions are provided to adjust specific settings in
-
Facing many issues with dev containers: This issue is about a user experiencing multiple problems with dev containers while using Windows 11, Docker, and VSCode, particularly when working with the Python FastAPI framework. The user reports difficulties with the lack of an interactive mode in dev containers, slow restart times, disconnection issues with VSCode, and problems with extensions like Pylance not being installed correctly.
- The comments discuss various suggestions and solutions, including running FastAPI from the VSCode terminal and modifying the container's entrypoint to keep it running. The user implements a solution by creating a separate
docker-compose-dev.ymlfile to address the interactive mode issue. However, the problem with the Pylance extension persists, with suggestions to check for conflicts with other extensions and review the output logs for further troubleshooting. - Number of comments this week: 7
- The comments discuss various suggestions and solutions, including running FastAPI from the VSCode terminal and modifying the container's entrypoint to keep it running. The user implements a solution by creating a separate
-
[UriError]: Scheme contains illegal characters: This issue reports a bug in Visual Studio Code where attempting to open certain URLs using the
vscode.Uri.parsemethod results in a "[UriError]: Scheme contains illegal characters" error, despite the URLs being correctly formatted. The problem seems to be related to the management of trusted domains, where only specific URLs like 'https://github.com/' work without error, while others require adjustments in the trusted domains settings to function properly.- Multiple users report experiencing the same error across different extensions and platforms, indicating a broader issue with the trusted domains configuration in VS Code. One user suggests a workaround by modifying the trusted domains list, which resolves the issue for them, while another user highlights that the error message is unclear and requests a fix from the development team.
- Number of comments this week: 6
-
Unbearable lag - Markdown language basics builtin plugin: This issue reports a significant lag experienced when editing large markdown files in Visual Studio Code with the Markdown language basics builtin plugin enabled, which does not occur when the plugin is disabled. The user provides a video demonstration of the lag and specifies that the problem arises during general editing tasks such as pasting text and invoking autocomplete.
- The comments discuss attempts to reproduce the issue, with one user unable to confirm the problem on a different setup. The original poster adds a video for clarity and mentions that disabling the plugin resolves the issue. There is a suggestion to test with the latest insiders build, but the original poster faces installation issues. Eventually, the original poster upgrades their flatpak version and confirms the issue persists.
- Number of comments this week: 5
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request for Visual Studio Code to support the generation and display of markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request highlights the need for an option to render markdown generated by code cells, allowing for dynamic titles and content to be displayed in the output, enhancing the functionality and user experience in VS Code.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue describes a bug in Visual Studio Code where using a
vscode://link with the parameters?new-windowor?reuse-windowdoes not function as expected, as it hijacks the existing window instead of opening a new one. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, resulting in the disconnection from the current server and replacement of the window with the new server's connection. ${userHome}in a task command creates bad paths: This issue involves a problem with the${userHome}variable in a task command within atasks.jsonfile, which creates incorrect paths when the task type is set to "process" instead of "shell". The incorrect path format results in an error indicating that the terminal process could not be started because the path to the executable shell file does not exist, whereas using${env:USERPROFILE}instead of${userHome}resolves the issue by generating a correct path.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where characters typed in a terminal window, when moved to a floating window during a remote connection, do not appear in real time if the main window is minimized. The characters only display once the main window is restored, suggesting a potential "sleep" state in the remote connection that prevents real-time updates in the terminal.
- How to wipe "code tunnel" authentication on uninstall?: This issue addresses the challenge of removing stale authentication information associated with the "code tunnel" feature in Visual Studio Code, which persists even after uninstalling the service and deleting the relevant directories. The user reports that despite following expected procedures to clear authentication tokens, the system fails to prompt for new authentication, leading to authorization errors and setup difficulties.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 197
Summarized Issues:
- Visual Studio Code Performance Issues: Visual Studio Code users have reported various performance issues, including significant slowdowns, application freezes, and lag during specific operations. These problems are often linked to recent updates, specific extensions, or system configurations, and users have sought solutions such as disabling extensions or downgrading to previous versions to mitigate the issues.
- GitHub Copilot and AI Integration Issues: Users have encountered various issues with GitHub Copilot and AI features in Visual Studio Code, including problems with signing in, unexpected behavior in agent mode, and performance slowdowns. These issues often require users to disable the Copilot extension or adjust settings to improve functionality and user experience.
- Extension and Plugin Issues: Visual Studio Code users have reported issues with various extensions and plugins, including installation failures, signature verification errors, and unexpected behavior. These problems often require troubleshooting steps such as disabling extensions, checking system configurations, or seeking updates from extension developers.
- Remote Development and SSH Issues: Users have experienced issues with remote development and SSH functionality in Visual Studio Code, including connection failures, permission errors, and compatibility problems with remote servers. These issues often require users to adjust settings, downgrade versions, or seek alternative solutions to maintain productivity.
- User Interface and Usability Issues: Visual Studio Code users have reported various user interface and usability issues, including problems with navigation, layout, and accessibility. These issues often require adjustments to settings or feature requests for improved functionality and user experience.
- Debugging and Code Execution Issues: Users have encountered issues with debugging and code execution in Visual Studio Code, including problems with breakpoints, execution flow, and error messages. These issues often require troubleshooting steps such as adjusting configurations or seeking updates to resolve the problems.
- File and Project Management Issues: Visual Studio Code users have reported issues with file and project management, including problems with file operations, workspace settings, and project configurations. These issues often require adjustments to settings or feature requests for improved functionality and user experience.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 181
Summarized Issues:
- Bugs in Visual Studio Code on Windows 10: Users have reported various bugs in Visual Studio Code version 1.99.3 on Windows 10, including issues with renaming or pasting text and the inability to check for updates. These problems may be linked to system or extension conflicts, as detailed in the system and extension information provided.
- Markdown Rendering Issues in vscode.dev: There is a problem where vscode.dev fails to render markdown content from Jupyter Notebook (.ipynb) files located in remote repositories. This issue does not affect markdown from local .ipynb files or markdown (.md) files from the same remote repository, suggesting a potential security restriction or bug affecting remote file rendering.
- Debugging and Terminal Bugs in Visual Studio Code: Users have encountered issues with debugging and terminal functionality in Visual Studio Code, such as the creation of a debug.log file at startup and terminal freezing when stepping over a breakpoint. These problems persist even when all extensions are disabled, indicating potential core application bugs.
- Visual Studio Code Feature Requests: Several feature requests have been made for Visual Studio Code, including support for the new Model Context Protocol (MCP) Server Authorization and guidance on displaying a
.envfile. These requests aim to enhance the functionality and user experience of the IDE.
- Syntax Highlighting and Folding Issues: Users have reported bugs related to syntax highlighting and code folding in Visual Studio Code, such as CSS syntax not appearing until a file edit and glitches with folding functions in HTML files. These issues affect the usability and readability of code within the editor.
- Authentication and Sign-In Problems: There are ongoing issues with authentication and sign-in processes in Visual Studio Code, particularly with GitHub authentication not persisting and the sign-in button for GitHub.com being unresponsive. These problems disrupt user workflows, especially for enterprise accounts using SSO.
- Performance and Freezing Issues: Users have experienced performance problems in Visual Studio Code, such as frequent SSH disconnections and the application freezing when opening the terminal. These issues significantly impact the usability and reliability of the IDE.
- Copilot and Extension Bugs: Several bugs have been reported related to the GitHub Copilot extension, including lost files and threads, signature verification failures, and compatibility issues with API proposals. These problems hinder the functionality and integration of Copilot within Visual Studio Code.
- Visual Studio Code Update and Installation Issues: Users have encountered difficulties updating Visual Studio Code and installing extensions, with issues such as failed signature verification and unresponsive installation processes. These problems prevent users from accessing the latest features and improvements.
- Visual Studio Code Terminal and Debugging Bugs: There are persistent bugs in the terminal and debugging modules of Visual Studio Code, such as the terminal scrolling unexpectedly and the debugging module for C# disappearing. These issues disrupt the development process and require workarounds or fixes.
- Visual Studio Code Feature Enhancements: Feature requests have been made to improve Visual Studio Code, such as adding a built-in PDF viewer and enhancing the "Search Inside Files" feature. These enhancements aim to improve user experience and functionality within the IDE.
- Visual Studio Code Configuration and Settings Issues: Users have reported issues with configuration and settings in Visual Studio Code, such as the inability to remove paths from Workspaces and Folders and problems with the
workbench.tree.indentsetting. These issues affect the customization and organization of the development environment.
- Visual Studio Code Performance and Usability Problems: Performance and usability issues have been reported in Visual Studio Code, such as slow IntelliSense suggestions and the application hanging when opening or saving files. These problems hinder productivity and require attention to improve the overall user experience.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
- Toxicity Score: 0.55 (Repeated frustration, Lack of empathy, Ineffective solutions.)
- This GitHub conversation involves a user expressing frustration with an AI assistant's repeated, ineffective solutions for error handling in a Jupyter Notebook workflow. The user, seeking a more systematic and framework-based solution, encounters redundant advice and a lack of acknowledgment of their emotional state and urgency. The AI's suggestions, such as using
sys.exit(1), are inappropriate for the user's context, leading to further dissatisfaction. The conversation highlights the need for a more structured approach and better adaptation to user feedback.
-
- Toxicity Score: 0.85 (Highly aggressive language, Lack of constructive feedback, No moderation or response.)
- This GitHub conversation involves a user expressing extreme frustration and dissatisfaction with the performance of an IDE, using aggressive and profane language to describe their experience and the development team. The tone is highly negative and confrontational, with no other participants or responses in the conversation.
-
- Toxicity Score: 0.85 (High hostility, personal attacks, nationalistic sentiments, rapid escalation.)
- This GitHub conversation involves multiple users engaging in a heated and contentious discussion. Usernames are not specified, but the conversation is characterized by aggressive language, personal attacks, and nationalistic sentiments. The tone is predominantly hostile, with users expressing strong opinions about the support for a particular feature. Triggers of tension include perceived disrespect, national pride, and accusations of betrayal. The conversation escalates quickly, with users resorting to insults and derogatory remarks.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 23
Key Open Pull Requests
1. Render complex HTML in screen reader content: This pull request aims to enhance the screen reader functionality in Visual Studio Code by rendering complex HTML content, addressing issues related to line wrapping and dynamic line heights affected by decorations, and ensuring that font sizes and line heights are accurately reflected in the screen reader's output.
- URL: pull/249356
- Merged: No
- Associated Commits: 03425, 88e55, d84a7, a2637, 82411, c54ab, a9806, 8a712, f4e5a, 8afcd, 6c110, 5ee48, 38dfb, d0685, f7ba2, f7d47, cf367, e3296, 91d4b, f7837, 25492, aaaad, 6395e, 549e9, 95f77, ce134, 9dec3, 952f8, 9f7b3, c6d8a, 6ab9c, 20d17, 54e89, e75e7, c7ce4, 13e7c, 5adde, 4ee17, b4b62, 4888a, 61dba, aae1f, 35b21, 295a5, 1e596, cdf87, 6ead1, 3414d, f06a2, 1e5a7, 1d64c, ed5fb, 5b066, b5991, 39256, b0b28, 9f5d1, 6f38e, 62d90, 9f044, 131cc, d1aec, ad4af, 71e1d, 1a44a, c5190, 904ec, 8a14e, 6a1d6, f2d01, 85989, 4ee90, 2b715, d37de, fc878, ba40a, 52056, dd305, 14a0f, 47d97, 891d4, 563ab, 3e914, b7c77, a72a0, 9c2ab, c2787, 52013, 97773, aebb4, 258e9, e66ae, 46c53, ea282, 50ec1, 244f8, 08511, 810ad, 33c3d, 2e751, fd68a, 6409b, 9764d, e7ee6, 30467, 5fbfa, fcd36, 65075, fb640, 0b24c, e59e8, 8c2e0, 6cbc9, 11754, 82e9b, 8a009, 4b2d3, 2b0bc, cf006, 5c662, d5443, 4425c, d6bfa, 07652, 2c677, 7f00f, ab923, 7e79a, d836d, 7a564, aa406, 686d4, 00a97, 7852d, 80f8f, 30609, 69048, 375f3, d188c, 02df0, 85934, 16156, 9ec92, 1840c, 0e1b5, 2ce71, 77403, 77c8c, f1996, 1e0e1, 75831, f4b05, 70e1d, 1d5fa, 19a81, 126c1, 74622, 71d8d, 5e3ed, 17b19, 71b44, b5ab2, ad495, 0b616, b257a, 39181, c59b9, d48a2, edd97, 944bc, ae06c, 17c0a, a2d6c, f73db, 5f6ad, 5ad6e, 3d302, 1440b, c7a26, c5740, b42fa, 3e551, c724b, ecf63, e3758, ed966, c2f1d, be957, 3ee33, da046, 64e34, 98175, 035c8, 53631, 4b061, b6084, 29177, 11e6a, 2d9de, 52655, 31461, 55fa4, f43f5, e0bdb, e6ca2
2. chat bubbles for requests: This pull request introduces enhancements to the chat bubble feature in the Visual Studio Code project, focusing on improving CSS styling, logic for toggling, margin adjustments, and scenarios for displaying bubbles, while also ensuring code cleanliness by removing unused imports and organizing code blocks.
- URL: pull/249681
- Merged: No
- Associated Commits: e880e, f05f3, 8f3da, 0182d, e80be, c9f81, 0add7, 220d2, 1bfbc, cf983, 69e2d, cbfc5
3. Joycegu/add genai packages 05222025: This pull request involves adding several generative AI-related packages to the project, addressing duplicate package issues, and updating specific files within the codebase, as evidenced by multiple commits and a merge from the main branch.
- URL: pull/249589
- Merged: No
Other Open Pull Requests
- Custom Chat Modes in Visual Studio Code: This topic covers the introduction of support for custom chat modes in the Visual Studio Code project. The pull request includes features such as exclusive tool sets for custom modes, conditional display of management actions, and improvements to mode descriptions and mock services.
- Copilot Recovery Fixes: The pull request titled "Copilot
1.100recovery fixes" addresses various issues in the Microsoft VSCode project. It includes tweaks to quota indicator rendering, fixes for a 102% usage bug, and ensures elements are defined when setting aria labels.
- Math Support in Chat: This pull request introduces math support in chat by enabling basic math rendering in chat requests and responses. It also adds a setting for this feature and makes various adjustments such as reverting small changes and replacing Unicode characters.
- AI Settings Search Toggle: The pull request proposes the removal of the "Did you mean" suggestions feature and introduces a new AI settings search toggle. It includes adding an AI search button, fixing styling issues, and tweaking provider names.
- User Guidance Document: This pull request introduces a document aimed at new users to help them understand and utilize the technologies associated with Visual Studio Code. It includes guidance on installing necessary dependencies and details the technologies used and design elements.
- macOS Application Installation Detection: This pull request introduces a feature for macOS users of Visual Studio Code that detects when the application is installed outside the Applications folder. It offers to move it there, with specific handling for cases where the app is launched from the command line or installed in portable mode.
- Secondary Foreground Color Settings: The pull request introduces new secondary foreground color settings for diff decorations in the editor overview ruler. This enhancement aims to improve visual distinction for staged changes, aligning with existing customization options.
- Codebase Refactoring: This pull request involves refactoring the code by removing elements that were unnecessarily renamed. It is part of an effort to streamline the codebase in the Microsoft VSCode project and includes a merge from the main branch.
- Copilot Setup Steps: The pull request introduces Copilot setup steps as the initial walkthrough step for users connected to a Codespace. This enhancement aims to improve the onboarding process within the Visual Studio Code environment.
- Error Correction Instructions: This pull request introduces error correction instructions by suggesting the use of the
--devflag. It aims to display the Electron window for debugging purposes in the Visual Studio Code project.
- NPM Grunt Configuration: This pull request involves the creation and addition of an
npm-grunt.ymlfile to the project. It is currently open and not yet merged into the main branch of the Microsoft VSCode repository.
- Drag-and-Drop Enhancements: The pull request aims to enhance the user experience of drag-and-drop (dnd) drag areas in the QuickInput component. It updates the drag areas when the input's value is empty and disables the tooltip when the input box is moving.
- Folder Deletion Undo Improvements: This pull request addresses issue #249263 by modifying the
DeleteOperationinbulkFileEdits.ts. It ensures that when a folder deletion is undone, all its contents, including files and subfolders, are fully restored.
- Translation Fixes for Remote Extensions: This pull request addresses the issue of missing translations for remote built-in extensions in Visual Studio Code. It fixes the absence of
nls.keys.jsonin the server build and the incorrect passing of the UI language to the backend.
- Task Terminal Icon Color Fix: The pull request addresses a color glitch in the task terminal icon of the VSCode project. It proposes changes to make the icon red for failed/error states and seeks assistance to resolve issues related to hover and focus states.
- Documentation Enhancements: This pull request aims to enhance the Visual Studio Code project's documentation by adding an additional description to the Readme.md file. It is detailed in the commit with SHA 40b0c32ea0661b178f24d04afb6a50622ef87649.
- Snippet File Path Customization: The pull request introduces support for extensions to define the path to snippet files using a custom scheme. It addresses issue #248407 and includes a test extension to demonstrate and verify the implementation.
- Local Playground for Monaco Editor: This pull request proposes the addition of a local playground that renders the Monaco editor to aid in local development. It includes instructions to start it using the command
npx vite playground.
- Telemetry Data Correction: The pull request addresses the correction of the telemetry data related to the 'interactiveSessionProviderInvoked ttft'. It ensures accurate tracking and reporting of this specific telemetry event in the Visual Studio Code project.
- Gitter Badge and Markdown Simplification: This pull request updates the Gitter badge to use a standard Shields.io endpoint for consistency. It also corrects a minor grammatical error and simplifies the Markdown by removing redundant HTML tags.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 169
Key Closed Pull Requests
1. Setup environment.sh submodule fallback & Linux compiler fixes: This pull request addresses the setup of a fallback for the environment.sh submodule and implements several Linux compiler optimizations, including parallel processing support, memory usage optimization, and fast transpilation with ESBuild, to enhance the speed and efficiency of Linux compilation in the project.
- URL: pull/249202
- Merged: No
- Associated Commits: 1ecc1, 495c9, 67503, 3e009, c04c9, be9db, 6fa35, ed02d, 55a1b, dda7b, d8f78, 81853, af2ee, 83d97, 34859, 81b54, 66910, 916d8, 6104e, 7af4d, fae43, be46b, 1f41b, 7385c, a2fee, 05789, 54f0a, 62745, 312c2, 554c7, 2e1f6, 330f8, 6423f, 50698, 5d0c6, 20296, 87d71, a0ee7, b76fc, d2f91, 4e757, 38d34, d371f, d1a5d, d6458, 19622, 99031, 5ce28, 26ca7, feb9a, 1feef, a0aff, d5e4f, 16b16, 8432b, b611f, ec8ad, d104b, 8178d, bd0cc, 29ae7, 39e36, 0d1eb, 3ad2c, c3824, 6fd27, ad287, f9928, 14099, f8ddb, 1505f, 2c698, 218bf, d9e73, d18eb, a9cec, dac86, 9f87e, 91de8, 1cf2b, 2d039, ecb66, bcd1f, 8655e, f4c19, 81a2f, f978a, fc458, 0d3f4, 91992, 2ea96, 89853, a406a, 7221b, 1bd7b, c41cd, d21c0, af0cb, 96e33, 556a9, b3472, 2732a, d100d, 57a58, 16049, 0f65f, 1ce9e, 70d26, fbe15, 59df0, e60f0, 10703, c77bc, 1bd69, 0171f, 27509, 25426, c619f, 8b9cd, 2964c, 427a9, 5c89e, ccc84, d0352, 4c14e, 8b320, 5e9b1, ad1c1, c7aa4, b8aa3, 19f4c, 60537, 885e6, f4a30, 7bdb4, 43824, 5c51e, e51e3, b7aca, 85c39, 1cd05, 27a83, 7dd68, 087fc, d5a30, 17b9f, dbcfa, 5128f, f0fc3, 2dd84, 752b3, 8a43f, 4325d, 8e0c3, af769, 39385, 44207, f7fed, 90ee7, 6a85e, d43c5, 95a42, 9adac, 51576, 3a548, 788ea, 8bc5d, 24a24, d65e8, 95d10, 70eea, 4e0cd, 2e813, da933, 17549, ce93d, b8c0e, d3ec2, 56b23, 7a7a7, 88fb6, 7b1ca, 48fe9, dab67, 7e41e, dbea1, ad2dd, 26dea, b4026, ec483, da81f, 26be4, cb5e2, a843b, 18d3b, 3a1ba, 7b60a, 6c28a, 59753, 71a98, 9be6d, 78135, aab51, f952e, 62c0b, 37a9a, f2598, c9b78, 5a48b, 19481, 9bb03, 9adeb, 99bfd, 9d998, 5d411, 8d36e, 5662f, 4c59e, 11842, 6e354, f972b, 03635, 11f09, 2e06a, 42582, a4cd4, b3415, 63b6f, 87b6a, 46192, c9671, 675df, c55c7, 0bb81, b8a63, 788b0, 2ca1e, cbccc, f21fc, 7d1e0, ef2ca, 5a4d5, aac10, f491b, c1188, d930f, 65738, 694cb, bc394, e012a
2. [prompts]: add support for "unquoted string" values in prompt file headers: This pull request adds support for "unquoted string" values in prompt file headers, treats them the same as usual strings, improves diagnostic messages, and includes additional unit tests, addressing issues in the Visual Studio Code project.
- URL: pull/249374
- Merged: 2025-05-20T21:56:52Z
- Associated Commits: f09a2, 480cc, 70450, 8e780, 6be86, 081cf, 51342, d7f8c, bdeb3, 94421, 656ef, f1603, 314fe, 8119e, 19cbd, 971a9, f3d54, 9d2e3, 08c43, a98f7, 824e7, 20312, 71b2a, bf555, b2a3b, 06221, e9272
3. Treesitter-refactoring: This pull request involves a comprehensive refactoring of the TreeSitter integration within the Visual Studio Code project, including updates to the TokenizationTextModelPart, implementation of the TreeSitterLibraryService, and various fixes and improvements to ensure proper functionality and test coverage, as evidenced by multiple commits addressing tokenization, tree handling, and editor checks.
- URL: pull/249608
- Merged: 2025-05-23T14:30:38Z
- Associated Commits: b41fd, d414d, 8c247, b69dd, 855d8, 1aa9f, a5843, 210cc, b95af, 8205c, c01b7, 4d850, 57c68, d923b, 8d4c6, a3b68, 6defe, 2a9e6, a9720, 782db, 8cca8, 72055, c1ece, 1a702, 1bfd0, 69439, bf4ea
Other Closed Pull Requests
- Tool Sets Support in Visual Studio Code: This topic covers the introduction of support for tool sets in the Visual Studio Code project. The pull requests add
.toolsets.jsoncfiles, enable toolSets contributions for extensions, and consolidate all tools from the MCP server into a single set.
- Authentication Dialog Input Mode: The pull requests introduce support for an input mode in the authentication dialog of the Visual Studio Code project. They include setup dialog tweaks and work-in-progress input changes to enhance user interaction.
- Diagnostic Messages for Front Matter Records: These pull requests improve diagnostic messages for front matter records in the VSCode project. They add support for "unquoted string" values in prompt headers and enhance diagnostics for invalid header records.
- SCM Graph Tree Rendering: The pull requests introduce tree rendering for commits in the SCM Graph of the Visual Studio Code project. They incorporate features such as support for compressed nodes and enhancements to twistie and indent guide rendering.
- Environment Discovery on Windows: These pull requests enable environment discovery on Windows by adapting existing Unix shell resolution logic. They primarily default to PowerShell but allow for future expansion to other shells.
- MCP Enhancements: The pull requests introduce enhancements to the MCP by allowing resources to be attached as chat context. They also improve the handling of async iterables and disposables in the "add context" feature.
- Extension Installation Tool: These pull requests introduce a new tool for installing extensions in the Microsoft VSCode project. They focus on polishing the feature, fixing compilation issues, and improving user interface elements.
- Play Tool User Action Requirement: The pull requests address an issue by ensuring that the play tool requires user action when the window is not focused. They include several commits for fixing the issue and tweaking functionality.
- New Sound Feature for
chatUserActionRequired: These pull requests introduce a new sound feature forchatUserActionRequiredand add anannouncementsetting. They include tasks such as integrating a sound and conducting tests.
- Technical Debt Reduction: The pull requests address technical debt by eliminating the use of the
anytype for timeout and interval functions. This improves type safety and code quality in the Microsoft VSCode project.
- Chat Setup Dialog Updates: These pull requests involve updates to the chat setup dialog in the Visual Studio Code project. They include shortening the dialog title and improving the rendering of link buttons.
- AutoReveal Feature Refactoring: The pull requests involve refactoring the "autoReveal" feature in the Microsoft VSCode project. They address issue #248546 and include a series of commits that progressively refine the code.
- Cell Autoreveal Functionality: These pull requests focus on refining the cell autoreveal functionality in the Visual Studio Code project. They implement several scrolling optimizations and include minor code cleanups.
- Electron Framework Update: The pull requests update the Electron framework to version 35.4.0 in the Visual Studio Code project. They address several issues such as restoring support for
--xdg-portal-required-versionand resolving a white background flash on startup.
- Menu Bar Implementation Refactoring: These pull requests involve refactoring the menu bar implementation in the Visual Studio Code project. They utilize a centralized
MenuSettingsenum to enhance maintainability and clarity.
- Telemetry Enhancements: The pull requests involve enhancing telemetry in the Visual Studio Code project. They capture and print the names of commands that are queued and pending responses.
- SCM Graph Avatars Display: These pull requests address an issue where avatars were not being displayed in the SCM Graph hover view. They update the
@octokit/graphqlAPI calls to the new format required after the GitHub extension migration.
window.menuStyleSetting: The pull requests introduce a new setting calledwindow.menuStyleto the project. They allow users to choose betweennative,custom, andinheritmenu styles for application and context menus.
- Rendering Process Enhancements: These pull requests involve enhancing the rendering process in the Visual Studio Code project. They propagate the indent level of list and tree elements to their respective renderers.
- Chat Setup Dialog Visual Adjustments: The pull requests involve making visual adjustments to the chat setup dialog in the VSCode project. They include increasing the dialog icon size and implementing additional tweaks to enhance the user interface.
- Project Operational Refactoring: These pull requests, titled "Get things running," focus on refactoring code and implementing a settable observable. They ensure the project is operational as evidenced by the commit messages.
- Implicit Attachments Implementation: The pull requests introduce a preliminary implementation of new implicit attachments for the Visual Studio Code project. They include commits for the initial setup and cleaning up comments.
- EditContext Word Wrap Value: These pull requests address the issue of using the correct word wrap value in the EditContext of the Visual Studio Code project. They ensure the correct implementation as indicated by the commit messages.
- Account Menu Update Issue: The pull requests address an issue where the account menu was not being updated when changes were made from other windows. They include multiple commits to fix the problem.
- Log tmLanguage File Update: These pull requests update the log tmLanguage file in the Visual Studio Code repository. They incorporate changes from the vscode-logfile-highlighter version 3.4.1 and include a fix for colorize tests.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
Revert "use idiomatic programming in
setupChatModeAndTools, also localize human readable strings"- Toxicity Score: 0.55 (Disagreement over changes, Polarized opinions, Defensive responses.)
- This GitHub conversation involves a discussion between several users, including username1 and username2, where username1 expresses frustration over a recent change that was reverted. The tone of the conversation is tense, with username2 defending the original change and username1 questioning the decision to revert it. The conversation escalates as more users join in, some supporting the revert and others opposing it, leading to a polarized discussion.
-
Take care of some of the boring refactor changes
- Toxicity Score: 0.55 (Defensive responses,critical feedback,tense exchange)
- This GitHub conversation involves username1 initiating a pull request for refactoring changes, with username2 providing feedback that is initially constructive but becomes increasingly critical. Username1 responds defensively, leading to a tense exchange. The tone shifts from collaborative to confrontational, with both parties expressing frustration.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| bpasero | 209 | 16 | 54 | 93 |
| meganrogge | 62 | 12 | 30 | 138 |
| legomushroom | 173 | 6 | 1 | 25 |
| roblourens | 95 | 13 | 26 | 55 |
| jrieken | 94 | 11 | 22 | 52 |
| connor4312 | 64 | 9 | 12 | 85 |
| lszomoru | 93 | 16 | 14 | 27 |
| justschen | 84 | 10 | 5 | 33 |
| aiday-mar | 78 | 5 | 10 | 10 |
| hediet | 70 | 13 | 5 | 8 |