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
Implement GitHub Actions for linting and unit tests #2819
Conversation
…CI suite. Ony unit tests are run with this file.
… there is no reason to execute those commands in a CI environment.
…ub Actions for the former and codecov for the latter. Also minor refactoring of headings and some language errors.
Voight Kampff Integration Test Succeeded (Results) |
Awesome! Should the |
Good call, Åke. Will remove. |
… part of the CI process.
Voight Kampff Integration Test Failed (Results). |
Voight Kampff Integration Test Succeeded (Results) |
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.
All looks good and we are ready to roll!
Description
Build upon the work done in PR 2764 to replace Travis CI with GitHub Actions. Moved code coverage from coveralls to codecov due to some issues coveralls has with pytest and GitHub Actions.
How to test
You can see the results of the GitHub Actions workflow in draft PR 2817. The "build" and "coverage" badges in README.md were replaced with GitHub Actions and codecov badges.
Contributor license agreement signed?
CLA [Y]