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
@kellrott: Server-side this already seems to be set up for Coveralls. However, when migrating our services and tools to GitHub Actions from Travis CI, we had a hard time getting Coveralls to work and migrated our services to Codecov instead. I could try again to make it work with Coveralls if you like (it's a little while ago) - but otherwise Codecov has worked really nice for us.
In that case, you would have to set this up on the Codecov server though, @kellrott, and set a repository secret. And then replace the last task in the CI workflow in the 0.5.0 release branch with the following two (you may of course need to change the name of the secret if you did not use CODECOV_TOKEN):
- name: Run unit testsrun: | coverage run --source tes -m pytest -W ignore::DeprecationWarning coverage xml
- name: Submit coverageuses: codecov/codecov-action@v3with:
token: ${{ secrets.CODECOV_TOKEN }}files: ./coverage.xmlfail_ci_if_error: trueverbose: true
Either way, please let me know.
The text was updated successfully, but these errors were encountered:
@kellrott: Server-side this already seems to be set up for Coveralls. However, when migrating our services and tools to GitHub Actions from Travis CI, we had a hard time getting Coveralls to work and migrated our services to Codecov instead. I could try again to make it work with Coveralls if you like (it's a little while ago) - but otherwise Codecov has worked really nice for us.
In that case, you would have to set this up on the Codecov server though, @kellrott, and set a repository secret. And then replace the last task in the CI workflow in the
0.5.0
release branch with the following two (you may of course need to change the name of the secret if you did not useCODECOV_TOKEN
):Either way, please let me know.
The text was updated successfully, but these errors were encountered: