Weekly GitHub Report for Vscode: March 03, 2025 - March 10, 2025
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.97.2
1.2 Version Information:
Released on February 12, 2025, this version of Visual Studio Code focuses on resolving issues identified in the "January 2025 Recovery 2" milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Opening Extremely Long URLs Causes Notification Popup to Overflow the Display: This issue describes a problem in Visual Studio Code where attempting to open an extremely long URL from the terminal using "Ctrl + Click" causes the notification popup to overflow the display, making it impossible for the user to interact with the popup. As a result, users are unable to confirm or cancel the action to open the external website, leaving them with no option but to shut down VS Code completely to resolve the situation.
- Relative clickable links rendered in the document don't work on Windows: This issue addresses a bug where relative clickable links rendered in documentation comments do not function correctly on Windows, despite working on MacOS. The problem specifically involves plain links in comments, such as those pointing to local files, and there is uncertainty about whether this is a regression or a longstanding issue.
- VSCode restarting devices periodically: This issue reports a bug in Visual Studio Code where the user's peripheral devices, such as the mouse, speakers, and keyboard, intermittently freeze and restart, accompanied by the Windows "plug in" sound. The problem has persisted for over a year, affecting the user's workflow on a system running Windows 10 with specific hardware and software configurations, including various extensions and system settings.
- Show Comments in TextMate Scope Inspector: This issue is about a feature request to enhance Visual Studio Code by displaying comments from TextMate grammar files within the TextMate scope inspector. The current limitation is that these comments are only present in the TextMate files and do not provide external assistance, so the proposal suggests using them to offer basic documentation for TextMate scopes in the editor.
- Inspect Context Keys Should Open JSON File instead of logging to dev console: This issue addresses a feature request for the VS Code project, suggesting that the "Inspect Context Keys" functionality should open a JSON file within the editor instead of logging information to the developer console. The proposed change aims to enhance user experience by allowing users to search within the object directly in VS Code, providing a more efficient and user-friendly interface.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
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: 118
Summarized Issues:
- Login and Authentication Issues: Users are experiencing login and authentication problems in Visual Studio Code, particularly with Azure accounts and sync settings. These issues often involve login loops or failed authentication processes, potentially due to misconfigurations or multiple accounts.
- Extension and Feature Requests: There are multiple requests for new features in Visual Studio Code, such as creating shortcuts for different profiles, exporting and importing extensions, and syncing workspace settings. These requests aim to improve user workflow and ease of use across different devices and environments.
- Performance and Stability Issues: Users report various performance problems, including crashes, freezes, and memory leaks in Visual Studio Code. These issues often disrupt workflow and require troubleshooting to identify the root cause, such as specific extensions or system configurations.
- Bug Reports in Recent Updates: Several bugs have been reported in recent updates of Visual Studio Code, affecting functionalities like text input, terminal operations, and extension compatibility. These bugs often require users to find workarounds or wait for patches in future updates.
- Git and Source Control Issues: Users encounter problems with Git integration in Visual Studio Code, such as unexpected prompts and issues with repository management. These issues can hinder version control processes and require adjustments in settings or workflows.
- Terminal and Shell Integration Problems: There are issues related to terminal and shell integration in Visual Studio Code, including problems with command suggestions and shell-specific features. These issues can affect productivity and require users to adjust their terminal configurations.
- Debugging and Execution Errors: Users report errors and unexpected behavior during debugging sessions in Visual Studio Code, such as missing breakpoints and execution failures. These issues often require detailed investigation and may involve specific language or platform configurations.
- User Interface and Accessibility Concerns: There are concerns about the user interface and accessibility features in Visual Studio Code, such as keyboard focus issues and theme inconsistencies. These issues can impact user experience, particularly for those relying on accessibility tools.
- File and Path Management Issues: Users experience problems with file and path management in Visual Studio Code, including incorrect path completions and file state reversions. These issues can lead to confusion and require careful management of file operations and settings.
- Extension Management Problems: There are issues with managing extensions in Visual Studio Code, such as automatic reinstallation and removal of extensions without user consent. These problems can frustrate users and require manual intervention to resolve.
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.
- VSCode Removing Extensions on its Own
- Toxicity Score: 0.65 (Frustration, critical tone, lack of resolution, escalating complaints.)
- This GitHub conversation involves multiple users expressing frustration over VSCode's automatic removal of extensions without user consent. The original poster and other users, such as username1, share a sentiment of annoyance and demand a solution that respects their choices. The tone is generally critical and exasperated, with some users providing additional context and potential workarounds. Tension arises from the perceived lack of control and the inadequate response from the VSCode team.
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: 0
As of our latest update, there are no open pull requests for the project this week.
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: 12
Key Closed Pull Requests
1. require 'prompt files' synchronization to be explicitly enabled by users: This pull request addresses privacy concerns by requiring users to explicitly enable the synchronization of 'prompt files' in Visual Studio Code, ensuring that this feature is only activated through the settings sync configuration dialog to protect potentially sensitive information.
- URL: pull/242360
- Merged: No
2. Smoke tests: Adding acceptance condition to dispatchKey: This pull request aims to enhance the smoke tests for the Visual Studio Code project by adding an acceptance condition to the dispatchKey function, addressing issue #237673, although it was ultimately not merged.
- URL: pull/239902
- Merged: No
3. Support targeting multiple scopes in a theme with tree sitter: This pull request introduces support for targeting multiple scopes in a theme using Tree-sitter in the Visual Studio Code project, as evidenced by the commits that include implementing the feature, fixing tests, and merging updates from the main branch.
- URL: pull/241703
- Merged: 2025-03-05T11:07:56Z
Other Closed Pull Requests
- Abstract Modified File Entry Reuse: This pull request introduces more reuse through an abstract modified file entry, addressing issues #13692 and #13693 in the vscode-copilot repository. It was successfully merged on March 2, 2025.
- Validation Checks for Startup Editor: This pull request addresses an issue in the Visual Studio Code project by adding validation checks to prevent an unnecessary warning from being logged. It ensures that only valid startup editor values trigger warnings.
- Terminal Suggestion Bug Fix: This pull request addresses a bug in the terminal suggestion feature where unexpected completions were returned. It ensures exact matches for command completions and corrects the comparison between
specLabelandcommand.label.
- API Tests with Test Runner: This pull request involves enabling API tests with a test runner for the Visual Studio Code project. It was successfully merged on March 3, 2025.
- Text Rendering Misalignment Fix: This pull request addresses the issue of misalignment in text rendering when word wrap is toggled. It transfers logic to ensure correct positioning of screen reader content.
- Night Owl Light Theme Adjustment: This pull request addresses and resolves issue #241887 by adjusting the color scheme of the Night Owl Light theme. It reduces the blue tint when using Tree Sitter highlighting.
- Comment Update Follow-up: This pull request involves updating a comment as a follow-up to a previous pull request (#242117). It was successfully merged into the Microsoft VSCode project on March 3, 2025.
- Writable Local Extension Files: This pull request addresses an issue in the Visual Studio Code project by making local extension files writable during the zip creation process. It is referenced in issue #151543.
- Pausing Problem Generation During Edits: This pull request addresses the issue of pausing problem generation during edits, rather than merely hiding squiggles. It resolves the specific problem tracked in https://github.com/microsoft/vscode-copilot/issues/13744.
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 |
|---|---|---|---|---|
| meganrogge | 175 | 2 | 33 | 169 |
| bpasero | 214 | 2 | 47 | 95 |
| gjsjohnmurray | 10 | 1 | 2 | 304 |
| Tyriar | 119 | 0 | 62 | 135 |
| TylerLeonhardt | 4 | 0 | 16 | 152 |
| jrieken | 69 | 2 | 19 | 41 |
| lszomoru | 41 | 0 | 4 | 72 |
| legomushroom | 106 | 1 | 4 | 2 |
| roblourens | 67 | 0 | 6 | 37 |
| alexr00 | 65 | 2 | 4 | 24 |