Weekly GitHub Report for Vscode: June 16, 2025 - June 23, 2025 (12:05:37)

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
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

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.

1. Bug: Chinese IME punctuation duplicates in v1.101 when Vim extension is active: This issue reports a bug in Visual Studio Code version 1.101 where using a Chinese Input Method Editor (IME) with the Vim extension results in duplicated punctuation marks. The problem is identified as a regression in the core of VS Code, as it does not occur in earlier versions, indicating a breaking change between the March and May 2025 releases.

   • The comments discuss the issue's occurrence with other characters and IMEs, suggest disabling the experimentalEditContextEnabled setting as a workaround, and mention ongoing investigations and discussions with the IME team to address the problem. A related issue is filed separately, and a potential fix is identified but not yet confirmed.
   • Number of comments this week: 12

2. ghost saves trash all the code: This issue describes a bug in Visual Studio Code where the application unexpectedly prompts the user to save a large number of files, many of which the user has not been actively working on, and subsequently reverts code to an earlier state, causing significant data loss. The user reports that this problem has occurred multiple times, even after applying updates, and suspects it may be related to using Copilot in Agent mode, although the exact cause remains unclear.

   • Multiple users report experiencing similar issues with unsaved files and code reversion, suspecting a link to Copilot's Agent mode. Despite updates, the problem persists, causing significant disruption and data loss, with users attempting various workarounds to mitigate the impact.
   • Number of comments this week: 11

3. Unable to resolve your shell environment: Bad escaped character in JSON at position 376 (line 2 column 375): This issue is about a persistent error notification in Visual Studio Code, where the user encounters a "Bad escaped character in JSON" error when trying to resolve the shell environment, even after updating to the latest version. The problem seems to be related to the use of certain package managers like fnm or vfox, which may cause issues with JSON escaping in the PowerShell configuration.

   • The comments discuss attempts to reproduce the issue using nightly insider builds, with some users confirming the error persists in preview versions. A potential cause is identified as the use of the fnm package manager, and a user suggests that removing fnm environment variables resolves the issue. Another user shares a solution involving modifying the PowerShell profile to avoid JSON escape issues, suggesting similar adjustments for other package managers like nvm or fnm.
   • Number of comments this week: 11

4. launching vscode and shows "Unable to resolve your shell environment“: This issue involves a problem with launching Visual Studio Code on Windows 11, where a notification appears stating "Unable to resolve your shell environment" due to an unexpected exit code from the spawned shell. The user reports that this issue persists even after reinstalling the application and adjusting the shell environment resolution timeout, but it does not occur when launching VS Code with the --verbose flag in PowerShell.

   • Multiple users report similar issues after updating to the latest version of VS Code, with some noting that the problem does not occur when launching from the command line, suggesting it might be related to how the shell environment is resolved. Some users have found workarounds by rolling back to previous versions or adjusting their shell settings, while others speculate that recent updates or specific configurations might be causing the issue. The discussion includes suggestions to use VS Code Insiders for potential fixes and to provide detailed logs for further investigation.
   • Number of comments this week: 10

5. VSCode 1.101 is injecting numerical environment variables into my remote linux Terminal environments, with the characters for "JSON.stringify(process.env)": This issue describes a bug in VSCode version 1.101 where numerical environment variables are being injected into remote Linux terminal environments, specifically when using the Remote SSH extension, and these variables appear to represent the string JSON.stringify(process.env). The problem does not occur when downgrading to VSCode version 1.100.3, indicating a potential regression or change in behavior in the newer version.

   • The comments discuss troubleshooting steps, including changing the shell and downgrading extensions, but the issue persists. It is discovered that a command in the user's ~/.profile file, specifically ps uxfw, is causing the problem, and removing or modifying this command resolves the issue. Another user confirms the same workaround, suggesting the environment variable parsing logic might be affected by the output of ps uxfw.
   • Number of comments this week: 9

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.

1. 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 highlights the need for an option to render markdown generated by code cells in the output, allowing for dynamic titles and content to be displayed, enhancing the functionality and interactivity of notebooks within VS Code.
2. 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-window or ?reuse-window does 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.
3. ${userHome} in a task command creates bad paths: This issue involves a problem with the ${userHome} variable in a task command within a tasks.json file, which creates incorrect paths when the task type is set to "process" in Visual Studio Code. The incorrect path format results in an error stating that the terminal process could not be started because the path to the executable does not exist, whereas using ${env:USERPROFILE} instead of ${userHome} generates a correct path and resolves the issue.
4. 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 become visible once the main window is restored, suggesting a potential issue with the remote connection entering a "sleep" state when the main window is minimized.
5. 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 as a question mark in Visual Studio Code. The problem persists even when all extensions are disabled, and the character is correctly rendered in browsers like Firefox, indicating a potential rendering issue within the VS Code environment.

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: 254

Summarized Issues:

• Performance Issues in Visual Studio Code: Users have reported various performance problems in Visual Studio Code, including lag, crashes, and unresponsiveness. These issues occur across different systems and configurations, often requiring users to revert to older versions or disable extensions to regain functionality.
  • microsoft/vscode/issues/251540, microsoft/vscode/issues/251574, microsoft/vscode/issues/251604, microsoft/vscode/issues/251622, microsoft/vscode/issues/251758, microsoft/vscode/issues/251865, microsoft/vscode/issues/251897, microsoft/vscode/issues/252019

• Bugs in Visual Studio Code: Several bugs have been identified in Visual Studio Code, affecting features like terminal activation, file explorer, and syntax highlighting. These bugs disrupt user workflows and often require workarounds or fixes in future updates.
  • microsoft/vscode/issues/251553, microsoft/vscode/issues/251557, microsoft/vscode/issues/251563, microsoft/vscode/issues/251569, microsoft/vscode/issues/251596, microsoft/vscode/issues/251650, microsoft/vscode/issues/251651, microsoft/vscode/issues/251676, microsoft/vscode/issues/251685, microsoft/vscode/issues/251696, microsoft/vscode/issues/251699, microsoft/vscode/issues/251701, microsoft/vscode/issues/251707, microsoft/vscode/issues/251791, microsoft/vscode/issues/251803, microsoft/vscode/issues/251806, microsoft/vscode/issues/251828, microsoft/vscode/issues/251832, microsoft/vscode/issues/251839, microsoft/vscode/issues/251841, microsoft/vscode/issues/251871, microsoft/vscode/issues/251874, microsoft/vscode/issues/251901, microsoft/vscode/issues/251903, microsoft/vscode/issues/251906, microsoft/vscode/issues/251907, microsoft/vscode/issues/251966, microsoft/vscode/issues/251968, microsoft/vscode/issues/251972, microsoft/vscode/issues/251975, microsoft/vscode/issues/251979, microsoft/vscode/issues/251980, microsoft/vscode/issues/251982, microsoft/vscode/issues/251991, microsoft/vscode/issues/251992, microsoft/vscode/issues/251993, microsoft/vscode/issues/251995, microsoft/vscode/issues/251998, microsoft/vscode/issues/252009, microsoft/vscode/issues/252010, microsoft/vscode/issues/252018, microsoft/vscode/issues/252022, microsoft/vscode/issues/252024, microsoft/vscode/issues/252025, microsoft/vscode/issues/252026, microsoft/vscode/issues/252034, microsoft/vscode/issues/252037, microsoft/vscode/issues/252038, microsoft/vscode/issues/252041, microsoft/vscode/issues/252043, microsoft/vscode/issues/252046, microsoft/vscode/issues/252049, microsoft/vscode/issues/252052, microsoft/vscode/issues/252053, microsoft/vscode/issues/252054

• Feature Requests for Visual Studio Code: Users have submitted various feature requests to enhance Visual Studio Code, including improvements to the user interface, new functionalities, and better integration with existing tools. These requests aim to improve productivity and user experience.
  • microsoft/vscode/issues/251559, microsoft/vscode/issues/251561, microsoft/vscode/issues/251567, microsoft/vscode/issues/251570, microsoft/vscode/issues/251576, microsoft/vscode/issues/251580, microsoft/vscode/issues/251586, microsoft/vscode/issues/251590, microsoft/vscode/issues/251592, microsoft/vscode/issues/251603, microsoft/vscode/issues/251609, microsoft/vscode/issues/251615, microsoft/vscode/issues/251616, microsoft/vscode/issues/251621, microsoft/vscode/issues/251653, microsoft/vscode/issues/251663, microsoft/vscode/issues/251682, microsoft/vscode/issues/251687, microsoft/vscode/issues/251689, microsoft/vscode/issues/251691, microsoft/vscode/issues/251741, microsoft/vscode/issues/251745, microsoft/vscode/issues/251746, microsoft/vscode/issues/251747, microsoft/vscode/issues/251783, microsoft/vscode/issues/251784, microsoft/vscode/issues/251785, microsoft/vscode/issues/251807, microsoft/vscode/issues/251812, microsoft/vscode/issues/251813, microsoft/vscode/issues/251816, microsoft/vscode/issues/251819, microsoft/vscode/issues/251827, microsoft/vscode/issues/251833, microsoft/vscode/issues/251837, microsoft/vscode/issues/251844, microsoft/vscode/issues/251845, microsoft/vscode/issues/251846, microsoft/vscode/issues/251848, microsoft/vscode/issues/251849, microsoft/vscode/issues/251850, microsoft/vscode/issues/251857, microsoft/vscode/issues/251960, microsoft/vscode/issues/251967, microsoft/vscode/issues/251973, microsoft/vscode/issues/251983, microsoft/vscode/issues/251987, microsoft/vscode/issues/251988, microsoft/vscode/issues/252001, microsoft/vscode/issues/252006, microsoft/vscode/issues/252008, microsoft/vscode/issues/252011, microsoft/vscode/issues/252012, microsoft/vscode/issues/252015, microsoft/vscode/issues/252027, microsoft/vscode/issues/252028, microsoft/vscode/issues/252029, microsoft/vscode/issues/252033, microsoft/vscode/issues/252035, microsoft/vscode/issues/252036, microsoft/vscode/issues/252045

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: 101

Summarized Issues:

• Input Method Issues in VSCode: Users have reported problems with input methods in Visual Studio Code, particularly when switching between languages or using specific input methods. These issues include underlined prompts without a candidate box for Chinese text entry and the failure of the candidate list to appear with the Microsoft Pinyin IME. issues/251518, issues/251543, issues/251913

• Performance and Crashes in VSCode: Several issues have been reported regarding performance problems and crashes in Visual Studio Code. These include high CPU usage by the "Code Helper (Renderer)" process and crashes when starting a notebook with many cells. issues/251584, issues/251796

• Terminal Issues in VSCode: Users have encountered various terminal-related issues in Visual Studio Code, such as unexpected behavior with keybindings and delays in screen reader announcements. These problems affect productivity and the expected interactive flow of the terminal. issues/251652, issues/251715, issues/251734

• Copilot and AI Features in VSCode: There are reports of unwanted AI-related icons appearing in the interface and issues with Copilot's functionality. Users have also requested features like a usage dashboard and a marketplace for custom Copilot modes. issues/251539, issues/251779, issues/251814

• Remote Development Issues in VSCode: Problems have been reported with remote development features in Visual Studio Code, including connection issues with remote servers and the TypeScript server crashing in Codespaces. These issues hinder the ability to work effectively in remote environments. issues/251541, issues/252039, issues/252040

• Feature Requests for VSCode: Users have submitted various feature requests to enhance Visual Studio Code's functionality. These include requests for custom tab colors, a native PDF preview, and a command to delete all comments in a code file. issues/251693, issues/251984, issues/251683

• Bug Reports and Templates in VSCode: Many issues have been submitted using bug report templates, often lacking specific details about the problem. These templates prompt users to disable extensions and use the latest Insiders build to verify if the issue persists. issues/251550, issues/251673, issues/251817

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.

1. ghost saves trash all the code

   • Toxicity Score: 0.65 (Repeated frustration, unresolved issue, escalating complaints.)
   • This GitHub conversation involves multiple users, with the primary user expressing significant frustration over a recurring issue with their code being unexpectedly altered or deleted, which they attribute to a software bug. The tone is predominantly negative, with the user repeatedly reporting the problem and expressing dissatisfaction with the lack of resolution, despite updates. Other users acknowledge similar issues, adding to the overall sentiment of annoyance and urgency. The conversation is marked by repeated reports of the problem, attempts to troubleshoot, and a strong demand for a fix, indicating a high level of tension and dissatisfaction.

2. oh shit-my git broke

   • Toxicity Score: 0.55 (Dismissive response, Lack of detail, Frustration in initial report.)
   • This GitHub conversation involves a user who initially reports an issue with a frustrated tone, as indicated by the title and lack of detail in the report. Another user responds with a dismissive and critical tone, demanding more details. The conversation is tense, with the initial user attempting to provide more information by sharing a screenshot.

3. Feature Request: Export Diff View in VS Code

   • Toxicity Score: 0.55 (Sarcasm, dismissive attitude, potential for misunderstanding.)
   • This GitHub conversation involves two users, with the first user questioning the practicality of the proposed feature in a neutral tone, while the second user responds with sarcasm and a dismissive attitude, indicating frustration with those who may not understand diff files. The interaction suggests a potential for tension due to the sarcastic and condescending response.

4. latest upate 6/20/25: VScode drops connections to remote then VScode crashes

   • Toxicity Score: 0.55 (Frustration expressed, negative tone, user switching to competitor.)
   • This GitHub conversation involves multiple users expressing frustration over a recurring issue with a software update, with one user detailing their experience of rolling back to a previous version to avoid crashes. The tone is generally negative, with users expressing dissatisfaction and disappointment. Tension arises as one user decides to switch to a competing product, citing better performance and fewer issues.

5. AI chat is down on all models

   • Toxicity Score: 0.65 (Negative sentiments, Lack of constructive dialogue, Escalating frustration)
   • This GitHub conversation involves multiple users expressing dissatisfaction with a software issue. The initial comment by a user reports a technical problem, which is followed by another user expressing frustration and comparing the software unfavorably to a competitor. The tone escalates as another user bluntly criticizes the software. The conversation is marked by negative sentiments and a lack of constructive dialogue, with users expressing frustration and disappointment.

---

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: 24

Key Open Pull Requests

1. Allowing to define variable font sizes: This pull request introduces the ability to define variable font sizes in the Visual Studio Code editor, addressing issues related to line wrapping and dynamic line heights when decorations are present, and includes numerous commits for implementing, testing, and refining these changes.

• URL: pull/251926

• 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, 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, ddb24, 7f3ff, e6e12, f2268, f9c90, 43d8b, 08c68, 783dd, 58856, e5497, 175d2, 9ebf6, e934d, 44d35, 6dedc

2. Allow tasks to be run via terminal suggest: This pull request introduces a new feature that allows users to execute tasks directly from terminal suggestions in Visual Studio Code by implementing a TaskCompletionProvider that offers task completions based on user input, supports command execution, and includes smart filtering and sorting to enhance user experience.

• URL: pull/252002

• Merged: No

• Associated Commits: 68d3c, 90ed9, 52654, d42a7, 36eb1, 76623, 230c9, 529ae

3. Determine how often EOL changes for nb cells: This pull request aims to determine the frequency of end-of-line (EOL) changes for notebook cells in the Visual Studio Code project, addressing issue #18287, and includes several commits for implementing the feature, fixing tests, and making updates.

• URL: pull/251768

• Merged: No

• Associated Commits: bf1a5, 87281, 194f6, faa05, 91715

Other Open Pull Requests

• JSON File-Based Policy Support: This topic involves implementing JSON file-based policy support as the default on Linux systems, which eliminates the need for the __enable-file-policy command line flag. The pull request includes modifications to the policy service creation logic, platform-specific policy service selection, comprehensive unit tests, and maintains backward compatibility to facilitate easier deployment of JSON-based policies by enterprise administrators.
  • pull/251642

• Mobile UI Redesign for Android: This topic covers a partial mobile UI redesign for Visual Studio Code to optimize its interface for Android smartphones. The pull request includes features like a collapsible sidebar, a bottom navigation bar, and a floating action button, while addressing challenges such as incomplete integration of the navigation bar and untested Android functionality.
  • pull/251909

• FreeBSD Support: This topic introduces changes to add support for FreeBSD in the project by treating it similarly to Linux. The pull request includes specific modifications such as adding checks for process.platform === 'freebsd', redirecting error messages, skipping glibc checks, and adjusting command arguments to ensure compatibility with both Linux and FreeBSD.
  • pull/251970

• Test Rerun and Debug Actions: This topic introduces new features that add rerun and debug actions for tests that failed in the last run. The pull request addresses issue #244870 in the Microsoft VSCode project.
  • pull/251679

• Edit Previous Requests Feature: This topic introduces a feature that allows users to edit previous requests in the project. The pull request includes commits for editing requests, merging updates from the main branch, and performing minor code cleanup, as part of addressing an issue referenced at https://github.com/microsoft/vscode-copilot/issues/18304.
  • pull/251732

• Search Confirm Replace All Option: This topic introduces a new configuration option, search.confirmReplaceAll, to the VS Code settings. The pull request allows users to disable the confirmation dialog for "Replace All" operations in the Search view, enhancing user control and aligning with existing confirmation settings like explorer.confirmDelete.
  • pull/251760

• Interactive HTML Article Generation: This topic introduces a Python script designed to generate interactive HTML articles using the OpenRouter API and the Claude 3.5 Sonnet model. The pull request features automated article creation from a list of topics, interactive HTML output with embedded quizzes, comprehensive error handling, and a complete suite of documentation and tests.
  • pull/251818

• Dialog Component Validation Hook: This topic introduces an onBeforeButtonClick hook to the Dialog component. The pull request allows developers to implement validation logic that can prevent the dialog from closing if certain conditions, such as form input validation, are not met, enhancing user experience by ensuring dialogs only close when inputs are valid.
  • pull/251900

• Terminal Completion Escaping Fix: This topic addresses issue #249024 by fixing the escaping mechanism for terminal completions in zsh, bash, and fish shells. The pull request includes multiple commits with adjustments to the escaping logic and the addition of a test file.
  • pull/251989

• Terminal Suggest Telemetry Enhancement: This topic enhances the terminal suggest telemetry in the project by adding a providerId field to the terminal.suggest.acceptedCompletion telemetry event. The pull request allows for better analysis of the effectiveness and issues of different completion providers by identifying which provider supplied each accepted completion.
  • pull/252016

• Minor Typo Corrections: This topic addresses a series of minor typo corrections in comments and error messages within the codebase. The pull request updates files such as textureAtlas.ts, editorOptions.ts, and gutterIndicatorView.ts to improve clarity and accuracy.
  • pull/252021

• Package/Extension Installation Interface Enhancement: This topic introduces a new feature that enhances the package/extension installation interface by extending the CountBadge to act as a toggle button. The pull request allows users to filter a dropdown list to display only selected items, improving user experience when managing long lists, particularly in the context of python-environments.
  • pull/251542

• Text Rendering Check Enhancement: This topic proposes an enhancement to the VS Code editor by introducing a check to prevent text rendering when the view node is hidden. The pull request aims to improve the reusability of the Monaco editor for projects like Eclipse Theia, which have different editor lifecycles compared to the VS Code workbench.
  • pull/251583

• Menubar Blur Fix on Android: This topic addresses an issue in the Visual Studio Code project by preventing the menubar from blurring when the window is resized on Android devices. The pull request is indicated by the commit titled "Fix: menubar blur onresize for android."
  • pull/251724

• Pipeline Autobaselining Config Update: This topic involves updating the PipelineAutobaseliningConfig.yml file in the Microsoft VSCode repository. The pull request is indicated by the commit message and the associated commit link.
  • pull/251842

• Notebook Troubleshooting Tool Layout Update: This topic aims to simplify the process of updating layouts within the notebook troubleshooting tool in the Visual Studio Code project. The pull request is indicated by its title and the associated commit message.
  • pull/251852

• Chat Attachment Pill Removal Enhancement: This topic aims to enhance the user experience by allowing users to remove a chat attachment pill from the chat context with a middle-click. The pull request provides an alternative to the existing method of clicking the 'x' icon, addressing issue #251877.
  • pull/251878

• Datadog Synthetics Configuration: This topic involves the creation of a new file named datadog-synthetics.yml in the Microsoft VSCode repository. The pull request likely pertains to setting up or configuring Datadog synthetic monitoring, as indicated by the commit message and the absence of a merge status.
  • pull/251946

• Preserve Focus Feature: This topic addresses issue #251241 by implementing the preserveFocus feature to maintain the editor's focus on either the source or disassembly when selecting different stack frames. The pull request ensures that the focus only shifts to disassembly when the debugger stops due to an instruction breakpoint or step, and includes testing based on the reproduction steps provided in the issue.
  • pull/251964

• Forward Stacktrace Parser Bug Fix: This topic addresses a bug fix for the forward stacktrace parser in the Visual Studio Code project. The pull request is indicated by the title and commit message, and is currently open and not yet merged.
  • pull/252020

• Core Telemetry Enhancement: This topic aims to enhance the core telemetry of Visual Studio Code by adding a releaseDate attribute. The pull request is similar to a previous update made for extension telemetry, as detailed in the commit with SHA 96068111102ca015bebe7f94948e5c6747415923.
  • pull/252047

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: 121

Key Closed Pull Requests

1. Call composition type handler when doing composition: This pull request addresses the issue of calling the composition type handler during composition in the Visual Studio Code project, as referenced by the related issue https://github.com/microsoft/vscode/issues/251608, but it was not merged into the main codebase.

• URL: pull/251823

• Merged: No

• Associated Commits: 00e55, c9f19, af218, 0bbc5, 73f8b, 8cff3, c91a3, c5ccd, 1a41f, cdf40, 42a3a, 5e8f6, 8af45, a3beb, 1a2ba, 73f3c, b2203, ef716, 5e10a, 4e037, 053aa, b4021, 51df2, 32557, 3d2e7, a0287, 4f255, f4792, fcf63, fbb72, 0147a, 43322, da3bd, 510bd, 94a97, d24ba, a1e32, 7e4d8, 5d582, 997f7, de39a, acd3b, 99323, 3f25a, 8349c, daf79, b35b5, 6b415, 47fb4, f5c3e, 23f0f, 96419, f7f11, 10066, b1cd9, 6bfb5, 7a24d, 2aee1, fa298, 99b89, 9f296, 62f57, be489, 73a5b, b6636, d1d42, f91d7, 0ac81, 13d49, 44fd9, c367a, 31228, defae, 325c6, e3bc6, 0d63e, d1d67, 6a8e3, 8def6, 080c6, af66e, 5a79c, 76847, d03db, b104f, 6ec42, 48e47, 8ece0, 74430, cfa7c, 2eed3, 9913e, fc7a6, e680d, 89ba1, ba80b, c00b7, 0ab63, 08650, 90da5, 3aaf8, f62c7, 6582e, 6d279, 7e4e0, 77664, 31620, 5547e, f0aef, ea92c, 5d1bd, 2c4bd, 29235, fafd5, 4ea56, 64bbb, 3fdc0, 70f8e, 17447, a7208, 810f7, bc81f, eea8d, aa393, e2a90, 1ee09, 69d90, b3c13, 17241, 6faee, 23e71, 20b69, 9a0a5, a2cd4, aab65, 35c4a, 9cbca, a275f, 7346a, d4cda, e5dc1, 40df1, acbe4, 5c849, cb4bf, cc59a, 80f28, dd48c, a41ac, 44c0f, 5d83e, 5a501, a1d87, 3fb7f, 8328d, 6f5ee, 2d9d9, d4fc0, 82054, 4b990, c30a6, 8eb5d, b2e66, 24c0f, 943fa, 3a2ee, 335ad, 36d60, ed787, 01fbd, 48048, 2faba, 5bc1c, bbcaf, 8bb98, 6b237, 4bfe8, 4ff7a, 2cd6a, d59fa, 7c43b, d8e9e, 6c327, 9f755, 52725, 84658, 2b7ad, 57c04, 559c2, fde1c, a0d63, 03bce, 36518, 121bf, e5650, 26fbb, 13450, 51eba, 0140a, 66cc8, 1fdaf, 0f5ce, b31fc, b55c9, b406b, 887da, 3ecaa, cb99f, 82edd, 3e677

2. Implements https://github.com/microsoft/vscode-copilot/issues/18482 in core: This pull request addresses the implementation of a feature or fix related to issue #18482 from the vscode-copilot repository into the core of the Visual Studio Code project, as indicated by the title and the final commit message.

• URL: pull/251916

• Merged: No

• Associated Commits: bcf74, 310b0, ac930, 13b43, 2576f, e481d, 75a25, 99849, 7157e, e5b5f, d493d, 92182, 6ab62, e287c, b5291, e4d31, 11202, 8f5db, 7750a, e0ab7, ca903, 3e2cd, 12ddf

3. track latency from request -> showing terminal completions, indicate first shown for shell type and for window: This pull request, which is part of issue #251994, focuses on tracking the latency from the request to the display of terminal completions in Visual Studio Code, and includes enhancements to indicate the first shown completion for different shell types and window instances, as evidenced by multiple commits addressing implementation, bug fixes, and code simplifications.

• URL: pull/252007

• Merged: Yes

• Associated Commits: 21352, 71dfa, fda2f, 9ea7c, da63f, f5fea, 18e31, 27f27, 1224e, e0ec7, 2948a, de00d, 389a4, 93ac5, c1008, 5789a, 18d92, ab911, 6eeb1, 4ba4a, 8b074, 355b6

