Weekly GitHub Report for Vscode: April 14, 2025 - April 21, 2025 (12:01:41)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
Released on March 12, 2025, this update for Visual Studio Code focuses on resolving issues identified in the February 2025 Recovery 2 milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
VS Code asks me to sign in to sync settings every 1-2 hours: This issue describes a bug in Visual Studio Code where users are repeatedly prompted to sign in to sync settings every 1-2 hours, despite having already signed in. The problem is occurring on version 1.99.2 of VS Code, primarily affecting users on Windows 11, and seems to have started after a recent update.
- Multiple users report experiencing the same issue on Windows 11, with some suggesting it began after the latest update. A potential link to a known authentication issue is discussed, and users are encouraged to enable trace logging to gather more information. Despite a recent update, the problem persists, and users are advised to be patient as developers work on a solution.
- Number of comments this week: 17
-
Screen readers HAS A BIG OLD BUG !!!!!!!!: This issue reports a performance problem in Visual Studio Code where using the multi-line comment function and then canceling the comment with the CTRL+/ key combination causes the program to freeze and crash without generating a crash report. The problem is described as being particularly disruptive for developers using VS Code, and the user requests an immediate fix.
- The comments discuss attempts to reproduce the issue, with requests for a GIF to illustrate the problem, but the initial link provided was broken. A new GIF was shared, but some users could not replicate the issue, suggesting it might be caused by an extension. The original poster tried disabling extensions without success, and further assistance was requested to identify the problem.
- Number of comments this week: 13
-
Implement different sorting logic for add context quick pick: This issue addresses the need to change the current alphabetical sorting logic for the "add context quick pick" feature in a GitHub project, proposing a new sorting method that prioritizes a "pinned list" of options followed by a "most recently used" sort to improve usability and discoverability. The issue also suggests a stretch goal of implementing an AI-powered recommendation system to further enhance the feature's functionality based on user activity and context.
- The comments discuss the confusion caused by the variety of icons and categories in the current system, with suggestions to categorize items into tools and attachments. There is a proposal to mimic the F1 > Run Task interface with recently used and pinned groups, and a discussion on the feasibility of pinning items. The conversation evolves with insights on implementation challenges, leading to a refined approach that organizes items by categories like Copilot and extensions, while addressing concerns about the length of the recent files list. The final comments express approval of the new design and inquire about the scope of the recently opened section.
- Number of comments this week: 10
-
error starting sse type mcp server: This issue reports a problem with starting an SSE type MCP server in Visual Studio Code's Insider version, where the user encounters an error message indicating "MPC -32601: Not found" after upgrading to a new version. The user also notes a potential typo in the error message and confirms that other server types like Docker and NPX are functioning correctly.
- The comments reveal a discussion about the error, with a request for detailed logs to diagnose the issue. The user provides server output logs, highlighting a change from a GET to a POST request in the newer version, which their server does not support. A clarification is provided that the change is intentional due to a protocol update, with a fallback mechanism in place. The user acknowledges the explanation and plans to update their server to handle POST requests, expressing gratitude for the support.
- Number of comments this week: 9
-
Content not recognized correctly while typing code: This issue involves a problem in Visual Studio Code where the content of a document is not recognized correctly while typing code, particularly in large projects using the AL language, leading to characters being unrecognized and causing the editor to slow down. The user reports that this problem persists even when all extensions, except the AL Language Extension, are disabled, and it requires frequent restarts of the editor to temporarily resolve the issue.
- The comments discuss potential causes and solutions, including the possibility of the issue being related to the AL Language Extension or hidden data from git blame history. Suggestions include reporting the bug to the AL Language Extension's GitHub, using the bisect tool to identify problematic extensions, and noting that the issue often occurs after copy-pasting operations.
- Number of comments this week: 8
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request for Visual Studio Code to support the generation of markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request highlights the need for an option to render markdown generated by code cells in the output, allowing for dynamic titles and content to be 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-windowdoes not function as expected, as it hijacks the existing window instead of opening a new one. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, resulting in the disconnection from the current server and replacement of the window with the new server's connection. ${userHome}in a task command creates bad paths: This issue 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 error occurs because the path is incorrectly formatted as\\c:\\Users\\myuser\\myfolder\\my.exe, whereas using${env:USERPROFILE}instead results in the correct path formatC:\\Users\\myuser\\myfolder\\my.exe.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where characters typed in a terminal window, when moved to a floating window during a remote connection, do not appear in real time if the main window is minimized. The characters only display once the main window is restored, suggesting a potential "sleep" state in the remote connection that prevents real-time updates.
- 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: 229
Summarized Issues:
- Visual Studio Code Bugs: Visual Studio Code has several recurring bugs affecting user experience. These include issues with focus shifting in dual-screen setups, syntax highlighting inconsistencies, and problems with extensions like Copilot forgetting context. Users have also reported issues with file selection, authentication prompts, and performance degradation due to new features.
- Copilot and Chat Issues: Users have reported various issues with GitHub Copilot and chat functionalities in Visual Studio Code. Problems include unresponsive chat interfaces, incorrect context retention, and chat prompts not functioning as expected. These issues disrupt the workflow and require further investigation to improve user experience.
- Accessibility and UI Concerns: Visual Studio Code faces several accessibility and user interface challenges. Issues include inadequate color contrast ratios, small target sizes for buttons, and confusing dialog language. These problems can hinder users with disabilities and require adjustments to meet accessibility standards.
- Performance and Compatibility Issues: Performance issues in Visual Studio Code have been reported, particularly with the integration of new AI features and compatibility with older systems. Users have experienced slowdowns, crashes, and compatibility problems with certain Linux distributions, affecting productivity.
- Feature Requests and Enhancements: There are numerous feature requests for Visual Studio Code, including better integration with mobile platforms, improved extension management, and enhanced user interface elements. These requests aim to expand the functionality and usability of the software for diverse user needs.
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: 207
Summarized Issues:
- Visual Studio Code Debugging Issues: This topic covers various issues related to debugging in Visual Studio Code, including problems with the "writeMemory" command not being sent to the lldb-dap extension, and debugging TypeScript extensions hanging indefinitely. These issues highlight challenges in debugging processes and the need for proper command execution and environment setup.
- Visual Studio Code UI and Accessibility Problems: Several issues address UI and accessibility challenges in Visual Studio Code, such as incorrect rendering of chat contexts, accessibility problems with combo boxes, and visual glitches in syntax highlighting. These issues emphasize the importance of consistent UI behavior and accessibility compliance for all users.
- Visual Studio Code Performance and Resource Management: Performance issues in Visual Studio Code are highlighted, including excessive CPU usage on MacOS, lag during file operations, and memory management problems. These issues point to the need for efficient resource management and performance optimization in the application.
- Visual Studio Code Extension and Feature Requests: Users have requested various features and improvements for Visual Studio Code, such as remote editing capabilities for FreeBSD, a larger pointer cursor area, and enhanced AI assistant performance. These requests reflect the community's desire for expanded functionality and improved user experience.
- Visual Studio Code Terminal and Command Issues: Issues related to terminal behavior and command execution in Visual Studio Code include problems with terminal focus, command variable resolution, and terminal display glitches. These issues highlight the need for reliable terminal functionality and command handling.
- Visual Studio Code Copilot and AI Integration: Several issues involve the integration of AI tools like Copilot in Visual Studio Code, including incorrect syntax generation, login problems, and feature requests for improved AI interaction. These issues underscore the challenges and potential of AI integration in development environments.
- Visual Studio Code Git and Source Control Issues: Problems with Git and source control in Visual Studio Code include incorrect file status display, syncing issues, and command execution errors. These issues highlight the importance of robust source control integration for effective version management.
- Visual Studio Code Configuration and Environment Issues: Configuration and environment-related issues in Visual Studio Code include problems with task execution, environment variable handling, and workspace settings. These issues emphasize the need for flexible and reliable configuration management.
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, Criticism of product, Potential for escalation.)
- This GitHub conversation involves multiple users discussing performance issues with a software product. The original poster expresses strong dissatisfaction with the product's performance, which has deteriorated with recent updates. Another user suggests a method to diagnose the problem, while a third user raises a related concern about resource usage. A fourth user comments on the harshness of the original criticism, suggesting a more moderate view. The original poster reiterates their dissatisfaction, indicating a willingness to provide further diagnostic information. The tone is generally frustrated, with some attempts at constructive feedback.
-
- Toxicity Score: 0.75 (Aggressive language, Frustration, Spam accusation)
- This GitHub conversation involves a user expressing intense frustration with frequent updates, using aggressive language, which triggers a response suggesting a solution and another comment labeling the post as spam.
-
your layout is fucking now I can'y fine file explorer ,
- Toxicity Score: 0.65 (Strong language, Dismissive response, Initial aggression.)
- This GitHub conversation involves a user expressing frustration with a software issue using strong language, which triggers a response from another user suggesting the use of a translation tool due to the unclear communication. The tone is initially aggressive and dismissive, but another participant offers a constructive suggestion to resolve the issue.
-
manipulation, lies, and security risk in a project with sensitive data from the so-called "AI"
- Toxicity Score: 0.55 (Frustration expressed, defensive responses, potential for misunderstanding.)
- This GitHub conversation involves multiple users discussing a performance issue related to a coding assistant. User1 expresses frustration over the assistant's actions, which they perceive as manipulative and misleading, particularly concerning security risks. User2 responds with a more neutral tone, suggesting that the issue might stem from a misunderstanding of the assistant's capabilities and emphasizes the user's responsibility in reviewing code. User3 acknowledges the concerns but maintains a constructive tone, suggesting improvements and clarifications. The conversation includes a mix of frustration, defensiveness, and constructive feedback, with some tension arising from differing perceptions of responsibility and expectations.
-
why the fuck is this here i didnt install co pilot
- Toxicity Score: 0.85 (Aggressive language, strong negative sentiment, lack of constructive dialogue.)
- This GitHub conversation involves a single user, who expresses intense frustration and anger towards the company responsible for the software, using aggressive and profane language. The tone is hostile and confrontational, with the user apologizing to any employee who might read the message but maintaining a strong negative sentiment throughout. The trigger of tension appears to be the unwanted installation of a feature or tool, which the user perceives as intrusive.
-
Remove Codepilot and suggestions
- Toxicity Score: 0.55 (Dismissive response, terse exchange, user frustration.)
- This GitHub conversation involves a user expressing annoyance about a feature, which is met with a dismissive response from another user, leading to a brief exchange of terse comments.
-
:warning: [ Security Issue ] - VSCode测试安全问题
- Toxicity Score: 0.70 (Aggressive language, Initial frustration, Potential for escalation.)
- This GitHub conversation involves a security issue reported in the Microsoft VSCode repository. The initial comment is brief and uses an aggressive tone, as indicated by the use of an expletive, which suggests frustration or anger. The conversation is likely to escalate if similar language continues to be used.
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: 29
Key Open Pull Requests
1. DRAFT: Allowing various font data in the editor: This pull request aims to enhance the editor by allowing the use of various font data, addressing issues such as cursor flickering, correct highlighting of selected words, proper rendering of multi-line selections and multi-cursors, alignment of cursor and character positions, and ensuring that font sizes are preserved across editors, while also discussing challenges related to the alignment of rendered whitespaces and IME text areas.
- URL: pull/246702
- 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, 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
2. ui element selection: This pull request introduces a feature that allows users to attach UI elements to chat within the Visual Studio Code environment, as detailed in the commits which include enhancements like a UI element selection window, background additions, and improvements to button functionality and event listening.
- URL: pull/246643
- Merged: No
3. Allow disabling built-in TS/JS extension in favor of tsgo: This pull request introduces a configuration option to disable the built-in TypeScript/JavaScript extension in Visual Studio Code, allowing users to easily switch between using the stable built-in extension and the experimental tsgo language server protocol (LSP) through a command in the typescript-go extension.
- URL: pull/246858
- Merged: No
Other Open Pull Requests
- TypeScript Language Features in VSCode: This topic involves reintroducing the expandable hover feature in the TypeScript language features for the VSCode extension. The pull request aligns with the latest TypeScript Server API updates that will be included in TypeScript 5.9.
- YAML Editing Enhancements: Enhancements to the YAML editing experience in Visual Studio Code are proposed by automatically triggering code completion within strings. This is achieved by adding
stringsto thequickSuggestionsunderconfigurationDefaults, addressing issue #239679.
- Browser Tests Reliability: The reliability and error handling of browser tests in the VSCode repository are improved by implementing unit tests for
browser/index.js. This includes improving test coverage, refining error messages, and ensuring tests adhere to the project's existing practices and conventions.
- LanguageModel API Updates: Updates to the LanguageModel API support prompt caching and thinking tokens by adding a new component called LanguageModelExtraDataPart. This change removes the LanguageModelChatMessage3 and bumps the API version to ensure compatibility with future extensions.
- Terminal Tooltip Behavior: Modifications to the terminal tab tooltip behavior in narrow viewports prevent it from covering the tabs. This is achieved by implementing
forcePosition: truein thevs/workbench/contrib/terminal/browser/terminalTabsList.tsfile, ensuring the tooltip is positioned to the left or right with a maximum width.
- File-Watching Mechanism: The file-watching mechanism in the VS Code repository is modified to respect the
.gitignorefile. This aims to reduce unnecessary file watching and git status triggers in large repositories, although it faces challenges with the glob pattern matching required to exclude specific paths.
- GitHub Extension Migration: The GitHub extension of the Visual Studio Code project is migrated to use ECMAScript Modules (ESM). This includes an additional commit to add a missing JavaScript file.
- ToolProgress API Introduction: A
toolProgressAPI is introduced to enable extensions to report progress using atoolInvocationToken. This enhances internal progress tracking by associating tool calls with their IDs and implements changes in the progress service to improve identifiability and state management.
- Configuration Behavior Change: A change to the configuration behavior in Visual Studio Code allows for input requests even in an empty workspace. The previous behavior of aborting early when a configuration was not found is deemed unnecessary, aiming to fix issue #245707.
- Screen Reader Content Display: Issue #225977 is addressed by ensuring that expanded content is not displayed when using screen readers (SR) in the Visual Studio Code project. This includes a commit with the message "Do not show expanded content when using SR."
- Chat Changes Rendering: A feature is implemented to render chat changes directly in the editor when a diff is available. This addresses issue #15856 in the vscode-copilot repository.
- Executable Detection Improvement: An issue in the Visual Studio Code project is addressed where the
extensionTipServicefails to detect certain executables. This is due to missing search locations like the homebrew directory on Mac and LOCALAPPDATA on Windows.
- Notebook Updates: Updates to notebooks within the Microsoft VSCode project are focused on, as indicated by the commit message. The absence of additional descriptive information in the body suggests a straightforward update.
- Notebook Edits Enhancement: The process of applying edits to notebooks is enhanced by utilizing a codemapper. This addresses issue #15567 in the vscode-copilot repository.
- Local Shell Resolution: The issue of resolving the local shell in a remote window within the terminal is addressed. This is referenced by issue #246181.
- JSX Transform Deemphasis: The old JSX transform in VSCode, which requires a React import, is deemphasized. The new automatic JSX transform that does not need a React import is promoted, aligning with the current default in React.
- GotoLineQuickAccess Feature: A feature is introduced to the
gotoLineQuickAccessfunctionality in Visual Studio Code. This allows users to move the cursor relative to its current position by entering a line number prefixed with a plus (+) or minus (-) sign.
- Task Input Handling: Issue #245665 is addressed by fixing a problem where tasks would exit prematurely when empty strings were entered into
promptStringinputs. The task now proceeds correctly through all inputs to theechocommand.
- Git Repository API Enhancement: The addition of a
getAnyConfigmethod to the gitRepositoryAPI is proposed. This enables extensions to access configuration settings across any scope to avoid confusion that arises when configurations are omitted due to scope-specific requests.
- Markdown Snippets Enhancement: An enhancement to the markdown-basics snippets in Visual Studio Code is proposed by modifying the behavior of the quote function. This ensures that all lines, including multiple paragraphs, are quoted, and adjusts the behavior when no text is selected.
- PHP Function Signatures Improvement: The improvement of PHP file function signatures is addressed by correcting parameter names and adding the functions
fdatasyn()andfsync(). This is part of resolving Issue #246963.
- README.md Update: The README.md file in the Microsoft VSCode repository is updated. It includes guidelines for contributors to ensure the pull request is associated with an existing issue and provides a description and testing details for the proposed changes.
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: 172
Key Closed Pull Requests
1. title: This pull request, titled "Create actions," involves a series of commits that include adding inline edit tests, fixing missing TypeScript scopes, reverting and reapplying engineering changes related to background codesign for Windows, implementing new features such as the run prompt command, and making various improvements and fixes across the codebase, including unit tests, chat prompt decoders, and markdown extensions, but ultimately was not merged into the main branch.
- URL: pull/246391
- Merged: No
- Associated Commits: 324d1, 1a602, 0bc67, 760b9, 39b68, 67524, 297f8, f0bb1, 75cea, 7a92a, 61e22, 3452c, ab9b3, 5b2b8, 4741f, 87111, 78c2b, fe3f4, 440da, 350e5, 721cf, 0160d, 4e151, 1450f, 11041, 574f9, 434c0, 968a8, 5f2ba, c6141, 0ab41, 63451, 32f9c, 8757e, d5487, 9d521, b2a09, 027e5, 8c60b, a32a3, 90034, 22d02, 02e46, c21a8, 2ad2a, f4a15, 6d74a, 769ab, f69cf, 96dea, 820a6, d0b11, 58c1e, c593e, 86489, fc836, a5431, 9125a, b0abf, 810f3, 8363e, 0d243, 4a18b, 00844, 8d1d5, dc88a, e1c53, 46c46, fd149, 0bd8e, 58d6d, ca5cb, a5501, 34d2b, 681fb, e9517, cee65, 7700c, e275f, 84c46, 599b9, b8965, 111ae, 032c7, d83e7, e87de, d2458, e8ab1, 4095b, f6b2d, fef48, cd3ae, 821b2, 63b5c, 1c1bd, b3a3f, 85492, d2a63, 77d9e, 472a7, c231d, 3d639, a9af8, 2b548, 0023c, 1fec1, 42f6f, 64126, bb2b0, d9156, 8ecef, 174af, 56ebf, 57dfc, 5df37, c6a20, 3a0b7, 75585, fa33e, 5d194, 3d39b, 6916a, e2afb, b952f, 2a049, 33c84, c9a61, 1afdf, e2947, 1e23a, 76ce3, 9d0bf, 88b8f, 0998f, 7021e, b4e68, 459f9, 613e2, 8e38e, 7dbf2, 40a7e, 060f2, 74ff8, 7ec68, b2060, d7523, b237e, 165c1, bb1d9, f074f, 65449, 807a4, 99732, 0c8f5, 3c7a7, 9c6b2, 91274, 66392, 2138f, d15f6, 4a0e9, ddede, 7ffe4, 91933, 71607, 76458, 933f9, 9ad84, 9143f, 41263, 25f25, f0ee5, 77a0b, 6c7a4, 41ecd, 0a94f, acf8d, ed478, 47932, 7b2ea, 0b0be, a19a7, 67562, e6348, 7aecf, c778b, 38c0e, 3a720, 6eddc, 8a1f5, 34c0c, 2fc67, 08ae9, 6a9a1, f2718, b17a4, 043f6, 49437, 36397, 0ab62, 18afe, 88c1f, f443e, bdc1a, 22141, a4a4b, a82ba, 385ab, 3ae3b, f093f, fd7fa, fe9ef, be37d, ae5d9, 07e01, 3f512, 1b1ed, febbc, 48cb4, 4293d, 816da, c3b0f, 522b9, f5bce, 0bb72, 296e7, 0440f, 84908, 03dc8, 88b8c, bb50f, 8e629, da19d, 8e86c, 05541, bf209, 63987, 0182d, c3806, f8308, 0ee4f, 609b6, 0a5f0, 11d22, 57008, d107c, 0f2f8, 550fe, 9cc0f, 92439
2. SCM - add secondary quick diff provider: This pull request introduces a secondary quick diff provider to the SCM (Source Control Management) feature in Visual Studio Code, addressing issue #60389, and includes various commits that implement the initial functionality, add a stagedQuickDiffProvider API, optimize the unstage command, deduplicate diffs, and refine UI elements such as colors and decorations.
- URL: pull/246707
- Merged: 2025-04-16T10:52:36Z
- Associated Commits: 56641, 014fa, f9e28, 24a20, eac2b, 67afc, b8c3f, 77695, b3f35, a342e, 5cffe, bfa66, a9eb9, ec7df, 96508, e27ec, 6bbf8, 39a24, c29c1, 90c43
3. [prompts]: run a saved prompt file: This pull request adds functionality to run previously saved prompt files with specified tools metadata in the Visual Studio Code project, addressing issues related to prompt actions registration, tools metadata collection, and unit testing improvements, as part of ongoing efforts to enhance the VSCode Copilot integration.
- URL: pull/246914
- Merged: 2025-04-18T21:39:31Z
- Associated Commits: 0452a, 1d73b, dc21f, 95c27, a5cba, fc000, 33a43, 8de0e, 3aa0e, 88b42, 74d82, 794c4, e37d5, f3514, 301b2, e70a9, f89e0
Other Closed Pull Requests
- Shell Environment API Refinement: This topic involves refining the shell environment API by scoping down the environment reporting for various shells such as zsh, bash, fish, and pwsh. The pull requests address issues #245695 and #244140 in the Visual Studio Code repository, ensuring consistent and reliable shell integration for zsh users, particularly on macOS.
- Front Matter Header Parsing: This topic covers the addition of logic to parse the contents of the Front Matter header in the Visual Studio Code project. The pull requests address issues related to quote and double quote token parsing, and include related unit tests and documentation improvements.
- Chat Feature Enhancements: This topic includes enhancements to the chat feature in the Visual Studio Code project, such as adding a "save to prompt" action for chat history and preparing for a new usage-based quota system. The pull requests also involve changing the URL to enable additional use and making minor adjustments to the wording related to chat quotas.
- Prompt and Instructions File Separation: This topic involves separating prompt and instructions files in the Microsoft VSCode project. The pull requests include multiple commits addressing updates to various components and files, with contributions from Oleg Solomko.
- Telemetry Tracing in TypeScript Extension: This topic covers the addition of telemetry tracing capabilities to the TypeScript extension in the Visual Studio Code project. The pull requests include adding telemetry trace support, fixing and improving event names, and ensuring GDPR compliance.
- Tools Metadata in Prompt Headers: This topic involves the introduction of logic to parse a list of
toolswithin a prompt header and adding diagnostics support for the 'tools' metadata. The pull requests address issues linked to the GitHub project for VSCode Copilot and include several commits that enhance thePromptHeaderclass and improve unit tests.
- Code Sign Script Refactoring: This topic involves refactoring the codesign scripts in the Microsoft VSCode project. The pull requests include consolidating the scripts, experimenting with a script task, reverting to an old syntax, and updating a dependency named "deemon."
- Internal Edit File Tool Cleanup: This topic focuses on cleaning up the internal edit file tool by ensuring it properly takes a URI from the extension and moving more functionality back to the extension. The pull requests address issue microsoft/vscode-copilot#15348.
- Electron Framework Update: This topic involves updating the Electron framework to version 34.5.1 in the Microsoft VSCode project. The pull requests address issues #242726, #224743, and #243957, and include additional updates to the Node.js build and distribution files.
- Node.js Compile Cache Adoption: This topic involves adopting a compile cache for the Node.js environment within the Visual Studio Code project. The pull requests include adjustments for utility processes and various tweaks, and were successfully merged on April 17, 2025.
- Prompt Attachments Event Improvements: This topic improves the events related to prompt attachments to enhance the chat widget render sequencing. The pull requests address issues linked to three specific GitHub issues in the vscode-copilot project.
- Git Extension Semantic Clarification: This topic addresses semantic inconsistencies in the Git extension of the VSCode project. The pull requests clarify the interpretation of the
DELETED_BY_THEMstatus as a conflict rather than a normal operation, eliminating ambiguity in static methods.
- RunCommand Function Corrections: This topic addresses a typo and corrects a type mismatch in the implementation of the
runCommandfunction within the Visual Studio Code project. The pull requests were successfully merged on April 14, 2025.
- Dependency Version Bumps: This topic aims to update the dependencies by bumping the versions of the "tokio" and "crossbeam-channel" libraries in the Microsoft VSCode project. The pull requests are indicated by the commit messages and the pull request title.
- Ask Mode Query Handling: This topic addresses the issue of ensuring that when an extension sends a query to a participant in the Visual Studio Code environment, it automatically switches to "Ask mode." The pull requests implement this behavior specifically in agent mode.
- Notification Component Memory Leak Fixes: This topic addresses memory leaks in the notifications component of the Visual Studio Code project. The pull requests include fixes for the leaks and ensure that the associated tests are corrected, with the changes successfully merged on April 14, 2025.
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.
- PR for testing #246822
- Toxicity Score: 0.55 (Defensive responses, unresolved issues, skepticism.)
- This GitHub conversation involves username1 expressing dissatisfaction with username2's implementation, which did not resolve the issue as expected. Username2 responds defensively, leading to a tense exchange. Username3 attempts to mediate by suggesting alternative approaches, but username1 remains skeptical. The tone shifts from collaborative to confrontational, with underlying frustration evident in the responses.
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 | 195 | 30 | 42 | 69 |
| roblourens | 161 | 13 | 21 | 104 |
| lszomoru | 248 | 11 | 7 | 31 |
| legomushroom | 251 | 9 | 3 | 13 |
| connor4312 | 86 | 13 | 23 | 98 |
| meganrogge | 82 | 8 | 25 | 84 |
| jrieken | 111 | 23 | 15 | 46 |
| i-stefan-1994 | 0 | 0 | 131 | 0 |
| albertosantini | 0 | 0 | 0 | 114 |
| TylerLeonhardt | 18 | 1 | 12 | 81 |