A GitHub Action that publishes code coverage reports to Code Climate from CI workflows.
codeclimate-action is a GitHub Action that automatically sends code coverage data from your continuous integration pipelines to Code Climate. It executes your test coverage commands, collects the resulting coverage reports, and uploads them to Code Climate for analysis and tracking. This helps development teams maintain visibility into their test coverage metrics directly within their GitHub workflows.
Development teams using GitHub Actions for CI/CD who want to integrate Code Climate's test coverage tracking into their automated workflows. Particularly useful for projects with multiple languages or monorepo structures.
Developers choose this action because it provides a reliable, configurable way to integrate Code Climate coverage reporting without manual scripting. It supports numerous coverage formats, handles complex scenarios like monorepos, and includes security features like binary verification.
GitHub Action to send your code coverage to CodeClimate
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports a wide range of coverage formats including Clover, Cobertura, LCOV, Jacoco, and more, as listed in the README, making it versatile for polyglot codebases.
Can aggregate coverage from multiple subprojects using glob patterns and path configurations, demonstrated in the Jest monorepo example with detailed setup instructions.
Includes options to verify downloaded reporter binaries with checksums and GPG signatures, enhancing security for automated workflows.
Requires only the CC_TEST_REPORTER_ID and optional commands for basic setup, simplifying integration into GitHub Actions with examples provided.
Relies on Code Climate, which has been deprecated in favor of Qlty, making future support uncertain and migration necessary for long-term projects.
For Ruby projects using SimpleCov, an additional gem (simplecov_json_formatter) is needed to avoid JSON errors, adding extra setup steps.
Configuring correct paths for monorepos or specific tools like Jacoco requires manual adjustments, as highlighted in the examples, which can be error-prone.