Other Closed Pull Requests

• Resource Completions Order and Presentation: This topic focuses on improving the order and presentation of resource completions by moving punctuation methods to the bottom of the list and eliminating duplicate entries. The changes enhance the overall organization and readability of the method list in the project.
  • pull/251922

• Terminal and Task Handling Improvements: Several pull requests address issues related to terminal command recognition and task handling in Visual Studio Code. These include ensuring terminal commands are recognized as completed to prevent hanging and updating task configurations to reflect changes in tasks.json.
  • pull/251655, pull/251755, pull/251759

• Color Picker and Regex Enhancements: The pull request modifies the regex pattern in defaultDocumentColorsComputer.ts to include positive lookbehind patterns. This change enables the detection of hex colors after common programming delimiters, improving usability without affecting existing functionality.
  • pull/251589

• Mobile Responsiveness and APK Automation: This pull request introduces mobile responsiveness to the web application and automates the generation of an Android APK. It integrates Capacitor, enhances CSS for smaller screens, and creates a workflow to build and upload the APK as a build artifact.
  • pull/251719

• AI Settings Search Prefetching: The pull request implements prefetching for AI settings search in the Settings editor by optimizing the search with performant algorithms. It initiates an AI search in the background for users with Copilot enabled, allowing instant toggling between non-AI and AI search results.
  • pull/251840

• Terminal Selection Mode and Loading Indicator: These pull requests introduce a new partial option for terminal selectionMode and a loading indicator to the SimpleSuggestWidget. The changes improve user feedback and address various issues, including bug fixes and style consolidations.
  • pull/251847, pull/251856

• Authentication and Sign-In Enhancements: Several pull requests focus on modernizing the authentication module and improving the sign-in page. These include adding light mode support, removing unnecessary notifications, and simplifying the authentication contribution logic.
  • pull/251895, pull/251509, pull/251511, pull/251512

• CLI Options and Subcommands Refinement: This pull request enhances the extensions/terminal-suggest module by refining CLI options and subcommands in code.ts. It includes changes like renaming arguments for clarity and adding new options, improving descriptions, and ensuring test coverage.
  • pull/251945

• Windows Agent and CI Fixes: These pull requests address issues related to the Windows 2022 agent for product builds and CI fixes. They involve reverting previous commits due to icon issues and removing deprecated proposals to fix CI issues.
  • pull/251560, pull/251610

• Quick Suggestions and File Handling: The pull requests introduce an experimental tag for quick suggestions delay and enhance file handling capabilities. They allow the resolution of realpath and provide a workaround for conflicts between IntelliSense and GitHub Copilot completion suggestions.
  • pull/251667, pull/251690

• TypeScript Comment Handling: This pull request refines the "onEnterRules" functionality in TypeScript to trigger only when the cursor is inside the body of a comment. It improves the behavior of comment handling in the Visual Studio Code editor.
  • pull/251692

• Codicon Font and Notebook Outputs: These pull requests update the codicon font file and introduce a feature for configuring transient outputs for notebooks. They provide more control over file sizes and output persistence through serializer options and user settings.
  • pull/251798, pull/251930

• Name Branding and Inline Completions: These pull requests address a typo related to name branding and involve a cleanup of the "provideInlineCompletions" feature. They include adding a missing function and fixing cycle detection.
  • pull/251566, pull/251598

• Chat Attachment and Elicitations Support: These pull requests transform the chatAttachmentResolve.js file into a service and add support for elicitations. They implement inline prompts in chat and ensure proper validation using quickpick for input.
  • pull/251632, pull/251872

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.

1. Create frst
   • Toxicity Score: 0.55 (Defensive responses,frustration,tense exchange)
   • This GitHub conversation involves username1 expressing dissatisfaction with username2's implementation, which did not meet expectations. Username2 responds defensively, leading to a tense exchange. Username3 attempts to mediate by suggesting alternative solutions, but the conversation remains strained. The tone is generally negative, with underlying frustration and defensiveness from 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
Copilot	209	40	0	20
meganrogge	146	17	19	75
bpasero	72	9	33	68
connor4312	57	6	1	51
Tyriar	28	5	11	59
aiday-mar	62	7	5	29
TylerLeonhardt	48	10	4	37
aeschli	44	8	0	15
jrieken	44	0	4	15
hediet	36	9	10	5