Weekly GitHub Report for Vscode: June 23, 2025 - June 30, 2025 (23:07:08)
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 version of 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.
-
Split Terminal Pane vertically: This issue is a feature request for the ability to split a terminal pane vertically in Visual Studio Code, as currently, the terminal only supports horizontal splitting. The user is seeking a more flexible terminal layout within the terminal window itself, rather than using workarounds involving moving the terminal to the editor area.
- The comments discuss potential workarounds for vertical splitting by moving the terminal to the editor area, where vertical splits are possible, but this does not meet the original request. There is confusion and clarification about how to drag and drop the terminal, with suggestions to refer to documentation and video demonstrations. Ultimately, it is confirmed that vertical splitting within the terminal panel itself is not currently possible, and the suggested workaround is not a perfect solution.
- Number of comments this week: 16
-
Agent Mode pauses when VS Code loses focus: This issue describes a problem with the Agent Mode in Visual Studio Code on macOS, where the mode pauses its operations when the editor window loses focus, particularly when using macOS's "spaces" feature to switch between different applications. The user reports that the Agent Mode resumes its activity only when the editor window regains focus, indicating a potential issue with how the application handles background processes or window focus.
- The comments discuss potential causes and solutions for the issue, including the possibility of OS or Electron-level suspension mechanisms and renderer throttling for non-focused windows. Suggestions include using a flag or API to disable background throttling dynamically, with considerations for power and CPU usage. The discussion also touches on the technical aspects of throttling in the Chromium and Electron environments, and the need for a method to manage chat sessions actively.
- Number of comments this week: 14
-
VSCode cannot open any folder: This issue involves a problem with Visual Studio Code (VSCode) where the application fails to open any folder after a Windows 11 update, resulting in a system error related to the
uv_os_gethostnamefunction. The error seems to be linked to a network disk software that causes gibberish characters, potentially affecting the hostname retrieval process in VSCode.- The comments discuss potential causes and solutions, including testing with different Node.js versions and running VSCode with specific command-line options. A temporary workaround is suggested, involving opening folders via the context menu. The issue is eventually traced back to a third-party software causing gibberish characters, and further investigation is requested to isolate the problem within VSCode.
- Number of comments this week: 11
-
Extension Signature Verification Failed: Pylance: This issue involves a bug encountered when attempting to install the
ms-python.vscode-pylanceextension on a remote OrbStack Linux VM, resulting in a signature verification failure with an 'UnhandledException' error. The problem appears to be related to the version of thevsce-signtool bundled with the latest version of VS Code, which fails to verify the extension's signature correctly.- The comments discuss related issues and inquire about the source code availability for
Microsoft.VisualStudio.Extensions.Signing. A user successfully verifies the extension using a newer version of thevsce-signtool, suggesting the issue is with the older version bundled with VS Code. It is noted that upgrading to version 2.0.6 of the@vscode/vsce-signpackage, which uses updated binaries, should resolve the problem. - Number of comments this week: 5
- The comments discuss related issues and inquire about the source code availability for
-
Disable ALL Extensions ReleaseNote Popup: This issue is about a request to provide a configuration option in Visual Studio Code to disable the automatic opening of release notes in a new editor tab after an extension update. The user is seeking a way to prevent these release notes from appearing without user intervention, as they find it disruptive.
- The comments discuss the cause of the issue, with images provided for context, and clarify that the behavior is due to the extensions themselves. It is explained that Visual Studio Code cannot prevent extensions from opening tabs, and users are advised to contact extension developers for a solution. A suggestion is made about detecting how tabs are opened, whether by user action or automatically by the extension.
- 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 generating markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request suggests that code cells should be able to produce markdown output that can be dynamically generated and displayed, enhancing the functionality and interactivity of notebooks within 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-windowfails to open a new window as intended, instead replacing the existing window with the new connection. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, causing the current session to disconnect and switch to the new server without creating a separate window. ${userHome}in a task command creates bad paths: This issue describes a problem in Visual Studio Code where using the${userHome}variable in a task command of type "process" results in incorrect path formatting, causing execution errors. The issue is specific to the "process" type and does not occur when using the "shell" type with PowerShell as the default shell, and a workaround involves using${env:USERPROFILE}instead of${userHome}to generate the correct path.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a bug in Visual Studio Code 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 problem specifically affects remote connections, such as those using WSL or SSH, and seems to be related to the remote connection entering a "sleep" state when the main window is minimized, causing a delay in character display until the main window is restored.
- Unicode character displayed as a question mark ?: This issue involves a problem where a Unicode character, specifically the full-width quotation mark (U+FF02), is displayed incorrectly as a question mark in Visual Studio Code. The problem persists even when all extensions are disabled, and the character displays correctly in other applications like Firefox, indicating a rendering issue within VS Code itself.
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: 294
Summarized Issues:
- Visual Studio Code Bugs: Visual Studio Code has several reported bugs affecting user experience, such as issues with sign-in badges not disappearing, Quick Chat input field overlapping the code search panel, and network drives not displaying contents. These bugs require users to restart the application or find workarounds to continue their work effectively.
- Feature Requests and Enhancements: Users have requested various enhancements in Visual Studio Code, such as the ability to add emojis and media files in code reviews, customize sticky scroll lines for Allman style, and improve the "Find All References" feature. These requests aim to enhance the usability and functionality of the platform.
- Remote and File Handling Issues: There are significant issues in remote scenarios, such as partial file loss during large file saves and problems with SSH agent forwarding in Devcontainers. These issues can lead to data loss and hinder remote development workflows.
- Git and Version Control Problems: Users have reported problems with Git functionality, including a regression in submodule detection and issues with the
commitfunction not respecting thesignCommit: falseoption. These issues affect the reliability of version control operations within the editor.
- Performance and Crash Issues: Visual Studio Code has performance problems, such as out-of-memory errors causing unexpected window terminations and crashes when interacting with GitHub Copilot. These issues disrupt user workflows and require attention to improve stability.
- Copilot and AI Integration Challenges: The integration of GitHub Copilot in Visual Studio Code has led to several challenges, including unresponsive behavior, excessive filtering by the Responsible AI Service, and unauthorized code changes. These issues impact the effectiveness of AI-assisted development.
- User Interface and Usability Concerns: Users have expressed concerns about the user interface, such as the need for vertical terminal splitting, better discoverability of settings, and improvements in the chat input interface. These concerns highlight the need for a more intuitive and customizable user experience.
- Extension and API Issues: There are issues with extensions and APIs, such as the failure of terminal smoke tests and the need for a public API for the merge editor. These issues affect the extensibility and integration capabilities of Visual Studio Code.
- Security and Authentication Problems: Users have reported issues with authentication, such as problems with GitHub authentication and OAuth errors during MCP Authorization. These issues can prevent users from accessing necessary features and services.
- Language and Syntax Highlighting Bugs: There are bugs related to language and syntax highlighting, such as poor semantic highlighting for equations in markdown files and issues with React component highlighting. These bugs can lead to confusion and misinterpretation of code.
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: 113
Summarized Issues:
- Visual Studio Code Bugs: Visual Studio Code has several bugs affecting user experience, including issues with terminal visibility, performance problems, and unexpected behavior in extensions. Users have reported invisible text in the terminal, unresponsive Jupyter Notebook projects, and terminal suggestions not functioning with certain shells. These bugs disrupt workflows and require workarounds or fixes to restore functionality.
- GitHub Copilot Issues: Users have encountered multiple issues with GitHub Copilot, including problems with screen reader compatibility, network errors, and unexpected filtering of responses. These issues hinder accessibility and functionality, causing frustration among users who rely on Copilot for coding assistance.
- Feature Requests and Enhancements: Users have submitted various feature requests for Visual Studio Code, such as maximizing new windows by default, adding a "favorite folders" functionality, and improving accessibility features. These requests aim to enhance user experience and streamline workflows within the editor.
- Performance Problems: Visual Studio Code users have reported performance issues, including high CPU usage, lag in terminal output, and unresponsive behavior. These problems affect productivity and require users to find temporary solutions or await updates for resolution.
- Agent Mode and MCP Issues: Users have experienced issues with Agent Mode and Managed Control Points (MCP) in Visual Studio Code, including problems with command execution and configuration recognition. These issues limit the functionality of these features and require troubleshooting to resolve.
- Documentation and Configuration Discrepancies: Discrepancies between Visual Studio Code's documentation and actual functionality have been reported, causing confusion and inconsistent behavior. Users have noted issues with configuration settings not aligning with documented instructions, leading to runtime errors.
- Network and Connection Errors: Users have encountered network-related errors in Visual Studio Code, such as failed requests and connection issues, often linked to firewall settings or DNS configurations. These errors disrupt the use of online features and require network troubleshooting.
- User Interface and Usability Concerns: Visual Studio Code users have raised concerns about the user interface and usability, including issues with notification options, toolbar design, and window state management. These concerns highlight areas for potential improvement to enhance user satisfaction.
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 (Frustration expressed, Sarcasm used, Repeated demands for fixes.)
- This GitHub conversation involves multiple users expressing frustration over a persistent issue with a software feature. The original poster, username1, exhibits a tone of exasperation and urgency, demanding a fix for a long-standing problem. Username2 echoes this sentiment, sarcastically acknowledging the novelty of the issue and suggesting a temporary workaround. Username3 agrees with the previous comments, reinforcing the shared dissatisfaction. The conversation is marked by a shared sense of frustration and a call for prioritizing basic functionality over new features.
-
Semantic Search Overrides Core Search UI/UX, Disrupts Workflow and Removes Essential Options
- Toxicity Score: 0.55 (Frustration expressed, critical tone, potential for escalation.)
- This GitHub conversation involves a user expressing frustration over the implementation of a feature in VSCode, with a tone that is critical and somewhat sarcastic. The user, who remains unnamed, is dissatisfied with the perceived lack of attention to core functionality and the disruptive nature of new features. The conversation is marked by a detailed critique of the user interface and user experience issues, with the user providing specific examples and suggestions for improvement. The sentiment is predominantly negative, with a focus on the disconnect between user needs and development priorities.
-
- Toxicity Score: 0.70 (Strong language, High frustration, Repeated emphasis on issues.)
- This GitHub conversation involves a user expressing significant frustration with a feature, using strong language to convey their annoyance. The tone is highly negative, with the user detailing multiple grievances about the feature's suggestions and its impact on their workflow. The intensity of the language and the repeated emphasis on the issues suggest a high level of dissatisfaction.
-
- Toxicity Score: 0.55 (Frustration expressed, Lack of resolution, Repeated issue reports.)
- This GitHub conversation involves a user expressing frustration over a persistent issue with VSCode's shell environment resolution, despite attempts to modify settings and configurations. The user, who appears to be the original poster, is dissatisfied with the suggested solutions and the need to alter their shell profile for VSCode's functionality. Another user comments, sharing a similar experience and detailing their troubleshooting efforts, which have also been unsuccessful. The tone of the conversation is one of frustration and dissatisfaction, with a focus on the perceived intrusiveness of the feature and the lack of a straightforward configuration option to disable it.
-
- Toxicity Score: 0.65 (Strong language, High frustration, Lack of resolution)
- This GitHub conversation involves a single user expressing intense frustration and dissatisfaction with a recurring issue, using strong language to convey their emotions. The tone is highly negative and exasperated, with no interaction from other users yet.
-
- Toxicity Score: 0.75 (Offensive language, violation of conduct, corrective response.)
- This GitHub conversation involves a user, md-random, expressing strong frustration and using offensive language in their initial post, which triggers a response from another participant who points out the violation of the community's code of conduct. The tone of the conversation is tense, with the initial comment being aggressive and the response being corrective, aiming to de-escalate the situation by referencing community guidelines.
-
- Toxicity Score: 0.55 (Frustration expressed, negative sentiment, potential for escalation.)
- This GitHub conversation involves a user expressing frustration over a service issue, specifically regarding AI filters that are perceived as overly restrictive. The user, identified by their username, conveys a tone of exasperation and urgency, highlighting the impact on their workflow and expressing dissatisfaction with the service they are paying for. The sentiment is predominantly negative, with a clear request for the removal of the filters to improve usability. The conversation is marked by a strong emotional response, which could potentially trigger tension if not addressed constructively.
-
- Toxicity Score: 0.75 (Aggressive language, strong emotional tone, potential for defensive responses.)
- This GitHub conversation involves a single user expressing intense frustration with a service, using strong and aggressive language to describe their dissatisfaction with the product's performance and pricing model. The tone is highly critical and emotional, with the user feeling wronged by the perceived inadequacies and additional costs. There are no responses from other users, but the initial comment sets a confrontational tone that could trigger defensive or equally aggressive replies if others were to engage.
-
- Toxicity Score: 0.65 (Frustration, Criticism of process, Exasperation, Lack of resolution.)
- This GitHub conversation involves three users, with the initial user expressing frustration over a technical issue. The first comment by another user suggests a potential solution, but the original poster responds with increased frustration, criticizing the complexity and perceived inefficiency of the setup process. The tone becomes more exasperated as the user describes their attempts to resolve the issue, including using code from an AI tool, which did not work. The conversation concludes with the user expressing disbelief at the necessity of using workarounds, indicating a high level of dissatisfaction.
-
- Toxicity Score: 0.65 (Strong negative sentiment, dismissive language, comparison to competitors.)
- This GitHub conversation involves a user expressing strong dissatisfaction with recent updates, using a frustrated and dismissive tone towards the developers' work. The sentiment is negative, with the user comparing the system unfavorably to a competitor's product. The trigger of tension appears to be the perceived inadequacy of the updates and their impact on the system's value.
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: 46
Key Open Pull Requests
1. Adopting variable fonts: This pull request introduces the capability to use variable fonts in the Visual Studio Code editor, although it acknowledges that there are unresolved issues with line break computations that will be addressed in a future update.
- URL: pull/252308
- Merged: No
- Associated Commits: 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, eda00, fc7d7, 13210, 486be, e16b5, 327dc, b9cc8, 9d58a, ff1f0, 148c8, 299b1, a41b8, 0acbd, cb5a2, 64dc6, 62c71, 602b6, 26006, 58df4, 87bfa, 236cf, 6fd96, 1e424, 6e2bf, ba098, ef376, de396, b12e2, 7e68f, 2906d, cbb6a, c1f60, f9952, d9db8, dd8ac, da4c3, befd4, 02a00, 0485a, 88a85, c7eeb, 8b386, 30a25, 48718, c0b14, 89e82, e7f3b, e309b, cd129, c59a5, 2991e, d186c, c4ecb, 6d3ac, f3133, a7438, 3c9bc, 39bf8, 07032, 1bf27, 70957, 5562e, 4360c, 6d287, 638bc, 8b40d, 815c5, 24f2e, 25cf2, 0e810, 2fdb6, 95d3b, a5f02, 9ad71, 85d10
2. chat - add agent subcommand: This pull request introduces a new agent subcommand to the chat functionality in the Visual Studio Code project, as indicated by the title and the initial commit message.
- URL: pull/252588
- Merged: No
- Associated Commits: 1fb35, 89414, 04e18, 4fa0d, 03eb9, 60135, 7abb9, 30481, 5b5ed, ebc4f, 267d6, 423fb, c6bca, 04e0b, 85dc1, 76ab7, 9aeaa, 36d54, 87bb8, 0559c, 6e04a, b24e8, c4a4b
3. Engineering - add GitHub action stub: This pull request involves adding a GitHub action stub to the project, with multiple commits detailing various adjustments and tests such as adding and removing tasks, changing operating systems for the runner, caching node_modules, and debugging environment variables to optimize the continuous integration process.
- URL: pull/252544
- Merged: No
- Associated Commits: 1c594, c4f92, 0c779, 5aa44, 888d1, 7b03d, 309d3, 19b17, 44369, af65f, 40739, a8892, de653, a389e, 442d6, 55e7f, b999d, ced65
Other Open Pull Requests
- Deprecation of Extensions: This topic involves the introduction of a feature to support the deprecation of specific versions of extensions in the Visual Studio Code project. The pull request allows versions at or below a specified deprecated version to be marked as deprecated, and includes various code refinements and reversions to optimize the implementation.
- Fetch Web Page Tool Update: The pull request addresses an issue with the fetch web page tool by modifying it to only handle HTTP and HTTPS schemes. This prevents errors when processing non-HTTP MCP resource URIs and includes updates to the code and tests to ensure unsupported schemes are treated as invalid with clear user feedback.
- Code Refactoring for Maintainability: Several pull requests focus on refactoring code to enhance quality, readability, and maintainability. These include extracting magic numbers and strings into constants, decomposing large methods, and improving code structure and documentation while preserving existing functionality.
- Security Vulnerability Mitigation: This pull request addresses security vulnerabilities in the Visual Studio Code project by updating specific package files. The updates mitigate issues identified by Snyk, specifically targeting a known vulnerability.
- Task Ordering Consistency: The pull request addresses the issue of terminal tabs being reordered arbitrarily when re-running all tasks. It modifies the task restart process to ensure terminals are recreated in the correct order, improving task ordering consistency.
- Authentication Badge Cleanup: This pull request addresses an issue where authentication badges in the Account Menu were not disappearing after a successful sign-in. It introduces a helper function for order-independent scope comparison and updates the cleanup logic accordingly.
- Color Picker Functionality: The pull request addresses the issue of the standalone color picker not functioning correctly with multiple cursors. It modifies the function to detect multiple selections and apply color insertions at all cursor positions.
- Accessibility Improvements: Several pull requests focus on addressing accessibility issues, such as ensuring proper
aria-labelsfor screen readers and correcting the positioning of the screen reader box for multi-line selections.
- Hover Feature Enhancements: Multiple pull requests address issues related to the hover feature, including ensuring the hover updates correctly to display definition previews and preventing layout shifts during asynchronous content loading.
- Color Format Support: The pull request updates regex patterns to support additional color formats, such as 3-digit and 4-digit hex color formats and CSS Level 4 syntax variants. This ensures compatibility with modern CSS syntax.
- Terminal Suggest Configuration: This pull request aims to enhance the discoverability of the terminal suggest configuration by highlighting the 'Learn More' action. It is pending a live link before merging.
- ThemeColor API Enhancement: The pull request proposes the addition of an
asHexmethod to theThemeColorAPI. This enables users to obtain the hexadecimal representation of theme colors, enhancing interoperability with external libraries.
- Hover Widget Scrollbar Accessibility: The pull request addresses the issue of hover widgets covering the vertical scrollbar by implementing logic to reserve additional space. This ensures the scrollbar remains accessible, particularly in split editor views.
- Sticky Scroll Performance: This pull request addresses a performance issue in the sticky scroll feature by correcting the array used for calculating the minimum content width. It eliminates unnecessary layout recalculations and reduces scroll stuttering.
- Extension Restart Button: The pull request adds a restart button to the Running Extensions view, ensuring consistency with the main Extensions view. It modifies the action bar to include the
ExtensionRuntimeStateAction.
- Handling "Thinking Data": This pull request introduces an initial proposal for handling "thinking data" within the project. It includes functionality to persist this data in the history.
- Publishing Pipeline Update: The pull request modifies the main publishing pipeline to duplicate built packages for signing with a new key. This enables uploads to new repositories and allows Linux users to install VS Code without security warnings.
- LSP Terminal Completions: This pull request aims to enhance the language server protocol (LSP) terminal completions by refining the feature. It addresses the challenge of disabling upper shell completion when a sub-shell is entered.
- MCP Token Flag Reintroduction: The pull request aims to reintroduce the adoption of the MCP token flag in the Microsoft VSCode project. It follows its initial implementation and subsequent reversion.
- Search Provider Performance Measurement: This pull request introduces a feature to measure the performance of different search providers in the Visual Studio Code project. It is indicated by the title and the commit message.
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: 136
Key Closed Pull Requests
1. layout - allow to maximise the secondary sidebar: This pull request addresses the issue of allowing users to maximize the secondary sidebar in Visual Studio Code, as referenced in issue #248807, and includes multiple commits to implement this feature, such as enabling restoration on startup and performing necessary cleanups.
- URL: pull/252301
- Merged: Yes
- Associated Commits: bbc4f, c8776, 2062c, 9b05b, 44191, 637ff, 72c67, b1e26, e8247, 3ffce, 3a500, b892f, c80e9, c1240, bc006, c4545, d3f43, b0644, bfb63, 10d49, 49757
2. Waveform real: This pull request involves the addition of a waveform viewer to the project, with multiple commits detailing the development process, including cleanup, title changes, and the successful implementation of a default extension using Surfer, although it was ultimately not merged.
- URL: pull/252254
- Merged: No
3. feat: Create initial structure for platform documentation: This pull request establishes the foundational directory structure and initial Markdown files for comprehensive platform documentation, including placeholder content and outlines for key areas such as Getting Started, System Architecture, Configuration Guide, Deployment Guide, and various integrations, with the goal of creating a modular and extensible documentation suite that supports theme customization, feature extension, and robust operational practices.
- URL: pull/252258
- Merged: No
Other Closed Pull Requests
- Inline Completion Suggestions in Unsupported Shells: This topic addresses the issue of inline completion suggestions appearing for unsupported shell types in Visual Studio Code. The pull requests implement changes to prevent the suggest widget from showing in such cases and update terminal suggest settings to reflect supported shells.
- Task Management Enhancements: This topic introduces a new command in Visual Studio Code that allows users to restart all currently running tasks simultaneously. The feature is integrated into the Command Palette and Terminal menu, providing user feedback on task restarts.
- Chat Widget and Remote Coding Agent: This topic involves enhancements to the chat widget in Visual Studio Code, including a 'Remote coding agent' entry point and integration of remote agent state. The changes establish the initial framework, integrate history functionality, and make the feature demo-able.
- Layout and Sidebar Enhancements: This topic focuses on enhancing the layout functionality in Visual Studio Code, allowing users to maximize the secondary sidebar and control its maximized state on startup. The pull requests address layout adjustments and related formatting changes.
- Accent Color Customization: This topic adds support for accent color customization on the windows border in Visual Studio Code. The pull request addresses and fixes issue #242980 and has been successfully merged into the main branch.
- Linkable Chat Prompts and Modes: This topic introduces the ability to create linkable chat prompts, instructions, and modes using
vscode://links. The pull request addresses and fixes the issue tracked at https://github.com/microsoft/vscode-copilot/issues/12944.
- Editing and Chat Features: This topic addresses issues related to editing in inline and quick chat features by improving the overlay and removing the 'x' from request edits. The pull requests ensure chat modes are correctly matched in edits.
- A/B Testing for Startup Experiences: This topic introduces a new
CoreExperimentationServiceto manage A/B testing experiments for Visual Studio Code startup experiences. The service allows for the random assignment of users into different experimental groups to test various startup layouts.
- Handling Untrusted Workspaces: This topic addresses the handling of untrusted workspaces in the VSCode project by implementing special treatment for them. The pull request includes a specific fix and several minor updates.
- Edit Source Tracking and API: This topic implements edit source tracking through a proposed API and addresses issue #18517 from the vscode-copilot repository. The pull request includes commits for fixing continuous integration and tests.
- Shell Current Working Directory Handling: This topic addresses issues by converting the shell current working directory (cwd) to a URI on the extension host. The pull request introduces a new method
ITerminalInstance.getCwdResourcewith future tests.
- Zsh Parameter Expansion Fix: This topic addresses an issue by adding the '-n' option to parameter expansion in Zsh and surrounding
${(P)var+_}with double quotes. The pull request has been successfully merged.
- Distro Bump: This topic involves a "Distro bump" for the Microsoft VSCode project, indicating an update or upgrade to the distribution. The pull request has been successfully merged into the main branch.
- Humorous Rebranding: This topic proposes a humorous rebranding of the Visual Studio Code project, including updates to documentation and scripts to reflect a "Joke Studio" theme. The changes include renaming the project to "Visual Studio Comedy."
- Toggled View Actions in Layout: This topic addresses and resolves an issue related to toggled view actions in the layout of the Visual Studio Code project. The pull request has been successfully merged into the main branch.
- Insiders Filters in CSS: This topic introduces support for insiders filters in the CSS and dynamically updates the filter variables based on the application name. The pull request is part of the Visual Studio Code project on GitHub.
- Edit Reason Refactoring: This topic involves refactoring related to "edit reason" in the Microsoft VSCode project. The pull request addresses issues such as a missing service and fixing tests.
- User MCP Servers: This topic implements a first-class resource for user MCP servers in the Microsoft VSCode project. The pull request includes changes such as reverting previous MCP JSON modifications and properly implementing workspace MCP servers.
- TypeScript Expression Evaluation: This topic addresses an issue where hovering over TypeScript expressions containing the non-null assertion operator
!during debugging would incorrectly evaluate only partial segments. The pull request modifies the regex pattern to include the!character.
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.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
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 |
|---|---|---|---|---|
| Copilot | 291 | 64 | 0 | 16 |
| meganrogge | 165 | 10 | 28 | 101 |
| bpasero | 148 | 21 | 43 | 76 |
| connor4312 | 61 | 8 | 8 | 79 |
| Tyriar | 36 | 5 | 36 | 63 |
| aiday-mar | 73 | 7 | 9 | 42 |
| TylerLeonhardt | 53 | 9 | 12 | 37 |
| aeschli | 68 | 16 | 1 | 24 |
| roblourens | 32 | 16 | 15 | 41 |
| joshspicer | 50 | 15 | 9 | 11 |
Don't miss what's next. Subscribe to Weekly Project News: