Skip to content

Add Code Coverage GH action #654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jul 10, 2025
Merged

Conversation

Alirexaa
Copy link
Contributor

@Alirexaa Alirexaa commented Mar 24, 2025

Pull Request

Related issue

Fixes #507

What does this PR do?

This pull request introduces a new GitHub Actions workflow for measuring and reporting code coverage. The workflow is configured to run on specific branches and includes steps to set up the environment, install necessary tools, and upload coverage reports to Codecov.

Key changes:

  • Added a new GitHub Actions workflow named coverage.yml to measure code coverage on trying, staging, and main branches.
  • Configured permissions to allow reading contents and writing issues.
  • Set up the environment to use Nightly Rust and installed cargo-llvm-cov for coverage data collection.
  • Added steps to run Meilisearch using Docker, collect coverage data, and upload the reports to Codecov.

PR checklist

Please check if your PR fulfills the following requirements:

  • Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
  • Have you read the contributing guidelines?
  • Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Summary by CodeRabbit

  • Chores
    • Introduced automated code coverage reporting for pull requests and key branches.
    • Code coverage reports are now uploaded to Codecov, with CI configured to fail if the upload fails.

@Alirexaa
Copy link
Contributor Author

@brunoocasali, I ran this action in my fork.
You can see coverage results at https://app.codecov.io/github/Alirexaa/meilisearch-rust/pull/1/tree.

Make sure CODECOV_TOKEN has been set in repo secrets.

Copy link
Contributor

coderabbitai bot commented May 17, 2025

Walkthrough

A new GitHub Actions workflow file, coverage.yml, has been added to automate code coverage reporting using Codecov. The workflow is triggered on pull requests and pushes to specific branches, runs Rust coverage tools, generates combined coverage reports, and uploads the results to Codecov, with conditional logic to skip certain branches and bots.

Changes

Files/Paths Change Summary
.github/workflows/coverage.yml Added a GitHub Actions workflow to automate Rust code coverage collection and upload to Codecov.

Assessment against linked issues

Objective Addressed Explanation
Add CodeCov to this repository. (#507)
Add the CodeCov badge on this repository README.md (#507) No changes to README.md or badge addition observed.
Ensure a minimum coverage is accepted (optional) (#507) No explicit minimum coverage threshold configuration found in the workflow file.

Poem

Hopping through the coverage fields,
With Codecov now, our progress yields!
Rusty tests all run with flair,
Reports uploaded with bunny care.
Workflows dance, the carrots cheer—
Our code is covered, never fear!
🐰✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (4)
.github/workflows/coverage.yml (4)

3-11: Simplify triggers by filtering branches at the on level
You can move branch restrictions into the on block to avoid complex if logic and unnecessary job invocations:

 on:
-  pull_request:
-  push:
-    branches:
-      - trying
-      - staging
-      - main
+  pull_request:
+    branches: [trying, staging, main]
+  push:
+    branches: [trying, staging, main]

This makes it clear which branches trigger the workflow and lets you remove some of the conditional complexity below.


28-33: Consider using the official actions-rs/toolchain action
Instead of the community fork dtolnay/rust-toolchain@nightly, the maintained actions-rs/toolchain@v1 is more widely used and regularly updated:

-      - uses: dtolnay/rust-toolchain@nightly
-        with:
-          components: llvm-tools-preview
+      - uses: actions-rs/toolchain@v1
+        with:
+          profile: minimal
+          toolchain: nightly
+          override: true
+          components: llvm-tools-preview

39-45: Fail fast on coverage steps
Wrap the combined commands with a stricter shell mode to stop on any error and avoid proceeding with incomplete data:

-      - name: Collect coverage data
-        run: |
+      - name: Collect coverage data
+        run: |
+          set -euo pipefail
           cargo llvm-cov --no-report --all-features --workspace
           cargo llvm-cov --no-report --doc --all-features --workspace
           cargo llvm-cov report --doctests --codecov --output-path codecov.json

This will immediately break if any subcommand fails.


46-50: Pin the Codecov Action to a specific patch version
Using @v5 can introduce unexpected changes when the action is updated. Pin to a known release, e.g.:

-      - name: Upload coverage reports to Codecov
-        uses: codecov/codecov-action@v5
+      - name: Upload coverage reports to Codecov
+        uses: codecov/[email protected]

This locks you to the tested version and avoids surprises on minor bumps.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 90a153c and 06d3ea6.

📒 Files selected for processing (1)
  • .github/workflows/coverage.yml (1 hunks)
🔇 Additional comments (1)
.github/workflows/coverage.yml (1)

12-15: Review required permissions
The Codecov Action may need additional permissions to post status checks or PR comments. Currently you have:

permissions:
  contents: read
  issues: write

Consider narrowing and adding only what’s required, for example:

permissions:
  contents: read
  checks: write
  pull-requests: write

Please verify the minimum scopes the Codecov Action requires.

@brunoocasali brunoocasali self-requested a review May 22, 2025 12:41
@Mubelotix Mubelotix changed the base branch from main to codecov July 10, 2025 15:59
@Mubelotix Mubelotix merged commit c2d6a67 into meilisearch:codecov Jul 10, 2025
7 of 8 checks passed
@Mubelotix Mubelotix mentioned this pull request Jul 10, 2025
3 tasks
@Mubelotix
Copy link
Collaborator

Thank you for your contribution! Coverage will be available on main shortly

@Mubelotix Mubelotix mentioned this pull request Jul 15, 2025
meili-bors bot added a commit that referenced this pull request Jul 15, 2025
682: Merge dev into main r=curquiza a=Mubelotix

Full changelog after this PR: (includes changes merged before this PR)

## What's Changed

### Breaking changes

* Fix deleted_tasks field type in TaskDeletion struct by `@coinmoles` in #666 (`TaskDeletion.deleted_tasks` and `TaskCancelation.canceled_tasks` have been made `Option`s)

### Enhancements

* Support all experimental features by `@ellnix` in #656
* Add `usedDatabaseSize` to stats by `@Alirexaa` in #653
* Add facet_search API functionality by `@hmacr` in #512
* Allow users to customize facet value sort behaviour by `@hmacr` in #514
* Support `embedders` setting and other vector/hybrid search related configuration by `@CommanderStorm` in #554
* Add documents and embbedings database metrics to stats response by `@Alirexaa` in #652
* Support facet search and prefix search settings by `@ellnix` in #634
* Serialize for MultiSearchResponse by `@milesgranger` in #668
* Implement federated multi search by `@LukasKalbertodt` in #625
* Add support for similar docs query by `@JiaYingZhang` in #674

### Maintainance

* Remove _md code samples for Mintlify migration by `@curquiza` in #661
* Add missing `exist` to `*_update` functions' docs by `@funlennysub` in #617
* Add Code Coverage GH action by `@Alirexaa` in #654








## New Contributors
* `@Alirexaa` made their first contribution in #653
* `@funlennysub` made their first contribution in #617
* `@milesgranger` made their first contribution in #668
* `@coinmoles` made their first contribution in #666
* `@JiaYingZhang` made their first contribution in #674

**Full Changelog**: v0.28.0...v0.29.0


Co-authored-by: hmacr <[email protected]>
Co-authored-by: Clémentine U. - curqui <[email protected]>
Co-authored-by: Frank Elsinga <[email protected]>
Co-authored-by: Clémentine <[email protected]>
Co-authored-by: Vladimir Donich <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add CodeCov
2 participants