Weekly GitHub Report for Vscode: June 02, 2025 - June 09, 2025 (12:03:06)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
Released on March 12, 2025, this version of Visual Studio Code focuses on resolving issues identified in the February 2025 Recovery 2 milestone, with detailed release notes available on the official website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
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.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request for Visual Studio Code to support the generation and display 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 alongside markdown cells, enhancing the functionality and interactivity of notebooks in 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-window
or?reuse-window
fails to open a new window as intended, instead replacing the existing window with the new connection. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, resulting in the disconnection from the current server and the connection being switched to the new server without opening a separate window. ${userHome}
in a task command creates bad paths: This issue involves a problem with the${userHome}
variable in a task command within atasks.json
file, which creates incorrect paths when the task type is set to "process" instead of "shell" in Visual Studio Code. The incorrect path format results in an error indicating 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 the correct path and resolves the issue.- 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 "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: 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: 0
Summarized Issues:
As of our latest update, there were no issues closed in the project this week.
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.
As of our last update, there are no open or closed issues with discussions going on within the past week.
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: 0
As of our latest update, there are no closed pull requests for the project this week.
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.
As of our last update, there are no open or closed pull requests with discussions going on within 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 |
---|---|---|---|---|
bpasero | 102 | 1 | 21 | 41 |
meganrogge | 45 | 0 | 16 | 51 |
roblourens | 53 | 2 | 9 | 24 |
lszomoru | 63 | 0 | 7 | 10 |
aiday-mar | 62 | 3 | 5 | 7 |
jrieken | 56 | 0 | 7 | 12 |
albertosantini | 0 | 0 | 1 | 69 |
connor4312 | 36 | 0 | 3 | 30 |
legomushroom | 59 | 0 | 1 | 0 |
justschen | 46 | 3 | 1 | 8 |