-
Notifications
You must be signed in to change notification settings - Fork 1
Enable CodeCov #768
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
Enable CodeCov #768
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
| with: | ||
| token: ${{ secrets.CODECOV_TOKEN }} | ||
| slug: PermanentOrg/sftp-service | ||
| fail_ci_if_error: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is something we might want to consider adding to our other codecov configs -- without it CI can still pass even if we don't successfully upload coverage to CodeCov
1419fad to
b67e78f
Compare
b67e78f to
a43390b
Compare
a43390b to
bd24340
Compare
bd24340 to
c63bc5f
Compare
c63bc5f to
755e7c9
Compare
Now that we're starting to write tests we should follow practices of our other repositories and use CodeCov. In the past we've run tests twice (once with coverage and once without) due to an upstream issue[1], however I don't think we need to do this since we don't use runInBand and also that issue may now be fixed. Issue #33 We need tests 1. kulshekhar/ts-jest#4193
This PR sets up CI to use codecov (and adds a ci version of the test command to run with coverage)
In the past this has sometimes resulted in a CI that won't fail if tests fail, due to an upstream bug -- I believe that isn't the case here, though once I open the PR and it works I'll add a temporary commit with a failing test to ensure CI fails.
Related to #33
This should be merged after #764