Weekly GitHub Report for Vscode: March 18, 2025 - March 25, 2025 (12:16:44)
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.97.2
1.2 Version Information:
Released on February 12, 2025, this version of Visual Studio Code focuses on resolving issues identified in the "January 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.
-
Extension Host Keeps Crashing When Enabling Extensions With Tree-Sitter On VS Code > 1.98: This issue reports a bug in Visual Studio Code where the extension host crashes when enabling extensions that use
tree-sitter, specifically when opening a Swift file in a production build of VS Code version 1.98.1 or higher. The problem does not occur in development mode and is resolved by downgrading to version 1.97.2 or lower.- The comments discuss attempts to reproduce the issue, with suggestions to upgrade VS Code and apply a workaround by modifying the extension host's arguments. There is a detailed technical investigation into the crash, including analysis of the WebAssembly module and potential toolchain issues. The conversation also includes sharing of crash dump files and ongoing efforts to identify the root cause, with updates on testing and debugging progress.
- Number of comments this week: 19
-
Terminal suggestions conflicts with normal usage: This issue describes a bug in Visual Studio Code's terminal suggestions feature, which interferes with the user's ability to navigate directories using the
cdcommand in PowerShell. Instead of suggesting directories, the terminal suggests executable files, disrupting the user's workflow and muscle memory.- The comments discuss the problem of terminal suggestions showing executable files instead of directories when using the
cdcommand in PowerShell. Various settings and configurations are suggested to resolve the issue, but the problem persists, particularly on Windows. The discussion includes attempts to diagnose the issue further, with suggestions to try different settings and to test on the insiders build of Visual Studio Code. - Number of comments this week: 10
- The comments discuss the problem of terminal suggestions showing executable files instead of directories when using the
-
Can't connect to Copilot: This issue is about a user experiencing difficulties connecting to Copilot in Visual Studio Code, where clicking "Use Copilot for Free" results in the process stopping and failing to connect. The user provides detailed system information and mentions that the problem persists across different attempts, but it works in the Visual Studio Code - Insiders version.
- The comments section involves troubleshooting steps, including running
code --verboseand checking logs, which the user attempts but encounters issues with. Suggestions are made to try the Insiders build, where the problem does not occur, and further guidance is provided on triggering the setup and sign-in flow for Copilot, which the user eventually confirms is working fine in the Insiders version. - Number of comments this week: 10
- The comments section involves troubleshooting steps, including running
-
[BISECT] Regression: Debugging Session Does Not Restart on Shift+Ctrl+F5: This issue reports a regression in Visual Studio Code where the debugging session does not restart when using the Shift+Ctrl+F5 shortcut, which is identified as a bug in the VS Code insiders build. The problem is confirmed to occur even when all extensions are disabled, and a specific commit has been identified as the cause through a git bisect process.
- The comments discuss potential causes and troubleshooting steps, including testing with the latest main commit and verifying if the issue persists with the insiders build. The user provides detailed reproduction steps and clarifies that the problem does not occur in earlier versions. There is also a discussion about an error related to the build script, but the user confirms that the issue is not related to the build process.
- Number of comments this week: 7
-
MCP: Customize descriptions for server/tools via mcp.json: This issue discusses the need for customizable descriptions for server and tool configurations in the
mcp.jsonfile to improve the quality and accuracy of tool usage within the project. The current descriptions do not align with best practices, leading to conflicts and inefficiencies, and the existing workaround usingcopilot-instructions.mdis becoming unwieldy and insufficient for covering all edge cases.- The comments reflect a debate on whether to improve server descriptions or allow user customization, with some suggesting integrating this functionality into servers or using structured frontmatter in configuration files. There is a consensus that both better server descriptions and user customization are necessary, and the current workaround is inadequate.
- Number of comments this week: 7
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.
- Opening Extremely Long URLs Causes Notification Popup to Overflow the Display: This issue describes a problem in Visual Studio Code where attempting to open an extremely long URL from the terminal using
Ctrl + Clickcauses the notification popup to overflow the display, making it impossible to interact with the popup. As a result, users are unable to confirm or cancel the action to open the external website, forcing them to shut down VS Code to resolve the situation. - Relative clickable links rendered in the document don't work on Windows: This issue highlights a bug where relative clickable links rendered in documentation comments do not function correctly on Windows, despite working on MacOS. The problem specifically affects plain links in comments, such as those pointing to local files, and there is uncertainty about whether this is a regression or a longstanding issue.
- VSCode restarting devices periodically: This issue is about a bug in Visual Studio Code (VSCode) where the user's peripheral devices, such as the mouse, speakers, and keyboard, intermittently freeze and restart, accompanied by the Windows "plug in" sounds. The problem has persisted for over a year, affecting the user's workflow on a Windows 10 system with specific hardware and software configurations, including various installed extensions and system settings.
- Show Comments in TextMate Scope Inspector: This issue is about a feature request to enhance the Visual Studio Code (VSCode) TextMate scope inspector by displaying comments from the TextMate grammar files. Currently, these comments are only present within the TextMate files themselves and do not provide any external assistance, so the proposal suggests using them to offer basic documentation for TextMate scopes within the VSCode environment.
- Inspect Context Keys Should Open JSON File instead of logging to dev console: This issue is about a request to change the behavior of the "Inspect Context Keys" feature in a GitHub project, suggesting that it should open a JSON file in VS Code instead of logging information to the developer console. The proposed change aims to enhance user experience by allowing users to search within the object, providing a more efficient and user-friendly interface.
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: 190
Summarized Issues:
- Accessibility Issues in Visual Studio Code: Accessibility issues in Visual Studio Code are affecting users, particularly those using screen readers. For instance, the NVDA screen reader reads terminal commands instead of text in the Nano editor, and the NVDA screen reader repeats the penultimate line of text when the last line is empty, impacting visually impaired users' experience.
- Bugs in Visual Studio Code Terminal: Several bugs have been reported in the Visual Studio Code terminal, including issues with terminal suggestions replacing commands incorrectly and the terminal becoming unresponsive after certain actions. These problems hinder users' ability to efficiently use the terminal for development tasks.
- Visual Studio Code Update and Installation Issues: Users have reported problems with updating and installing Visual Studio Code, such as the update process searching for the wrong installation path and the inability to execute updates on macOS. These issues prevent users from keeping their software up to date.
- Performance Problems in Visual Studio Code: Performance issues in Visual Studio Code have been noted, including high CPU usage and slow terminal launch times. These problems affect the overall efficiency and responsiveness of the editor, impacting users' productivity.
- Visual Studio Code Debugging Issues: Debugging in Visual Studio Code is facing challenges, such as the failure to restart debugging sessions and the inability to gracefully terminate sessions. These issues disrupt the debugging workflow and require users to find workarounds.
- Visual Studio Code Feature Requests: Users have requested various feature enhancements for Visual Studio Code, including the ability to pin code snippets and improve search and replace functionality. These requests aim to enhance the usability and functionality of the editor.
- Visual Studio Code Extension Issues: Problems with extensions in Visual Studio Code include the failure of the GitHub Copilot extension and unexpected automatic installation of extensions. These issues affect users' ability to customize and extend the functionality of the editor.
- Visual Studio Code UI and Layout Problems: Users have reported UI and layout issues in Visual Studio Code, such as non-functional window control buttons and off-center chat widgets. These problems affect the visual consistency and usability of the editor.
- Visual Studio Code Language and Syntax Issues: Language and syntax-related issues in Visual Studio Code include incorrect snippet suggestions and problems with semantic highlighting. These issues impact the accuracy and effectiveness of code editing and navigation.
- Visual Studio Code Git and Source Control Issues: Users have encountered issues with Git and source control in Visual Studio Code, such as the failure of the "Stage Changes" command and problems with file renaming. These issues hinder version control and collaboration workflows.
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: 131
Summarized Issues:
- Theme Customization in Visual Studio Code: Users have requested a default "intermediate" gray color theme to improve visibility in challenging lighting conditions. However, the team has indicated no plans to add more built-in themes, encouraging users to explore or create custom themes instead.
- Server Connectivity and Command Execution Issues: Several issues involve difficulties with server connectivity and command execution in Visual Studio Code. These include problems with server integrity checks, missing files causing connectivity issues, and difficulties running server commands in remote environments.
- Crashes and Performance Problems: Users have reported crashes and performance issues in Visual Studio Code, such as crashes on Raspberry Pi 5 and excessive memory consumption on macOS. Workarounds and patches are suggested to mitigate these issues.
- Feature Requests for Enhanced Usability: There are requests for new features to improve usability, such as adding an "Open folder in VS Code" option in the file browser and an envFile configuration option for mcp.json. These features aim to enhance convenience and performance for developers.
- Source Control and Git Integration Issues: Problems have been reported with source control integration, such as incorrect links to Git installation pages and issues with signing into GitHub. These issues affect the functionality of extensions and user workflows.
- Terminal and Debugger Functionality Problems: Users have experienced issues with terminal and debugger functionalities, including problems with terminal suggestions on remote connections and missing debugging controls for Python programs. Solutions involve configuration adjustments and software updates.
- Memory Management and Resource Leaks: Several issues highlight memory management problems, such as memory leaks in the terminal and listener leaks in event handling systems. These issues can lead to performance degradation and require careful resource management.
- Accessibility and User Interface Concerns: Accessibility issues have been raised, such as redundant announcements by screen readers and visual bugs affecting user interaction. These concerns emphasize the need for inclusive design and user-friendly interfaces.
- Code Execution and Debugging Errors: Users have reported errors related to code execution and debugging, such as "400 Bad Request" errors with APIs and missing configurations in launch.json. These issues disrupt development workflows and require troubleshooting.
- Extension and Plugin Management: There are requests for better management of extensions and plugins, including the ability to enable or disable specific extensions in workspace settings and to manage configuration settings of uninstalled extensions. These features aim to streamline development environments.
- Visual and Syntax Highlighting Issues: Problems with visual elements and syntax highlighting have been reported, such as incorrect icon themes and broken syntax highlighting due to null object errors. These issues affect code readability and user experience.
- Build and Compilation Delays: Users have experienced delays in the build process, such as unexpected pauses during compilation. These delays can hinder development efficiency and require investigation to identify the root cause.
- Autocomplete and IntelliSense Errors: Issues with autocomplete and IntelliSense have been reported, such as unsupported color formats and incorrect error messages for C++ projects. These problems affect code completion and error detection capabilities.
- Configuration and Environment Variable Management: Users have highlighted the inconvenience of managing environment variables, such as the need to restart VS Code to update variables. Suggestions include more efficient solutions for refreshing environment variables.
- GitHub Codespaces and Container Issues: Problems with GitHub Codespaces and container setups have been reported, such as initialization errors and permission issues. These problems affect the ability to work in cloud-based development environments.
- Search and Navigation Problems: Users have experienced issues with search functionality and navigation, such as incomplete search results and disappearing menu items. These issues impact the ability to efficiently locate and access features within the application.
- Task and Process Management Errors: Errors related to task and process management have been reported, such as missing tasks and incorrect process execution. These issues require careful configuration and troubleshooting to resolve.
- Docker and MCP Server Enhancements: Feature requests for Docker support and MCP server enhancements have been made, aiming to improve security and configuration management. These features are intended to streamline server operations and enhance development workflows.
- Terminal Focus and Input Issues: Users have reported problems with terminal focus and input, such as unexpected focus shifts and unresponsive input models. These issues disrupt terminal usage and require attention to input handling mechanisms.
- Schema and Configuration Validation: There is a need for improved schema handling and configuration validation to prevent errors and ensure proper tool functionality. This includes validating schemas against known properties and implementing debugging commands.
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.
- Auto-indent of switch-case is idiotic
- Toxicity Score: 0.55 (Strong language, Frustration, Questioning moderation decisions)
- This GitHub conversation involves a user expressing frustration over an indentation issue in a code editor, using strong language to describe their dissatisfaction. Another user comments on a related issue being marked as a "feature request" and questions why it was locked, indicating a sense of confusion and mild frustration. The tone of the conversation is tense, with triggers of tension being the perceived inadequacy of the software and the handling of related issues.
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: 22
Key Open Pull Requests
1. Allowing to define variable font-sizes: This pull request introduces the ability to define variable font sizes within the Visual Studio Code editor, ensuring that font sizes do not exceed the line height, and includes various tests and adjustments to ensure correct rendering and functionality of text decorations, line wrapping, cursor alignment, and accessibility features.
- URL: pull/243987
- 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, 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
2. drag and drop from external URLs: This pull request addresses issues #240025 and #242039cc by implementing a feature that allows users to drag and drop content from external URLs into the Visual Studio Code environment, with various commits focusing on re-adding the drag-and-drop functionality, improving data handling, and ensuring compatibility with the main branch.
- URL: pull/243816
- Merged: No
- Associated Commits: e75e9, 5a353, e43dc, 95ced, 61808, 98fc2, 9d769, 84e64, 82c3c, a5e78, 48776, 4ee30, 49f3e, 71fb9, 7b8a9, 7dcb5, b751a, ca80c, 89167, f16bb, 31363
3. Add inertial scrolling to scrollable elements: This pull request introduces inertial scrolling support for scrollable elements on Linux Wayland in the Visual Studio Code project, addressing the lack of this feature despite its support in Electron, by implementing a workaround that includes a new setting to enable inertial scrolling, which is disabled by default.
- URL: pull/244034
- Merged: No
Other Open Pull Requests
- DOM Class Navigation Enhancement: This pull request addresses issue #236603 by implementing a feature that allows users to navigate to the definition of built-in DOM classes in HTML scripts. It enhances the functionality of Visual Studio Code by correctly resolving the filename
lib.dom.d.tsto its corresponding file.
- Account Policy Service Introduction: This pull request introduces a new
AccountPolicyServiceto the project, which works alongside the existingNativePolicyServicewithin aMultiplexPolicyService. It extends theDefaultAccountServiceto handle account policy logic and allows for the addition of policies for configurations not present in the core.
- Copilot Feature Enhancements: This pull request aims to enhance the functionality of the Copilot feature in Visual Studio Code by allowing users to attach notebook cell outputs as context in chat requests. Specific updates include the addition of output URI parsing to the notebook document service and support for handling images like other outputs.
- PlzDedicatedWorker Feature Fix: This pull request aims to fix and re-enable the PlzDedicatedWorker feature in the Microsoft VSCode project, addressing issue #244143. It incorporates feedback from a related issue comment, with a series of commits that include re-enabling the feature, addressing review feedback, and improving ID checks.
- Tree View Rendering Race Condition: This pull request addresses a race condition in the tree view rendering of a GitHub project by ensuring that each element waits on the correct batch. This prevents incorrect rendering when the treeView data source is synchronous or near-synchronous.
- Git Commit Error Message Box Fix: This pull request addresses issue #169871 by fixing the problem of the message box being too short for git commit errors in the VSCode project. It ensures that error messages are now displayed in a multiline format and has been manually tested to confirm the improvement.
- Text Cursor Transparency Adjustment: This pull request addresses issue #244087 by making the browser's default text cursor transparent in the code editor. This change prevents the overlapping of two text cursors.
- Work-in-Progress Submission: This pull request, titled "wip," is a work-in-progress submission to the Visual Studio Code repository on GitHub. It includes multiple commits, such as merging the main branch into a feature branch named "ben/encoding-exthost-wip," but lacks a detailed description of the proposed changes or associated issue.
- Copilot Cell Decoration Handle: This pull request addresses issue #14614 in the vscode-copilot repository by preferring the use of a handle to identify which cell to decorate. It makes the handle optional to avoid additional calculations and includes two commits with changes to the codebase.
- Installation Folder Warning Banner Disablement: This pull request aims to disable the "installation folder" warning banner that appears when debugging extensions in Visual Studio Code. It addresses issues #176164 and #225801, as detailed in the commits and further illustrated by an attached image.
- Terminal Suggest Path Executable Cache Update: This pull request addresses issue #240129 by updating the terminal suggest path executable cache whenever there is a change in the binary. The changes are detailed in the commits linked to the pull request on the Visual Studio Code GitHub repository.
- Git Request Cancellation in Timeline: This pull request addresses the issue of git requests not being cancelled when switching editors too quickly in the timeline feature of Visual Studio Code, as referenced in issue #244336. It implements changes such as cancelling git log commands and ensuring timeline requests are not redundantly deleted upon cancellation.
- Breakpoint Property Persistence: This pull request addresses issue #239770 by modifying the
updateBreakpointsfunction to ensure that existing breakpoint properties, such aslogMessage, persist during updates. It includes a test to verify that these properties are retained correctly when a breakpoint's condition is modified.
- Drag-and-Drop Handler Modification: This pull request addresses issue #239048 by modifying the drag-and-drop handler to ensure that the correct drag image is used for panel tabs in the lower panel. It prioritizes the use of the .action-label element for a more accurate visual representation and includes tests to verify the functionality and fallback behavior.
- Download Extensions Locally Option: This pull request introduces a new feature that adds the
--download-extensions-locallyoption to the project, addressing issue #9994 in the vscode-remote-release repository. It includes a commit with the necessary code changes.
- Async Tokenization Feature Disablement: This pull request proposes to disable the
experimental.asyncTokenizationfeature by default in the project due to its current issues with embedded languages. It addresses and aims to resolve the problems outlined in issues #235344, #202938, and #237438.
- Automatic Closure of Forwarded Ports: This pull request proposes the addition of a command to automatically close all forwarded ports that remain open without an active process when connecting to a remote development container in Visual Studio Code. It addresses an issue where these ports are not detected and closed by the current setup.
- TextInputFocus State Bug Fix: This pull request addresses a bug where the TextInputFocus state is not correctly set to false when the setHasFocus function is triggered with a false value. The fix is indicated by the commit titled "adding fix for focus issues."
- Chat Status Dashboard API Addition: This pull request proposes the addition of a new API that allows extensions to contribute basic status items to the chat status dashboard in Visual Studio Code. It includes an example implementation for workspace status and plans for further refinement for integration with Copilot.
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: 310
Key Closed Pull Requests
1. Store chat sessions in fs: This pull request addresses the issue of excessive data for the storage service by implementing a solution to store chat sessions in the filesystem, as indicated by the title and the series of commits that include starting the storage process, handling session clearing, and fixing related errors, ultimately resolving issue #187407.
- URL: pull/243670
- Merged: Yes
- Associated Commits: 0cb90, 1e581, fc44c, f8c15, d1edd, 9b9df, cc7d1, b4df4, 3917d, e2152, 3b3ef, e04a4, e6ec0, c5eed, 6e108, 5bce5, d2236, 00802, fcb92
2. add code-tunnel suggestion spec: This pull request adds a suggestion specification for code-tunnel to the Visual Studio Code project, addressing and fixing issue #242589, and includes various commits for code cleanup, redundancy removal, and test fixes, ultimately resulting in a successful merge.
- URL: pull/243809
- Merged: Yes
- Associated Commits: 49191, 7d992, d8e0a, c4829, 79673, 8c7d9, 05434, 59196, 116c3, afc93, 93ded, b0c0e, ad1a8, 05cb0, 8cf9e, 77fd0, d7252, 596ec
3. fix fish terminal suggestions when wrapping occurs: This pull request addresses the issue of incorrect command line detection in the Fish terminal when line wrapping occurs by implementing a special handling in the prompt input model to accommodate Fish's lack of a line continuation character, ensuring that either a newline is added or not based on the presence of a backslash, while also trimming whitespace and adding tests to cover these scenarios.
- URL: pull/243806
- Merged: Yes
- Associated Commits: a6614, 6bd8a, 6240b, 8d234, 98a7b, 68f7e, 6183a, 160a4, 0f00b, c09d8, e3e9d, c7aca, aa41d, 4ba1f
Other Closed Pull Requests
- 7z Archiving Process Debugging and Correction: This topic involves implementing debugging and corrective measures to address the issue of the 7z archiving process including too many files. The pull request includes actions such as printing debug statements, skipping failing tests, using absolute paths, and adjusting flags, ultimately resulting in a successful merge to resolve issue #243484.
- Terminal Completions and Prompt Glitch Fixes: This topic covers the addition of a
code-tunnelspecification to terminal completions and resolving a prompt glitch issue in zsh and bash shells. The pull requests include implementing different fixes for each shell due to their distinct underlying causes and refining the solution with multiple commits.
- Chat Feature Setup Tweaks: This topic involves making various setup tweaks for the chat feature in the Visual Studio Code project. The pull requests include support for notebooks, addressing leaks, clearing hacks, sorting, and fixing issues, ultimately resulting in successful merges.
- Web Workers Code Cleanup and Renaming: This topic involves a comprehensive cleanup and renaming of code related to web workers in the Visual Studio Code project. The pull request includes changes such as renaming
NotebookSimpleWorkertoNotebookWebWorker, mergingBaseEditorSimpleWorkerwithEditorSimpleWorker, and simplifying the build file for web workers.
- Prompt Files Configuration Enhancements: This topic addresses the addition of support for glob patterns in the configuration settings of the "prompt files" feature. The pull request includes various commits that remove redundant arguments, implement new logic, and add comprehensive unit tests for different workspace scenarios.
- Prompt Input Model Tweaks: This topic addresses the issue #243906 by tweaking the prompt input model to ensure correct handling of values, cursor indices, and ghost text, particularly for
pwshandfishshells. The pull request includes a series of commits with fixes, simplifications, and the addition of tests.
- National Language Support and Code Simplification: This topic involves adding national language support (nls) information to the
monaco-editor-coreand removing leftover AMD tasks. The pull request includes several code simplifications, splitting of editor worker scripts, and deletion of unused code.
- Terminal Suggestions Fixes: This topic addresses issues with terminal suggestions in wrapped terminals by fixing the
getPrefixfunction. The pull request ensuresprecedingTextandleadingLineContentare stripped of\nfor proper command matching and adjusts the acceptance code to handle newlines inreplacementText.
- Accessibility Signals for Edits: This topic addresses the addition of accessibility signals for keeping or undoing edits in the Visual Studio Code project. The pull request includes fixing a specific issue, updating settings, making changes for individual edits, and improving naming conventions.
- Build Process Enhancements: This topic involves enhancing the build process of setup packages by enabling parallel execution. The pull request includes attempts to build the setup in parallel, merge updates from the main branch, and make various adjustments such as uncommenting code and updating task display names.
- Server State Control and Configuration Improvements: This topic introduces lenses to control the server state from the MCP configuration and inputs. The pull request addresses issues related to configuration changes to prevent re-prompting, ensures loading from user local config, and allows viewing and editing of saved configurations.
- Synchronization Feedback Improvements: This topic introduces various synchronization feedback improvements, notably adding a 'yolo' mode for
chat.tools.autoApprove. The pull request includes several other enhancements and fixes such as adjusting UI elements and supporting new protocol features.
- Prompt Contents Parser Refactoring: This topic refactors the prompt contents parser to enhance its flexibility. The pull request addresses issues related to prompt parsing and cleanup and is linked to a specific issue in the VSCode Copilot repository.
- Setup Dialog Restyling: This topic involves restyling the setup dialog in the Visual Studio Code project. The pull request includes changes to the dialog's appearance, wording adjustments, alignment, and renaming, ultimately resulting in a merged update to the main branch.
- Browser Bug Workaround: This topic addresses a browser bug by implementing a workaround. The pull request includes several commits such as fixing an issue with the chat widget service's focus handling and moving code related to textarea focus into NativeEditContext.
- Tree-sitter for CSS: This topic involves the addition of tree-sitter for CSS to the project. The pull request includes several commits such as hard coding root scopes, adding temporary logging for testing, excluding CSS from module ignore, and removing log lines.
- Tool Confirmation Alerts and Accessibility Enhancements: This topic addresses the need for an alert when tool confirmation is required and enhances accessibility by adding to the response's ARIA label. The pull request fixes issue #243359 and makes the tree data hint check more specific.
- Task Problem Matcher Events API Simplification: This topic simplifies the task problem matcher events API by removing a previously added generic change event with redundant properties. The pull request introduces two specific events,
TaskProblemMatcherStartedandTaskProblemMatcherEnded, to better align with the existing task API.
- Configuration Resolver Service Simplification: This topic simplifies the
IConfigurationResolverServiceby introducing an introspectableConfigurationResolverExpression. The pull request consolidates and streamlines internal methods and enables introspection for MCP work.
- CodeQL and Azure Container Web App Configuration: This topic involves the creation of configuration files for CodeQL and Azure Container Web App. The pull request was ultimately closed without being merged into the main branch of the Microsoft VSCode repository.
- Source Control Provider Enhancements: This topic introduces a new status bar entry and repository picker for the source control provider. The pull request implements the ability to pin the active repository and includes several commits to integrate these features while ensuring compatibility with the main branch.
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.
-
on bin change, update terminal suggest path executable cache
- Toxicity Score: 0.55 (Persistent disagreement, defensive responses, lack of resolution.)
- This GitHub conversation involves user1 proposing a change, which user2 critiques for potential issues, leading to user1 expressing frustration over the feedback. User3 attempts to mediate by suggesting a compromise, but user2 remains firm in their stance, causing user1 to become defensive. The tone shifts from collaborative to tense as the discussion progresses.
-
- Toxicity Score: 0.55 (Persistent disagreement, defensive responses, unresolved tension.)
- This GitHub conversation involves username1 expressing dissatisfaction with username2's approach, leading to a defensive response from username2. The tone becomes increasingly tense as username1 insists on a different solution, while username2 attempts to justify their method. The conversation is marked by a lack of resolution and growing frustration on both sides.
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 | 176 | 32 | 36 | 52 |
| meganrogge | 121 | 22 | 21 | 118 |
| Tyriar | 37 | 10 | 31 | 106 |
| roblourens | 85 | 33 | 7 | 37 |
| connor4312 | 74 | 28 | 12 | 43 |
| jrieken | 42 | 15 | 19 | 25 |
| TylerLeonhardt | 15 | 11 | 13 | 54 |
| gjsjohnmurray | 2 | 0 | 0 | 90 |
| sandy081 | 39 | 19 | 7 | 26 |
| legomushroom | 63 | 7 | 4 | 4 |