Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CodeCov: add configuration #464

Merged
merged 1 commit into from
Apr 16, 2021
Merged

CodeCov: add configuration #464

merged 1 commit into from
Apr 16, 2021

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Mar 21, 2021

This commit:

  • Removes the configuration for the Coverall service which is no longer used.
  • Adds a configuration for the CodeCov service (which is used).
    This configuration:
    • Adds a threshold of a 1% difference before failing the build for project status checks (= total coverage for the whole project).
      Too often, due to some imprecision in how the code coverage is calculated, a difference of -0.12% (or similar) will be reported.
      That kind of difference is no a reason to fail the build and block merges as it is often incorrect anyhow. (how can a docs PR cause a negative code coverage diff ?)
    • Explicitly sets the path for which files we expect to be covered.
    • For patch status checks the threshold remains at 0% (which is the default), meaning that the code coverage is not allowed to go down for the lines touched in the patch.
    • Turns off in the inane PR comments. The status checks are sufficient, the huge comments on each PR do not add much value.

This commit:
* Removes the configuration for the Coverall service which is no longer used.
* Adds a configuration for the CodeCov service.
    This configuration:
    - Adds a threshold of a 1% difference before failing the build for project status checks (= total coverage for the whole project).
        Too often, due to some imprecision in how the code coverage is calculated, a difference of `-0.12%` (or similar) will be reported.
        That kind of difference is no a reason to fail the build and block merges as it is often incorrect anyhow. (how can a docs PR cause a negative code coverage diff ?)
    - Explicitly sets the path for which files we expect to be covered.
    - For patch status checks the threshold remains at 0% (which is the default), meaning that the code coverage is not allowed to go down for the lines touched in the patch.
    - Turns off in the inane PR comments. The status checks are sufficient, the huge comments on each PR do not add much value.
@schlessera schlessera merged commit 84a64e8 into master Apr 16, 2021
@schlessera schlessera deleted the feature/add-codecov-config branch April 16, 2021 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants