CI(codecov): do not notify until all reports are ready

[njzjz]

Summary by CodeRabbit

• Chores
  • Updated the code coverage notification settings to trigger alerts after 14 builds, improving monitoring of code coverage metrics.

[coderabbitai]

Walkthrough

Walkthrough

The pull request introduces a modification to the codecov.yml configuration file by adding a new notify subsection. This subsection includes a parameter after_n_builds, which is set to 14. This update specifies that notifications regarding code coverage will be triggered after 14 builds, thus refining the notification strategy for monitoring code coverage metrics without altering existing functionality.

Changes

File	Change Summary
codecov.yml	Added codecov.notify.after_n_builds: 14

Sequence Diagram(s)

sequenceDiagram
    participant CI as Continuous Integration System
    participant Codecov as Codecov Service
    CI->>Codecov: Trigger build
    Note right of Codecov: Build completed
    CI->>Codecov: Notify after 14 builds
    Codecov-->>CI: Send notification

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 64e6e52 and 5bff430.

Files selected for processing (1)

• codecov.yml (1 hunks)

Additional comments not posted (1)

codecov.yml (1)

47-50: LGTM! The after_n_builds configuration is a good addition.

Setting after_n_builds to 14 aligns with the total number of builds (12 Python + 2 C++) and will trigger notifications only after all builds are complete. This approach has several benefits:

1. Reduces noise by consolidating notifications instead of sending them after each individual build.
2. Provides a more comprehensive view of the overall code coverage status across all builds.
3. Helps maintainers and reviewers quickly identify if any build has coverage issues that need attention.

Great work on enhancing the notification strategy!

---

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>, please review it.
  -- 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 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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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 83.02%. Comparing base (64e6e52) to head (5bff430).
Report is 2 commits behind head on devel.

Additional details and impacted files

@@            Coverage Diff             @@
##            devel    #4136      +/-   ##
==========================================
- Coverage   83.03%   83.02%   -0.01%     
==========================================
  Files         532      532              
  Lines       52187    52187              
  Branches     3030     3030              
==========================================
- Hits        43331    43328       -3     
- Misses       7911     7914       +3     
  Partials      945      945              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.