Weekly GitHub Report for Vscode: October 20, 2025 - October 27, 2025 (12:00:42)
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:
The version released on March 12, 2025, primarily focuses on resolving various issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." For a comprehensive overview of all updates and improvements, users are directed to the official release notes on the Visual Studio Code 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.
-
Conversation History Summarization.: This issue reports a critical bug where the conversation history summarization feature in the GitHub Copilot extension frequently loses context, causing unreasonable and disruptive coding suggestions during active development. The user expresses significant frustration over wasted time, premium request usage, and the inability to disable or override this summarization behavior, which severely impacts productivity.
- The comments reveal multiple users eager to work on the issue and request assignment, while others share their own frustrations and attempts to find solutions, including rolling back versions. There is a strong demand for a fix or an option to disable the summarization, with users emphasizing the negative impact on workflow and the lack of timely responses from maintainers.
- Number of comments this week: 18
-
latest inside SCM only shows one repo: This issue reports a bug where the Source Control Management (SCM) view in VS Code only shows one repository instead of all multiple repositories in a workspace after a recent update. The user finds the new behavior inconvenient because they have to manually toggle and select repositories, which adds extra work and clicks compared to the previous automatic display of all repos.
- The comments discuss that the change is related to a new default setting that limits SCM to a single repository to simplify the interface, but users with many repos find this cumbersome. Suggestions include toggling the
scm.repositories.selectionModeto multiple and using Shift+Click to select repos, though this is seen as a poor user experience. Some users request an easier way to switch modes or revert the change, while maintainers explain the motivation behind the update and encourage further feedback. - Number of comments this week: 13
- The comments discuss that the change is related to a new default setting that limits SCM to a single repository to simplify the interface, but users with many repos find this cumbersome. Suggestions include toggling the
-
Stuck "Retrieving Notebook summary": This issue describes a bug where the GitHub Copilot extension in agent mode frequently gets stuck on the "Retrieving Notebook summary" step when interacting with Jupyter notebooks in Python, affecting multiple language models including Claude Sonnet 4 and GPT-5. Users report that the problem persists across different environments and VS Code versions, with some temporary workarounds like reloading the window or copying the notebook, but no permanent fix has been identified yet.
- Multiple users confirm experiencing the same issue with consistent repro steps and detailed logs showing errors related to invalid cell IDs and forbidden kernel fetches; suggestions include enabling verbose logging and temporary workarounds such as reloading or duplicating notebooks, but the root cause remains unresolved and the problem affects various models and setups.
- Number of comments this week: 12
-
Unreliable middle-mouse-button paste in integrated terminal on Linux: This issue reports that the middle-mouse-button paste functionality in the integrated terminal on Linux is unreliable, often failing to paste the primary selection when clicked. The problem appears consistently across multiple VSCode versions and Linux desktop environments, with indications that it may be related to the terminal’s handling of mouse events, particularly when the cursor is over non-blank characters or clickable text regions.
- The discussion explores whether this is a regression by bisecting VSCode versions, identifying the bug’s introduction between versions 1.67.2 and 1.68.0, and considers the role of the terminal’s clickable link feature as a possible cause. Participants share code references, test results on various versions, and suggest disabling features or testing underlying components, but no definitive fix or workaround is confirmed yet.
- Number of comments this week: 10
-
Copilot gets unable to get issuer certificate on model metadata fetch: This issue describes a bug where GitHub Copilot in VS Code Insiders, when used with Remote-SSH into a Mac, repeatedly fails to fetch model metadata due to an "unable to get issuer certificate" TLS error. The problem does not occur in stable VS Code or when not using Remote-SSH, and attempts to debug show successful network pings but failed fetch requests caused by certificate validation issues, with users investigating system certificate loading and network configurations to identify the root cause.
- The comments include detailed diagnostic outputs showing successful curl requests to the API but failing fetch calls within the extension due to TLS certificate errors. Users share environment details, run diagnostic commands, compare behavior between stable and insiders versions, and check system certificate counts, with suggestions to enable debug logging and verify proxy and certificate configurations to help isolate the issue.
- 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.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request asking for the ability to display markdown generated by code cells in the notebook outline, similar to how JupyterLab handles dynamic titles produced by code outputs. The requester highlights that this functionality would allow outlines to include dynamically generated content from code cells, enhancing navigation and organization within the notebook environment.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue reports a bug in Visual Studio Code where using a vscode:// link with the query parameters ?new-window or ?reuse-window does not behave as expected when opening remote SSH connections. Instead of opening a new window or reusing the existing one, the current remote connection is disconnected and replaced by the new connection, causing loss of the original session.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set toprocess, causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}produces malformed paths like/c:/Users/myuser/myfolder/my.exe, using${env:USERPROFILE}correctly resolves to a valid Windows path, indicating an inconsistency in how these variables are expanded depending on the task type and shell environment.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where the terminal in a floating window does not echo typed characters in real time when connected to a remote environment, such as WSL or SSH, and the main VS Code window is minimized. The characters only appear after restoring the main window, indicating a delay in terminal updates likely caused by the remote connection entering a sleep state when the main window is minimized.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is pasted into Visual Studio Code, it is incorrectly rendered as a question mark instead of displaying the correct symbol. The problem does not occur in web browsers like Firefox, indicating a rendering or font support issue specific to VS Code on Fedora 39 with version 1.87.2.
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: 507
Summarized Issues:
- Extension Signature Verification Failures: Several issues report that extension signature verification fails for specific extensions like "XML Tools" and PowerShell on various platforms, causing trust and security concerns. These failures prevent proper extension validation and may hinder extension usage or updates.
- GitHub Copilot and Chat Functionality Problems: Multiple issues describe Copilot and Copilot Chat extensions failing to respond, freezing, or not showing expected UI elements such as chat icons or commands. Users experience persistent network errors, unresponsiveness, and failures in chat initialization or model loading, severely impacting productivity.
- issues/272176, issues/272179, issues/272198, issues/272205, issues/272243, issues/272269, issues/272271, issues/272311, issues/272325, issues/272328, issues/272336, issues/272338, issues/272342, issues/272354, issues/272409, issues/272448, issues/272506, issues/272507, issues/272551, issues/272668, issues/272669, issues/272713, issues/272714, issues/272742, issues/272745, issues/272810, issues/272811, issues/272842, issues/272844, issues/272845, issues/272850, issues/272861, issues/272897, issues/272901, issues/273000, issues/273001, issues/273028, issues/273030, issues/273056, issues/273069, issues/273080, issues/273127, issues/273250
- Extension Unresponsiveness and Performance Issues: Numerous reports indicate that the VS Code extension or the editor itself becomes unresponsive, freezes, or suffers from severe performance degradation on various platforms and configurations. These issues include long hangs, excessive memory consumption, and slow or stuck responses, disrupting user workflows.
- Agent Mode and AI Model Behavior Issues: Several issues describe problems with agent mode, including freezing after edits, switching AI models unexpectedly, ignoring prompts, or producing hallucinations and incorrect code. These problems cause workflow interruptions and token wastage.
- Network and Connectivity Errors: Users report persistent network errors such as connection resets, HTTP2 protocol errors, and name resolution failures affecting GitHub Copilot and Git operations, often despite stable network conditions, suggesting firewall or configuration issues.
- File and Workspace Management Bugs: Multiple issues describe problems with file handling such as lost or deleted files, inability to reopen chat histories, corrupted files due to replacement commands, and workspace settings not applying correctly. These bugs cause data loss and workflow disruption.
- UI and UX Inconsistencies and Requests: Several issues highlight UI problems such as inconsistent icon sizes, confusing or missing indicators, misplaced hover effects, and requests for new features like tab menus, better keybinding dialogs, and improved chat input behavior. These affect usability and user satisfaction.
- Terminal and Shell Integration Issues: Users report problems with terminal behavior including search overwriting clipboard, terminal freezing, command execution hanging, and shell integration not being detected or functioning properly, impacting development workflows.
- Code Completion and Suggestion Problems: Several issues describe bugs where code completions are incorrect, duplicated, or not accepted properly, including problems with inline completions, tab key behavior, and suggestions ignoring user prompts, leading to frustration and inefficiency.
- Settings and Configuration Requests: Users request new settings such as disabling auto-opening files on drag, controlling model visibility, adding spell checkers, and improving commit message generation, aiming to enhance customization and workflow efficiency.
- Agent and Tool Integration Bugs: Issues report problems with MCP server registration, tool visibility, input variable prompting, and tool call formatting, causing inconsistent behavior and errors in agent workflows.
- Accessibility and Screen Reader Issues: Some reports highlight incomplete or incorrect screen reader announcements and aria-label problems in chat and other UI components, affecting users relying on assistive technologies.
- Crash and Stability Problems: Several issues describe crashes of VS Code or extensions, including native crashes on Windows, extension host crashes, and JavaScript heap out of memory errors, leading to loss of work and instability.
- issues/272272, issues/272868, issues/273004, issues/273318, [issues/273174](https://github.com/issues/273174]
- Feature Requests for Enhanced Developer Experience: Users request features such as multi-chat session referencing, commit message improvements, parallel call stacks, and native MATLAB/Simulink integration to improve productivity and workflow.
- Miscellaneous Bugs and Requests: Various other issues include problems with color pickers, scrolling lag, menu bar behavior, and extension installation failures, reflecting a broad range of user-reported problems.
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: 257
Summarized Issues:
- Terminal and Integrated Shell Issues: Multiple issues report problems with terminal behavior in VS Code, including terminals freezing or becoming unresponsive after running commands, incorrect terminal profile usage (PowerShell used despite CMD setting), laggy or duplicated terminal content, and failures in running or focusing terminals properly. These bugs affect various platforms and VS Code versions, causing workflow interruptions and user frustration.
- GitHub Copilot and Copilot Chat Functionality and Bugs: Numerous issues describe bugs and feature requests related to GitHub Copilot and its Chat extension, including failures to respect user settings (e.g., terminal profile), inability to log out or switch accounts, persistent error messages despite paid subscriptions, rate limiting despite available credits, model selection not persisting, and requests failing with various error codes (400, 408, 413). These problems cause degraded user experience, lost productivity, and confusion about subscription status.
- issues/272139, issues/272165, issues/272199, issues/272222, issues/272223, issues/272326, issues/272344, issues/272357, issues/272426, issues/272434, issues/272436, issues/272652, issues/272722, issues/272726, issues/272727, issues/272746, issues/272952, issues/273051, issues/273077, issues/273130, issues/273122, issues/273288, issues/273261, issues/273272
- Performance and Responsiveness Problems: Several reports highlight severe performance degradation in VS Code and its extensions, including extremely slow responsiveness (up to 30 minutes for simple changes), laggy code completion, slow notebook summary retrieval, and long hangs during conversation summarization or code execution. These issues affect productivity and usability across platforms and versions.
- Request Failures and JSON Format Errors: Multiple issues report requests failing with 400 errors due to invalid JSON format in tool call arguments or other malformed requests, affecting various VS Code extension versions and platforms. These errors cause features to stop working and require fixes in request formatting or validation.
- Network and Connectivity Errors: Several issues describe network-related errors such as SSL alerts, connection closures, and network changes causing failures in VS Code extensions, often linked to firewall or network configuration problems. These errors disrupt normal extension operation and require network troubleshooting.
- Agent Mode and Chat Handoff Issues: Multiple reports indicate problems with agent mode in Copilot Chat, including agents getting stuck waiting for terminal responses, failure to persist selected custom agents during handoffs, and chat modes not switching correctly. These bugs hinder smooth multi-step workflows and agent interactions.
- Extension and Feature Request Templates and Incomplete Reports: Several issues are incomplete bug report templates or lack sufficient detail, making it difficult to diagnose or address the problems. These include generic templates for Copilot Chat and VS Code, as well as blank or placeholder submissions.
- issues/272192, issues/272216, issues/272225, issues/272283, issues/272650, issues/272659, issues/272660, issues/273234, issues/273242, issues/273293, issues/273308, [issues/273309](https://github.com/issues/273309]
- UI and UX Inconsistencies and Improvements: Various issues address UI problems such as duplicated menu actions, confusing button labels, misaligned text, missing icons, and requests for features like multi-line tabs, keyboard navigation for search history, and better sorting in tool pickers. These affect user experience and interface clarity.
- Debugging and Development Environment Issues: Several issues report problems with debugging extensions, breakpoints not binding correctly, remote development features failing due to unsupported VS Code versions, and extensions not functioning properly in certain environments. These hinder development workflows.
- Security, Privacy, and Ethical Concerns: Some issues raise concerns about security risks due to Copilot's use of cmd shell on Windows, accidental sending of sensitive files to AI providers, and the need for respectful and ethical conduct within the project. These highlight important considerations beyond technical bugs.
- Miscellaneous Bugs and Feature Requests: Other issues cover a wide range of topics including JSON multiline string support rejection, bug reports about specific language support (e.g., SCSS attr() highlighting), requests for new icons, and problems with extension marketplace behavior.
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.
-
replace string command horribly broken
- Toxicity Score: 0.75 (Rapid escalation, aggressive language)
- This GitHub conversation involves a user expressing strong frustration and urgency regarding a malfunction, using aggressive language to demand a fix, while no other participants have yet responded, creating a tense and confrontational tone.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, refusal to cooperate)
- This GitHub conversation involves a user expressing strong frustration and refusal to engage further, directed at another party's automated tool and the resulting workload. The tone is confrontational and dismissive, with clear tension triggered by perceived unfair responsibility and excessive demands. The interaction is brief but marked by aggressive language and a defensive stance.
-
Conversation History Summarization.
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, repeated demands, profanity, unresolved frustration)
- This GitHub conversation involves multiple users expressing increasing frustration and urgency regarding a recurring issue, with initial polite requests for assistance escalating into aggressive and exasperated language. The tone shifts from cooperative and inquisitive to highly agitated and confrontational, triggered by perceived lack of response and ongoing problems causing significant disruption. The conversation shows signs of tension due to unresolved issues and dissatisfaction with the support process.
-
if cant make anything this software is junk
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, threats, repeated accusations)
- This GitHub conversation begins with a user posting a bug report expressing frustration about software limitations. Subsequent comments by various users quickly devolve into accusations and hostile language, with sentiments shifting from disappointment to anger and distrust. The tone becomes increasingly aggressive and confrontational, triggered by perceived failures and dissatisfaction with the software and its management. This escalation is marked by repeated use of inflammatory language and threats, indicating a breakdown in constructive dialogue.
-
Scammer -- don't close ticket respond
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a single user expressing strong frustration and distrust towards the service, using accusatory and emotionally charged language to highlight perceived inconsistencies and dissatisfaction with the product's performance. The tone is confrontational and urgent, with the user feeling financially wronged and demanding accountability. There is no response from other participants, so the conversation remains one-sided and unresolved.
-
response contained no choice i will never pay again
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, one-sided negativity)
- This GitHub conversation involves a single user expressing frustration and dissatisfaction with a software feature, using strong language and negative sentiment. The tone is confrontational and dismissive, with no responses or engagement from other users, indicating a one-sided expression of discontent. The tension is triggered by perceived failures or limitations of the software, leading to a harsh critique without constructive dialogue.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, threat of legal action)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger towards a software feature, using aggressive and threatening language without any responses or further interaction.
-
The inline command not working when press enter or click
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration using explicit language, without any subsequent replies or interactions. The tone is highly negative and aggressive, triggered by the user's dissatisfaction with a technical issue. No other participants or sentiments are present to moderate or escalate the discussion.
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: 74
Key Open Pull Requests
1. add terminal output dropdown, reveal command on focus : This pull request introduces a terminal output dropdown feature and reveals the executed command when the terminal output is focused, addressing issues #271387 and #271388 in the VSCode project.
- URL: pull/273175
- Merged: No
- Associated Commits: 30c3b, 7c335, b5e7b, 27a39, 919b8, 44580, 01a94, 82dca, cc4ad, e5a1f, e7894, 581da, 45fea, d0f7d, fe1e0, 0652e, 28d44, cc79a, 7aa74, d95cd, 3c752, 44fcf, 1756c, 02684, e35e8, 9e040, 4d24d, e2e84, d3eba, 3990a, ec552, c892a, d5c0c, fdad4, b4673
2. Add build folder tests to CI: This pull request adds the previously excluded tests from the build folder to the continuous integration node test suite to ensure they are run as part of the unit testing process.
- URL: pull/272564
- Merged: No
- Associated Commits: 50bfc, 1bc9a, 658a3, 24d2e, 32e7d, f76c0, e7cd2, d70db, b6fda, efbac, ddbea, 0f7cf, 5efc4, 53ebc, d7aab, 87c39, d6f32, 796d4
3. feat(monaco): Add option to remove Paste option from editor context menu: This pull request introduces a feature to the Monaco editor that allows users to remove the Paste option from the editor's context menu, addressing an issue where the built-in Paste command does not work properly in modern browsers by enabling the use of a custom Paste implementation without breaking existing APIs or workflows.
- URL: pull/272265
- Merged: No
- Associated Commits: 5d02a, 1b274, 4491d, a6b6c, 73fc8, 4c0c5, 9f0cd, 5a226, 7fc46, 4671a, 21cff, f828c, 323ac, 04c07, 88b96, d31fb, 84343
Other Open Pull Requests
- Explorer Files List View: This pull request implements a new "Files List" view in the VS Code Explorer sidebar that displays workspace files in a hierarchical tree structure with file type icons, asynchronous loading, accessibility support, theming integration, and user-configurable options. It enhances file browsing and visualization within the editor.
- Git and Branch Commit Information: This pull request implements a feature to display the latest commit message details—including author, hash, subject, and relative commit time—for branches directly within the terminal suggest widget in VS Code. It enhances git branch completions with contextual commit information and includes comprehensive unit tests and code refactoring for maintainability.
- Agent and Chat UI Improvements: Multiple pull requests improve the chat and agent experience by enabling find functionality with fuzzy word matching across agent sessions, updating inline chat placeholder text to reflect current chat mode descriptions, and renaming user-facing references from "Agent" to "Plan" to fix accessibility issues with screen readers. These changes enhance usability and accessibility in the chat interface.
- Sticky Scroll Enhancements: This pull request introduces a new
scopePreferencesetting with options forinnerScopeandouterScopeto enhance the sticky scroll feature in the editor. It modifies thestickyScrollControllerto support inner scopes and improve behavior with deeply nested code structures.
- Terminal and Shell Integration Fixes: These pull requests revert a previous hack related to terminal configuration policies and propose replacing backtick wrapping of the Shell Integration's prompt input with a pre element to improve rendering, including enabling HTML rendering in the terminal tooltip to fix command input wrapping. The latter is currently a draft pending testing.
- URI Identity Service Performance: This pull request improves the performance of the UriIdentityService by migrating to string keys and native Map for caching to reduce URI object creation and conversion. It also enhances the cache cleanup algorithm using a quickSelect method instead of full sorting, resulting in significant speedups in URI insertion, reading, and cache trimming operations.
- Exception Widget Behavior: This pull request aims to display the exception widget in inactive editors without shifting their current focus range. It addresses issues from a previous pull request to ensure consistent exception visibility across all editors for the same file while only scrolling the active editor.
- Multi-file Diff Navigation: This pull request enables next and previous navigation functionality in the multi-file diff editor of VS Code. It allows users to seamlessly navigate through changes by automatically scrolling to and expanding files as needed to make changes visible.
- SCM History View UI Update: This pull request enhances the SCM history view in Visual Studio Code by increasing the codicon font size to 16px and reducing the padding to 1px. These changes improve the visibility and overall user experience of the interface.
- Policy Localization ESLint Rule: This pull request introduces a new ESLint rule aimed at enforcing policy localization best practices. It acknowledges that the linting is best-effort and can be bypassed by using variables.
- Delegate to Agent Feature: This pull request implements a comprehensive, agent-agnostic "Delegate to Agent" feature in VS Code core that detects TODO comments across multiple languages and allows users to delegate these TODOs to any available chat agent via integrated code actions and CodeLens UI. It provides context-rich prompts and configurable settings to streamline developer workflow from planning to AI-assisted implementation.
- Dotenv Language Support: This pull request adds basic language support for the dotenv language in Visual Studio Code, including syntax highlighting and a language configuration file for
.envfiles and related filenames. It integrates grammar from the dotenv-vscode repository and resolves conflicts with ini and shellscript languages.
- Chat List Item Height Fix: This pull request addresses issue #265031 by updating the chat list item height dynamically when the row container resizes. It implements a shared ResizeObserver with a WeakMap to efficiently manage row container elements and ensure proper garbage collection.
- Tool Reference Parsing Update: This pull request introduces a requirement for the '#tool:' prefix when referencing tools in prompt, instruction, and agent files, along with stricter parsing rules and related fixes. These changes improve matching accuracy and semantic token support.
- MCP Resource Directory Support: This pull request adds directory support for MCP resources in the Visual Studio Code project, enhancing the resource picker functionality as part of fixing issue #262368.
- RunInTerminalTool Focus Fix: This pull request fixes the RunInTerminalTool to prevent the VS Code integrated terminal from automatically revealing and stealing focus when it is closed and the user is working with external CLI terminals. It adds a visibility check that only reveals the terminal if it is already open, improving user experience without breaking existing behavior.
- TextDecoder BOM Preservation: This pull request addresses an issue where the default TextDecoder used in VSBuffer.toString() strips the BOM character during message deserialization. It sets TextDecoder.ignoreBOM to true, preserving the BOM and fixing the related bug described in issue #251527.
- Word Selection Fix for Punctuation: This pull request fixes the issue where double-clicking on punctuation characters incorrectly selects adjacent whitespace instead of the punctuation itself. It updates the word selection logic to explicitly handle punctuation as a separate word type, ensuring correct selection behavior while preserving existing drag selection functionality.
- Create Fork Default Branch Option: This pull request introduces a feature for the "create fork" option that allows users to fork only the default branch of a repository when publishing a branch to a repo they don't have permission to. It provides a popup prompt with this choice and integrates it seamlessly into the existing
octokitpackage.
- Window Management Enhancements: This pull request introduces a new
ShowAllWindowsActionin VS Code that enables users to view, manage, and quickly switch between all open windows—including main and auxiliary ones—via a command accessible from the Command Palette. It features window icons, active window indication, close buttons for non-active windows, unsaved change markers, and grouping of auxiliary windows with their parents, implemented by extending existing window management infrastructure.
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: 272
Key Closed Pull Requests
1. Add support for linux policies via JSON file: This pull request proposes adding support for Linux policies through a JSON file, enabling the project to handle Linux-specific policy configurations.
- URL: pull/272339
- Merged: No
- Associated Commits: 65d6e, 76c33, fe388, 0a156, c8f61, b6d99, f4357, cdbfb, f54c9, 7eb00, e6935, 8e72c, bfba6, 5f13f, adaf8, 60686, 9334e, 2db66, 19b5f, e1e18, ba86b, 1f4b2, 15589, 6e218, c6277, 78fb8, c5b94, bb09b, e0f4b, f7d91, f1d3d, 48c93, a676d, 1bcb2, 5b439, a95d6, 40f44, 7e2db, 7a86b, 56951, 7fccf, c397e, 42943, 4659a, 2c8dc, c3d58, ca2f9, 02ebb, b63cd, d4c39, e4db2, cc184, 806b0, 69d1c, c2c62, ef3f1, d568d, 795c8, ec115, 2eec8, 3925c, 49632, 67961, 58553, 63ef4, 7a90c, f77f4, afeca, b4621, 90124, adcc3, 87d1f, dd3d0, 79d54, 5aac6, e15e1, b42b3, f9304, ce8f9, 1e95f, 900c0, ecb6b, 3e730, 9d45e, ab73e, 8fffc, 025f4, bbaef, 9d482, 9db33, 98db5, 53983, 98651, 705c8, 04da0, 99c29, e975e
2. Use unified timeout setting under shell integration in runCommand : This pull request unifies the timeout setting for shell integration under the terminal.integrated.shellIntegration configuration in VS Code's runCommand function, optimizing the timeout application by considering the terminal process's ready time to avoid unnecessary waiting.
- URL: pull/272369
- Merged: Yes
- Associated Commits: 9559f, 32a00, a937b, 30898, 15139, 33209, 81011, dcded, cf429, d4cbe, cd335, 1f12e, 7c4b2, 21d50, 80711, e46d7, 3002e, 06b0b, ec365, 262be, 55d3e, 7c1ac, adb0e, 2925d, 76b69, 980c4, f87c0, e04bb, f9286
3. Use tree sitter for parsing terminal auto approve sub-commands: This pull request integrates the tree-sitter parsing library to improve the parsing of terminal auto-approve sub-commands in the VSCode project, addressing issue #261794 by enhancing command parsing accuracy, adding asynchronous APIs, supporting PowerShell, and refining auto-approval logic.
- URL: pull/272281
- Merged: Yes
- Associated Commits: 5f4c6, 5bb3b, ca9fc, f11c1, d9fe5, 9013d, f4eda, 93336, cfc2e, e5f42, f35c9, 2fe79, 82758, 258d0, 6ae9c, e1f2a, 46235, 6f54e, dafe2, 30f6d, cbd17, 9cdad
Other Closed Pull Requests
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 | 301 | 59 | 0 | 474 |
| meganrogge | 236 | 9 | 28 | 166 |
| Tyriar | 134 | 31 | 61 | 197 |
| bpasero | 184 | 32 | 68 | 115 |
| mjbvz | 133 | 24 | 25 | 83 |
| dmitrivMS | 163 | 19 | 3 | 55 |
| connor4312 | 52 | 8 | 16 | 162 |
| roblourens | 48 | 10 | 33 | 121 |
| pwang347 | 154 | 15 | 0 | 22 |
| TylerLeonhardt | 44 | 7 | 19 | 102 |