Weekly GitHub Report for Vscode: May 12, 2025 - May 19, 2025 (12:01:38)
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.
-
Extension Signature Verification Failed: GitHub Copilot Chat: This issue is about a bug in the GitHub Copilot Chat extension for Visual Studio Code, where the extension's signature verification fails, preventing updates from being applied. The problem is reported to occur across different operating systems and environments, including Windows, macOS, and Linux, and involves an error related to the inability to load the
vsce-signmodule.- The comments discuss the need for additional logs to diagnose the issue, with users sharing their experiences of similar problems across different platforms. A suggestion is made that the issue might be related to using a non-official build of VS Code, and users are asked to provide more information about their environments, including Docker or devcontainer files, to help reproduce the issue. There is also a mention of related issues being reported by other users.
- Number of comments this week: 9
-
My VSCode was BROKEN!: This issue is about a user experiencing a problem with Visual Studio Code (VSCode) where the application fails to open properly, displaying a blank window, and the user is seeking assistance to resolve this issue. The problem persists even after attempting to disable extensions and GPU, and it seems to be related to a TypeError in the application code, with the issue being specific to the Debian package of VSCode.
- The comments reveal that the user was initially advised to update VSCode to the latest version, which they confirmed was already done. Another user reported a similar issue on Linux, and attempts to troubleshoot included disabling extensions, GPU, and resetting configurations, all of which failed. The problem was identified as a TypeError, and updating to version 1.100.2 resolved the issue when using Snap and Flatpak packages, but the Debian package continued to malfunction.
- Number of comments this week: 8
-
in v1.100.0 it feels like the .github/copilot-instructions.md is now ignored: This issue reports that in version 1.100.0 of VS Code, the
.github/copilot-instructions.mdfile appears to be ignored by the AI, as it no longer references or consults the specified documentation files before making code modifications. The user notes that prior to the update, the AI would begin by acknowledging and utilizing the instructions within the file, but this behavior has ceased, leading to concerns about the effectiveness of the instructions.- The comments discuss the issue of the AI not referencing the specified files as it did before the update, with suggestions to rename files according to documentation and use Markdown links for references. Users express frustration that the instructions are not being followed, and there is speculation about changes in how the AI processes these instructions, with some users noting that different AI models handle the instructions differently.
- Number of comments this week: 7
-
Add Indexing Feature for Faster Navigation Between References: This issue is a feature request for Visual Studio Code to implement an indexing feature similar to those found in PyCharm or WebStorm, aimed at improving the speed of navigation between references within large projects. The current problem is that VSCode takes a long time to load references, especially in large codebases, which can be frustrating for developers who are accustomed to the nearly instant navigation provided by other IDEs with indexing capabilities.
- The comments discuss the languages affected, mainly TypeScript and Python, and the handling of language features by extensions. Users highlight the performance issues in large projects and suggest comparing VSCode's navigation speed with WebStorm's to illustrate the difference. There is a debate on whether the issue is due to a lack of indexing or other factors, with suggestions for further investigation and testing.
- Number of comments this week: 7
-
After restart of VSCode due to an upgrade, many files are opened in my project, all with the last change undone: This issue describes a bug in Visual Studio Code where, after an upgrade and restart, multiple files in a project are reopened with their last changes undone, despite the user having closed all files before the restart. The user finds this behavior particularly frustrating as it disrupts their workflow, and it continues to occur with each restart of the application.
- The comments discuss potential solutions and clarifications for the issue, including the use of the "hot exit" feature, which remembers unsaved files between sessions. Suggestions include turning off the "hot exit" feature, recording the issue for better understanding, and manually deleting backup files to prevent unsaved changes from reappearing.
- Number of comments this week: 7
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-windowor?reuse-windowfails 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 hijacking of the existing window rather than creating a new one. ${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, leading to execution errors. The problem does not occur when using${env:USERPROFILE}instead, which correctly formats the path for execution.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue involves a bug in Visual Studio Code 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 problem specifically affects remote connections, such as those using WSL or SSH, and seems to be related to the remote connection entering a "sleep" state when the main window is minimized, causing a delay in character display until the main window is restored.
- setting "preLaunchTask" leads to error "Cannot read properties of undefined (reading 'kind')": This issue involves a problem with Visual Studio Code where setting the "preLaunchTask" in a launch configuration results in an error message stating "Cannot read properties of undefined (reading 'kind')". The error occurs when attempting to run a launch configuration with a "preLaunchTask" specified, and it is noted that removing the "preLaunchTask" allows the launch to proceed without issues, suggesting a bug related to task recognition or configuration.
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: 189
Summarized Issues:
- GitHub Copilot Issues: GitHub Copilot is facing multiple issues, including incorrect Python command suggestions in a Next.js/TypeScript project and failure to update due to signature verification errors. These problems are compounded by compatibility issues with certain API proposals and the absence of necessary packages, affecting users across different environments.
- Visual Studio Code Performance Problems: Visual Studio Code users are experiencing significant performance issues, including slow startup times and unresponsiveness during use. These problems persist even with all extensions disabled and are reported on various operating systems, indicating potential underlying software inefficiencies.
- Visual Studio Code Debugging Issues: Users have reported several debugging-related issues, such as the unexpected appearance of the debug toolbar in auxiliary windows and the inability to attach to Chrome for debugging purposes. These issues hinder the debugging process and require workarounds or alternative solutions.
- Visual Studio Code UI/UX Enhancements: There are multiple requests for UI/UX enhancements in Visual Studio Code, including increased spacing in the Activity Bar and the addition of alt-text support for images. These enhancements aim to improve usability and accessibility for a diverse range of users.
- Visual Studio Code Terminal Issues: The integrated terminal in Visual Studio Code is experiencing various issues, such as incorrect rendering of Unicode text and unexpected scrolling behavior. These problems affect the terminal's functionality and user experience, requiring attention to improve stability.
- Visual Studio Code Extension Problems: Users are encountering issues with extensions in Visual Studio Code, including signature verification failures and problems with the GitHub Copilot Chat extension. These issues prevent the proper installation and functioning of extensions, impacting productivity.
- Visual Studio Code Git Integration Issues: There are several issues related to Git integration in Visual Studio Code, such as the inability to activate the 'Git' extension on a remote host and problems with the Git checkout command. These issues disrupt the workflow for users relying on Git for version control.
- Visual Studio Code Feature Requests: Users have submitted various feature requests for Visual Studio Code, including the ability to configure the initial size and position of the first window and the addition of a
code-terminalshell command. These requests aim to enhance the flexibility and functionality of the editor.
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: 191
Summarized Issues:
- Visual Studio Code Performance Issues: Visual Studio Code users have reported various performance issues, including high CPU usage, memory consumption, and application freezes. These problems often occur during specific actions like opening files, running commands, or using extensions, and are sometimes linked to recent updates or specific configurations.
- GitHub Copilot and Chat Issues: Users have encountered several issues with GitHub Copilot and chat features in Visual Studio Code, including unexpected behavior, performance delays, and authentication problems. These issues often disrupt the user experience by causing errors, slow responses, or unresponsive interfaces.
- Terminal and Environment Variable Bugs: Several issues have been reported regarding the terminal and environment variables in Visual Studio Code, including incorrect character encoding and terminal display problems. These bugs can lead to disrupted workflows and require users to adjust settings or downgrade versions to resolve them.
- Extension Signature Verification Failures: Users have experienced issues with extension signature verification in Visual Studio Code, particularly on non-official builds or specific operating systems. These failures prevent the installation or update of extensions and often require users to contact their software distributor for a solution.
- Visual Studio Code Debugging Issues: Debugging in Visual Studio Code has been problematic for some users, with issues such as breakpoints not triggering, debugger unresponsiveness, and configuration errors. These issues can hinder development processes and often require configuration adjustments or updates to resolve.
- Visual Studio Code UI and Usability Concerns: Users have reported various UI and usability issues in Visual Studio Code, including missing buttons, unresponsive elements, and confusing interface layouts. These concerns can affect productivity and often require updates or configuration changes to address.
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.
-
Accidentally removed WSL Ubuntu via Remote Explorer — no confirmation, entire data lost
- Toxicity Score: 0.55 (Mixed sentiments, confrontational tone, user frustration, potential for blame-shifting.)
- This GitHub conversation involves several users discussing a data loss issue related to the Remote - WSL extension in Visual Studio Code. The original poster, hui-cyber, expresses frustration and seeks help after losing critical data due to a misunderstanding of the "Remove" option's consequences. Another user questions the clarity of the prompt and suggests improvements, while a third user, with a more confrontational tone, criticizes hui-cyber for not taking responsibility and suggests recovery options. The conversation includes a mix of supportive and critical sentiments, with some users offering sympathy and advice, while others emphasize user responsibility.
-
error in processing .gitignore file
- Toxicity Score: 0.55 (Strong disagreement, Frustration, Escalating tone.)
- This GitHub conversation involves multiple users discussing an issue with Visual Studio Code's handling of .gitignore files. User1 reports a problem and User2 attempts to clarify the situation with a detailed explanation, suggesting a potential misunderstanding. User3 provides a technical explanation, while User4 strongly disagrees, expressing frustration and emphasizing the inconsistency in VS Code's behavior. The tone escalates as User4 insists on the need for consistent behavior, highlighting a poor user experience and the necessity for a workaround.
-
- Toxicity Score: 0.55 (Frustration over delay, critical tone, historical neglect.)
- This GitHub conversation involves two users expressing frustration over a long-standing issue with a software feature. The first user, without a specific username, comments on the delay in addressing the issue, which is echoed by the second user who elaborates on the inconvenience caused by the lack of the feature. The tone is critical and exasperated, with both users highlighting the time elapsed since the issue was first raised. The trigger of tension is the perceived neglect by the software developers to implement a seemingly basic feature.
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: 18
Key Open Pull Requests
1. Font Size PR with Screen Reader Change: This pull request aims to enhance the Visual Studio Code editor by implementing changes to support dynamic font sizes and line heights, particularly focusing on improving the handling of decorations that affect text rendering, and ensuring that these changes are accessible to screen readers.
- URL: pull/249098
- 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, cb5a2, 64dc6, 62c71, 602b6, 26006, 58df4, 87bfa, 236cf, 6fd96, 1e424, 6e2bf, ba098, ef376, de396, b12e2, 7e68f, 2906d
2. Add some tree sitter API tests: This pull request involves adding several tests for the tree-sitter API in the Visual Studio Code project, including tests for the getChangedRanges function, while ensuring no tree-sitter files are altered to prevent conflicts, as evidenced by multiple commits addressing test additions, comments, and minor fixes.
- URL: pull/249078
- Merged: No
3. New branch: This pull request, titled "New branch," involves multiple commits with various updates and changes to a file named "thefile.html" in the Visual Studio Code repository, but it lacks a detailed description of the proposed changes and testing instructions, and it has not yet been merged.
- URL: pull/249123
- Merged: No
Other Open Pull Requests
- New Sound Feature and Announcement Setting: This topic covers the introduction of a new sound feature for
chatUserActionRequiredand the addition of anannouncementsetting. The pull request addresses issues #244290 and #248200, involving tasks such as swapping in a sound from @afre100 and testing the implementation.
- Extension Marketplace Warning Feature: This feature warns users about installed extensions in Visual Studio Code that are no longer available in the Marketplace. It leverages the
ExtensionsWorkbenchService::checkForUpdates()function to identify and display such extensions, addressing issue #181248.
- Chat Style Update with Text Bubbles: The pull request involves updating the chat style by implementing text bubbles, re-adding accidentally deleted CSS, and ensuring the bubbles are both bordered and right-aligned. This update is detailed in the associated commits.
- Copy Test Name Submenu Feature: This pull request introduces a new "Copy Test Name" submenu feature to the project. It includes updates to the clipboard service path to support this functionality.
- Service-Worker Exclusion from TypeScript Configuration: The pull request aims to exclude the service-worker from the main TypeScript configuration project in the Visual Studio Code repository. It includes updates to ensure the code is aligned with the main branch.
- Log tmLanguage File Update: This update incorporates changes from the vscode-logfile-highlighter version 3.4.1, specifically addressing the Trace regex. It includes commits for updating the language file and fixing colorization tests for logs.
- Zsh Shell Integration Enhancement: The pull request enhances the zsh shell integration by replacing the '-v' option with '-n' and implementing parameter expansion. This enhancement is detailed in the associated issue.
- IEditorOptions Interface Property Sorting: This pull request involves sorting properties within the IEditorOptions interface. The changes are indicated by the commit message and the associated commit link.
- Dialog Message Maximum Height: The pull request addresses issue #248731 by adding a maximum height to dialog messages to prevent text overflow. It is currently not merged.
- Stream Listening and Unlistening Enhancement: This pull request aims to enhance the mechanisms for stream listening and unlistening. It is referenced in issue #248389.
- Bubble Approach Transition: This pull request involves making miscellaneous changes aimed at transitioning to a "bubble" approach within the project. It is currently open and not yet merged.
- Parallel Test Execution: The pull request aims to enhance the testing process by enabling tests to run in parallel. This change potentially improves efficiency and reduces the time required for test execution.
- Webview Resource Loading Improvement: This pull request addresses the issue of delayed webview resource loading by modifying the service worker controller. It prevents unnecessary service worker restarts and avoids the retrieval of stale clients due to ID changes.
- AI Search Delay Mechanism: The pull request introduces a feature that adds a delay mechanism to the AI search functionality. It reduces the number of requests sent to the AI settings search service and enhances the service's capability to store results.
- Git Checkout Dirty Work Tree Fix: This pull request addresses issue #249087 by implementing a fix for handling the "dirty work tree" error in the
git.checkoutcommand. It ensures that the code is aligned with the main branch and provides a detailed description and testing instructions.
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: 182
Key Closed Pull Requests
1. chat - revamp the setup dialog: This pull request involves a comprehensive revamp of the setup dialog in the Visual Studio Code project, as indicated by the title and the series of commits, which include multiple tweaks and adjustments, ultimately leading to its successful merge on May 14, 2025.
- URL: pull/248789
- Merged: 2025-05-14T14:38:20Z
- Associated Commits: d157b, 5b43b, aeb85, d5c2a, d47e9, 27640, 6d75f, 5dc29, 39f1f, f007e, 21950, b72a9, c5975, cbacc, cbc56, 7144c, ad6b8, d6028
2. SCM Graph - show commit details: This pull request, titled "SCM Graph - show commit details," was merged on May 12, 2025, and involves multiple commits aimed at enhancing the Source Control Management (SCM) graph in Visual Studio Code by implementing features such as initial rendering of resources, opening a multi-file diff editor, adding actions and commands for file versioning, and fixing layout and focus-related issues, as referenced in the related issue #248696.
- URL: pull/248694
- Merged: 2025-05-12T09:43:53Z
- Associated Commits: 40bab, 0caf5, 3b648, d05e8, 5101d, 9254f, edf85, 8d097, 26492, 62f21, fa4b0, cae3a, 67cfa, 8a427
3. aux window - scoped services alignments: This pull request addresses the alignment of scoped services within auxiliary windows by implementing a top-to-bottom approach to ensure that the correct instantiation services are used for editor parts, thereby clarifying the responsibility for creating and using these services and reducing the complexity for downstream components like the title or status bar, especially in scenarios involving floating windows.
- URL: pull/249095
- Merged: 2025-05-16T14:44:02Z
Other Closed Pull Requests
- AI Cell Execution Tracking Enhancements: This topic involves improving the
autoRevealargument for AI cell execution tracking in Visual Studio Code. The pull request includes features like enabling or disabling the execution follower from the toolbar and overhauling the autoReveal behavior to prevent eager auto-revealing.
- SCM Chat Context and History Item Enhancements: This topic covers the introduction of chat context capabilities and the refinement of the history item context picker within the Source Control Management (SCM) feature of Visual Studio Code. The pull requests involve developing a variable widget, refactoring efforts, and polishing the history item context picker.
- Task Error Handling and Troubleshooting: This topic focuses on enhancing error handling in task-related chat functionalities and introducing a "Troubleshoot with Chat" task command. The pull requests include moving problems into code blocks, utilizing regex, and refining messages to support various task errors.
- MCP Server Features: This topic involves implementing a gallery view and a development mode for MCP servers in Visual Studio Code. The pull requests include changes to the schema and types, automatic server startup, and debugging capabilities.
- TypeScript Language Features: This topic introduces a new configuration option for TypeScript language features, allowing users to set a maximum length for hover text. The pull request addresses issue #233557 and includes related work in the TypeScript repository.
- Remote libcxx Requirement Reversion: This topic addresses reverting the remote libcxx requirement back to version 3.4.25 in the Microsoft VSCode project. The pull request includes debugging, updating the CI cache, and fixing directory paths for sysroot and objdump.
- Auxiliary Window Compact Actions: This topic focuses on enhancing the functionality of compact actions within the auxiliary window of Visual Studio Code. The pull request includes a series of commits aimed at improvements and fixes.
- Line Height Calculation and Decoration Options: This topic addresses issues related to line height calculation and decoration options in Visual Studio Code. The pull requests involve incorporating view data for line height and limiting decoration options to 300px.
- Chat Editing and Toolbar Enhancements: This topic enhances the chat editing experience and toolbar functionality in Visual Studio Code. The pull requests improve handling of editing strategies, support multiple response chunks, and swap chat input toolbar actions.
- Response Toolbar and UI Element Selection: This topic addresses the response toolbar and continuous selection of UI elements in Visual Studio Code. The pull requests implement a feature to hide the toolbar when not focused and ensure URL functionality.
- ChatPrepareToolInvocationPart Feature: This topic introduces the ChatPrepareToolInvocationPart feature to display a "working" progress indicator while a tool call is being generated. The pull request supports Claude and includes commits for the initial implementation and progress display setup.
- Class Fields Initialization Order: This topic addresses the implementation of the
useDefineForClassFieldsfeature in Visual Studio Code. The pull request fixes initialization order issues and ensures compatibility with explicitly defined class fields.
- Commit Message Generation with GitHub Copilot: This topic introduces a stub action for generating commit messages using GitHub Copilot within the SCM feature of Visual Studio Code. The pull request includes the initial implementation and updates to integrate with the main branch.
- Typographical and Grammatical Corrections: This topic addresses minor typographical and grammatical errors in the Microsoft VSCode project. The pull request corrects a typo in the
quickFix.tsfile and ensures proper grammar in theextensions/references-view/README.mdfile.
- Auto Semantic Search Settings: This topic introduces a modification to the auto semantic search settings in the VSCode project. The pull request adds an option to automatically perform a semantic search only when text search results are empty.
- R Syntax Upstream Repository Update: This topic updates the upstream repository for R syntax in Visual Studio Code. The pull request points to the new location of the syntax file and includes updates to the cgmanifest and grammar.
- Tab Key Functionality in Tool Confirmation: This topic addresses issue #249134 by ensuring that the tab key does not get stuck in the tool confirmation code block. The pull request sets an
editorOptionand fixes its application to allow focus movement.
- Custom Line Number Bug Fix: This topic addresses a bug fix in Visual Studio Code by ensuring that a custom line number is strictly greater than the
toLineNumberbefore performing a deletion. The pull request references issue #247676 and was successfully merged.
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.
- Show line range in github uri references
- Toxicity Score: 0.55 (Frustration expressed, Tension in responses, Attempts to de-escalate.)
- This GitHub conversation involves username1 and username2, where username1 initially provides a solution that username2 finds ineffective, leading to username1 expressing frustration. The tone shifts as username2 attempts to clarify their position, but username1's continued dissatisfaction creates tension. Despite username2's efforts to de-escalate, the conversation remains strained, with both parties showing signs of impatience.
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 | 167 | 23 | 50 | 75 |
| meganrogge | 71 | 9 | 28 | 158 |
| legomushroom | 204 | 2 | 1 | 23 |
| roblourens | 97 | 13 | 32 | 54 |
| jrieken | 84 | 18 | 23 | 51 |
| connor4312 | 70 | 9 | 11 | 79 |
| lszomoru | 85 | 19 | 16 | 29 |
| albertosantini | 0 | 0 | 1 | 132 |
| justschen | 69 | 12 | 4 | 34 |
| sandy081 | 46 | 12 | 8 | 34 |