[CI] Update coverage tool to codecov for pre-merge

[yunchu]

Description

• Replaced coverage reporting tool from Codacy to Codecov for the pre-merge job in the workflow

Changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which refactors the code base)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• My code follows the pre-commit style and check guidelines of this project.
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• I have added a summary of my changes to the CHANGELOG (not for minor changes, docs and tests).

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@27a2c5f). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #885   +/-   ##
=======================================
  Coverage        ?   86.85%           
=======================================
  Files           ?      165           
  Lines           ?     6331           
  Branches        ?        0           
=======================================
  Hits            ?     5499           
  Misses          ?      832           
  Partials        ?        0           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[samet-akcay]

@yunchu, thanks for your PR. Is it possible to do this without setting it up from https://app.codecov.io/gh/openvinotoolkit?

[yunchu]

@yunchu, thanks for your PR. Is it possible to do this without setting it up from https://app.codecov.io/gh/openvinotoolkit?

@samet-akcay AFAIK, for the public repo, it doesn't need to register it and corresponding token is also not required.

[samet-akcay]

@yunchu, thanks for your PR. Is it possible to do this without setting it up from https://app.codecov.io/gh/openvinotoolkit?

@samet-akcay AFAIK, for the public repo, it doesn't need to register it and corresponding token is also not required.

hm, if this is the case, it's good news!

[samet-akcay]

Any idea about how to use codecov badge on the readme file? For codacy, there is this line on the readme

To get this, I assume we need to somehow connect to codecov's anomalib dashboard?

[yunchu]

um... it looks like to have signing up to the codecov.io
here is a guild for the badge and need to get into the "setting" menu but cannot see it without sign up to there.
https://docs.codecov.com/docs/status-badges

[samet-akcay]

Yeah, I think we need to add both anomalib and training extensions to codecov to get this. I can only see datumaro and mmdetection repos in codecov.

[yunchu]

how about just putting to the README.md? I will try here :)

[yunchu]

I guess the number of the coverage for the default branch should be reported to the codecov to show it correctly.

[ashwinvaidya17]

Thanks for adding this

[samet-akcay]

Thanks!