feat: add paths to codspeed.yml

[shenxianpeng]

follow-up to #81

Summary by CodeRabbit

• Chores
  • Updated workflow triggers so that the CodSpeed workflow now runs only when relevant files or directories are changed on the main branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.12%. Comparing base (4c09c13) to head (33a40c5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   95.12%   95.12%           
=======================================
  Files           3        3           
  Lines          82       82           
=======================================
  Hits           78       78           
  Misses          4        4           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Walkthrough

The CodSpeed GitHub Actions workflow configuration was updated to restrict its triggers. Now, the workflow only runs on pushes and pull requests affecting specific files or directories and only on the "main" branch. No changes were made to exported or public entities in the codebase.

Changes

File(s)	Change Summary
.github/workflows/codspeed.yml	Updated workflow triggers to include path filters and restrict pull_request events to the "main" branch.

Possibly related PRs

• feat: support codspeed #81: Modifies the trigger paths and branch filters of the same CodSpeed GitHub Actions workflow, directly related to .github/workflows/codspeed.yml.

---

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

• 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.
  • 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/codspeed.yml (2)

6-11: Verify that the new paths filter covers every file that affects benchmarks

Only changes under cpp-linter-hooks/**, tests/**, the workflow file itself, and pyproject.toml will now trigger CodSpeed.
If benchmark-relevant code lives elsewhere (e.g. a src/** folder or top-level Python modules) a commit may silently skip performance checks.

       - "pyproject.toml"
+      # Consider adding the actual source tree or a catch-all for Python files
+      - "src/**"
+      - "**/*.py"

Double-check the repository layout and expand the list if needed.

---

13-19: Branch & path restrictions on pull_request could miss valid PRs

Limiting to branches: [ "main" ] is fine—GitHub compares against the base branch—but the same path filter caveat applies here.
External contributors editing files outside the listed paths will not get benchmark feedback, which may hide regressions.

Consider whether you want CodSpeed on every PR targeting main, irrespective of touched files, or keep the current optimisation.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c09c13 and 33a40c5.

📒 Files selected for processing (1)

• .github/workflows/codspeed.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run benchmarks

[codspeed-hq]

CodSpeed Performance Report

Merging #84 will not alter performance

_{Comparing update-codspped-path (33a40c5) with main (4c09c13)}

Summary

✅ 31 untouched benchmarks