Codacy Product Showcase: April 2024

Group 370

Codacy Security Adds Thousands of New SAST Rules With Semgrep Integration

Group 370

New Coverage Status Checks Added

In this article:
Subscribe to our blog:

Our recently introduced Coverage pipeline now sends more detailed and much faster diff coverage status checks to all your pull requests on all our supported Git providers.

These new, speedier status checks are currently in an open beta phase. They are visible as two additional checks on your pull requests, marked "beta," alongside the preexisting Codacy Coverage check. This is what the additional checks look like on GitHub: 



We've developed these new status checks to provide you with: 

  • More detail: Each new check sends distinct and highly specific coverage information.

  • Improved speed: Checks now take seconds, not minutes.

  • Greater control: You now have more options to block low-quality pull requests and safeguard the quality of your code.


Deprecation and Retirement of the Old Coverage Check

To minimize the risk of disruption to your workflows, we will slowly deprecate and retire the old checks. The timetable for these changes looks like this:




What to expect

February 14, 2024

Deprecation of the old Coverage status check

From this day on, the new checks will no longer be marked beta and will be considered the de facto status checks for Codacy Coverage. The old check will be marked deprecated but will keep working.

If, on this date, you are still using the old check to block merging pull requests on GitHub, please update your settings.

April 18, 2024 

Brownout of the old Coverage status check

Codacy will not send the old status check on this day.

This will help you confirm that your setup has been updated correctly and lower the risk of disruptions when the old status check is removed.

June 5, 2024

Removal of the old Coverage status check

Codacy will stop sending the old status check.

If, on this date, you are still using the old check to block merging pull requests on GitHub, you will no longer be able to merge them. To fix this, you will simply need to update your GitHub settings.

What to Expect from the New Coverage Checks

Faster checks. Initial tests show marked improvements, slashing analysis times from minutes to seconds.

Compared to the old check, the new checks may send different values in some cases, depending on your setup and the contents of your coverage reports.

We will keep improving these new checks based on your needs and preferences. 

We encourage you to check it out first-hand and tell us your thoughts! 


New Pull Request Coverage Diff View Is Live
Developers often struggle to find and keep track of uncovered lines in their pull requests (PRs). Our latest feature, the Pull Request Coverage Diff...
April 2023 Product Update 🚀
Hi there 👋
How Vevo uses Codacy to replace legacy systems while guaranteeing code coverage
As the tech world keeps evolving, having legacy systems is a certainty, especially for organizations that have been around for decades. Long-lived...

Automate code
reviews on your commits and pull request

Group 13