You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we track code coverage targets using a coverage file in the repository root, which needs to be manually updated every time code coverage changes (both improvements and reductions). This issue aims to start a discussion around stopping to do that, and instead use codecov.io to track our coverage for us. We've been using it over at Firecracker for about a year now.
Pros:
No more manual tracking of coverage numbers in the repository
No more CI blocking if coverage is lowered by a PR (although realistically in the past we always just "overrode" those anyway by updating the file, so not sure if this will really be much of a change)
The text was updated successfully, but these errors were encountered:
Currently, we track code coverage targets using a coverage file in the repository root, which needs to be manually updated every time code coverage changes (both improvements and reductions). This issue aims to start a discussion around stopping to do that, and instead use codecov.io to track our coverage for us. We've been using it over at Firecracker for about a year now.
Pros:
Cons:
The text was updated successfully, but these errors were encountered: