Replies: 1 comment
-
Well, the point of using that codecov is because some awesome list we're willing to join requires public test coverage. So we still should adopt that. Even we say okay to merge the PR, which reduces the test coverage, it doesn't mean we should turn it off. I will create tasks to increase PipeCD test coverage and can say for sure that we want to increase that number (and make it green) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've confirmed this discussion, but I think Codecov affects a not good experience than good it. Of course, I know Codecov is good product, but, in fact, some pull requests are failed by Codecov's reporting, although PipeCD maintainer comments that it's ok to go, now. wdyt ?
Beta Was this translation helpful? Give feedback.
All reactions