| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
Disable codecov annotations on PR.
So far they seem to be more annoying than useful.
We have some files that are not covered by unit tests
and these are just filled with "this line is not covered".
See https://docs.codecov.io/docs/codecovyml-reference
|
| |
|
|
|
| |
We are still getting nacks from codecov on PRs after the previous commit.
Try to add patch section to prevent failures.
|
| |
|
|
|
|
|
| |
Somehow informational:true is not enough to not produce errors.
We are constantly getting nacks on PRs like:
x codecov/patch — 59.2% of diff hit (target 65.3%)
Add back and relax target and treshold.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Informational mode should always produce "pass" result:
https://docs.codecov.io/docs/commit-status#informational
I can't get anything useful of these notifications.
E.g. now we have patches that add 1 line,
which gives 0% patch coverage, which results in a failure.
But we have some packages/commands not tested at all,
so we can't require contributors to make that covered.
For overall project coverage I also have not seen
any useful pass/fail results. The criteria highly depends
on the nature of the change. If we set the threshold too low,
we will get lots of effectively false failures. The current 50%
setting effectively means "never fail" anyway.
|
| | |
|
|
|
Merge 2 coverage sections.
|
