fix: setup qlty for code coverage reports

[matteoredz]

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline to use Ruby 3.4 for improved performance and compatibility
  • Migrated code coverage reporting to a new service platform
  • Refreshed code quality and coverage badge sources in project documentation

[coderabbitai]

Walkthrough

Workflows migrated from Code Climate to QLTY for code coverage tracking. Ruby version updated from 2.7.0 to 3.4 with expanded matrix testing. README badge URLs updated to reference QLTY instead of Code Climate.

Changes

Cohort / File(s)	Change Summary
Workflow Configuration .github/workflows/release.yml, .github/workflows/test.yml	Ruby version bumped to 3.4; secret key renamed to QLTY_COVERAGE_TOKEN; Code Climate coverage action replaced with QLTY coverage action; Ruby matrix expanded to include 3.4; coverage file path updated.
Documentation README.md	Maintainability and Code Coverage badge URLs migrated from Code Climate to QLTY.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify QLTY_COVERAGE_TOKEN secret is available in repository settings
• Confirm coverage file path coverage/.resultset.json aligns with test output
• Validate Ruby 3.4 compatibility with project dependencies

Poem

🐰 From CodeClimate's arms we hop away,
To QLTY's embrace, hip-hip-hooray!
Ruby 3.4 runs swift and bright,
Badges renewed, coverage in sight!
Our tests now dance in the morning light. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: replacing Code Climate with qlty for code coverage reporting across workflows and documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-code-coverage-report

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e19de59 and 360455d.

📒 Files selected for processing (3)

• .github/workflows/release.yml (2 hunks)
• .github/workflows/test.yml (3 hunks)
• README.md (1 hunks)

🔇 Additional comments (4)

.github/workflows/release.yml (1)

14-14: Consistent secret and Ruby version updates for QLTY migration.

The changes correctly propagate QLTY_COVERAGE_TOKEN to the test workflow and update the release Ruby version to 3.4, aligning with the coverage job configuration. No issues identified.

Also applies to: 50-50

.github/workflows/test.yml (2)

39-43: QLTY action confirmed, but verify SimpleCov coverage path in your build.

The qltysh/qlty-action/coverage action is official and requires a free Qlty Cloud account for code coverage reporting. The action, token, and files parameter are correctly configured. However, the success depends on:

1. Coverage path validation: Confirm that your test setup (likely using SimpleCov) generates coverage/.resultset.json. If your project uses a different coverage format or path, the files parameter must be adjusted accordingly.
2. Qlty Cloud account: Ensure your account is set up and the QLTY_COVERAGE_TOKEN secret is properly configured in your GitHub repository with the correct token value.

Assuming these prerequisites are in place, the implementation is sound.

---

11-12: I need to verify two more details to confirm the review comment:

Based on the web searches, I can now provide the verification:

SimpleCov output path confirmed. SimpleCov automatically caches coverage results in your (coverage_path)/.resultset.json, so coverage/.resultset.json is the correct path for the default configuration.

QLTY action confirmed. The qltysh/qlty-action is a collection of reusable GitHub Actions, with the coverage action requiring a free Qlty Cloud account. The first search confirmed that simplecov is an explicitly supported coverage format.

One verification gap: The search results do not explicitly confirm the stability or current status of version @v2. The GitHub qlty-action repository exists, but the search results don't contain specific version release information to verify whether v2 is the current stable version.

---

Confirm QLTY action/coverage@v2 stability and current availability.

The workflow correctly uses the coverage path coverage/.resultset.json (the standard SimpleCov output location) and the qltysh/qlty-action is confirmed as a reusable GitHub Action with simplecov as an explicitly supported coverage format. However, verify that @v2 is the current, stable version of this action by checking the GitHub action marketplace or the qltysh/qlty-action repository's releases page to ensure no breaking changes have been introduced since v2's release.

README.md (1)

3-3: Badge URLs are correctly formatted and follow QLTY's documented conventions.

The badge URLs match QLTY's standard format with the correct project path (matteoredz/projects/itax-code) and endpoints (maintainability.svg, coverage.svg). No changes needed.

---

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