chore(codecov.yml): fix config file

[lumtis]

Description

Tentative to fix coverage number

Summary by CodeRabbit

• Chores
  • Updated the coverage configuration for improved clarity and organization.
  • Renamed sections to reflect a more streamlined structure without changing functionality.

[coderabbitai]

Walkthrough

Walkthrough

The recent modifications to the codecov.yml file involve a reorganization of the coverage configuration, specifically renaming sections from common to pkg. This change aims to improve clarity and structure within the codebase. Additionally, the ignore patterns have been refined for better maintainability by grouping related directories, thereby enhancing the overall effectiveness of coverage reporting without impacting functionality.

Changes

Files	Change Summary
codecov.yml	Renamed sections: coverage.common → coverage.pkg, flags.common → flags.pkg, ignore.common → ignore.pkg. Updated paths in flags to match new naming. Adjusted and streamlined ignore patterns, explicitly listing zetaclient/testdata/**/* and zetaclient/testutils/**/*. Removed specific file types in favor of broader directory naming.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.57%. Comparing base (9faeb15) to head (0014520).

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #2575       +/-   ##
============================================
+ Coverage    46.80%   71.57%   +24.77%     
============================================
  Files          465      327      -138     
  Lines        30820    17798    -13022     
============================================
- Hits         14425    12739     -1686     
+ Misses       15539     4490    -11049     
+ Partials       856      569      -287     

see 138 files with indirect coverage changes

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9faeb15 and 0014520.

Files selected for processing (1)

• codecov.yml (4 hunks)

Additional comments not posted (3)

codecov.yml (3)

18-22: Ensure consistency in coverage targets and flags.

The addition of the pkg entry aligns with the existing structure for zetacore and zetaclient. Ensure that the target coverage and flags are correctly set for the pkg section.

---

36-38: Verify the path for the pkg flag.

The addition of the pkg flag with the path "pkg/" is consistent with the naming convention changes. Ensure that the path correctly corresponds to the intended directory.

---

64-65: Ensure the necessity of new ignore patterns.

The addition of ignore patterns for zetaclient/testdata/**/* and zetaclient/testutils/**/* helps in maintaining clarity. Ensure these directories contain files that should be excluded from coverage.