ci: exclude generated/boilerplate packages from coverage

[QuantumExplorer]

Issue being fixed or feature implemented

Coverage metrics are diluted by packages that contain no testable application logic — generated gRPC bindings, JSON schema boilerplate, version const tables, etc. These inflate the denominator without being meaningful coverage targets.

What was done?

Added the following to .codecov.yml ignore list:

Package	Reason	Current Coverage
dapi-grpc	Generated gRPC bindings	55.83%
dashpay-contract	JSON schema + load boilerplate	54.55%
data-contracts	Schema definitions	25.35%
dpns-contract	JSON schema + load boilerplate	54.55%
feature-flags-contract	JSON schema + load boilerplate	0.00%
keyword-search-contract	JSON schema + load boilerplate	61.29%
masternode-reward-shares-contract	JSON schema + load boilerplate	54.55%
token-history-contract	JSON schema + load boilerplate	40.57%
wallet-utils-contract	JSON schema + load boilerplate	54.55%
withdrawals-contract	JSON schema + load boilerplate	54.55%
rs-platform-version	Large const version tables	—
simple-signer	Thin test-only wrapper	—

This focuses the project coverage % on actual application code (dpp, drive, drive-abci, sdk, dapi, etc.).

How Has This Been Tested?

Codecov config change only — no code changes.

Breaking Changes

None.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation if needed

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@QuantumExplorer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00746b91-821a-4282-b9b4-78e1dcd7449a

📥 Commits

Reviewing files that changed from the base of the PR and between 9ebc7e4 and 5b8814f.

📒 Files selected for processing (1)

• .codecov.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/exclude-generated-from-coverage

📝 Coding Plan

• Generate coding plan for human review comments

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.