Add Codecov integration for coverage reporting

[theturtle32]

Summary

• Integrates Codecov for automated coverage reporting and PR comments
• Configures coverage thresholds (85% project, 80% patches)
• Adds Codecov badge to README

Changes

• GitHub Actions: Added coverage generation and upload to Codecov (Node.js 20.x only)
• codecov.yml: Configured coverage targets, PR comment format, and ignore patterns
• README.md: Added Codecov badge for v2 branch

Coverage Configuration

• Project target: 85% (matches current coverage: 85.05%)
• Patch target: 80% (ensures new code is well-tested)
• Threshold: 1-2% tolerance to avoid false failures
• PR Comments: Shows coverage diff, flags, and file tree

Setup Required

After merging, the repository owner needs to:

1. Go to https://codecov.io/ and sign in with GitHub
2. Add the WebSocket-Node repository
3. Add CODECOV_TOKEN to GitHub repository secrets

Test Plan

• Configuration files validate against Codecov schema
• PR will trigger coverage upload after CODECOV_TOKEN is configured
• Codecov badge will display coverage percentage

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @theturtle32, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces Codecov integration into the project's CI/CD pipeline. The primary goal is to automate code coverage reporting, enforce minimum coverage standards for both the entire codebase and new contributions, and provide clear coverage feedback directly in pull request comments. This enhancement aims to improve code quality and maintainability by ensuring new code is adequately tested.

Highlights

• Codecov Integration: Integrates Codecov for automated code coverage reporting and comments directly within pull requests.
• Coverage Thresholds: Configures specific coverage thresholds: 85% for the overall project and 80% for new code introduced in patches, with defined tolerance levels.
• README Update: Adds a Codecov badge to the README.md file to visually display the current coverage status.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/websocket-tests.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces Codecov for coverage reporting, which is a great addition for maintaining code quality. The configuration in codecov.yml is well-structured. I've provided a few suggestions to refine the setup: one to improve the accessibility of the new README badge, and two for the codecov.yml file to reduce PR comment noise and improve consistency with your Vitest coverage configuration.

[gemini-code-assist]

For better accessibility and clarity, it's good practice to use more descriptive alt text for the Codecov badge. I suggest changing it from codecov to code coverage.

Suggested change

	[](https://codecov.io/gh/theturtle32/WebSocket-Node)
	[](https://codecov.io/gh/theturtle32/WebSocket-Node)

[gemini-code-assist]

To reduce comment noise on pull requests, consider setting require_changes to yes. This will ensure that Codecov only posts a comment when there's an actual change in code coverage, making PR discussions cleaner.

  require_changes: yes

[gemini-code-assist]

The vitest.config.mjs file excludes lib/version.js from coverage reporting. To maintain consistency and ensure Codecov's report accurately reflects what's being tested, it's a good practice to also add this file to the ignore list here.

  - "test/**"
  - "examples/**"
  - "bench/**"
  - "docs/**"
  - "scripts/**"
  - "lib/version.js"
  - "**/*.test.mjs"
  - "**/*.test.js"
  - "**/*.bench.mjs"