-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Move continuous integration from Travis CI to Github Actions #58
Conversation
Just runs flake8 and pytest to verify our builds. See issue: #51
added another push trigger just to test the workflow within the feature branch
…e have a working flake8 configuration
merge dev into feature branch
don't stop build due to flake8 errors. should be changed later once we have a working flake8 configuration
installation of requirements_ci.txt as part of the workflow
…e for newer ubuntu versions
…in numpy version used by Python3.6
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.
Looks great @IroNEDR, thanks for the work! ✨
@IroNEDR I have approved the PR, looks good to me. I will hold off on merging and deleting the feature branch for now, but next time if you would like me to proceed with the merge and with deleting the feature branch please let me know 🔧 |
@vc1492a no worries, good thing you didn't merge yet. I renamed the workflow file and added a test status badge to the readme to replace the old travis badge |
Our free travis CI credit ran out a long time ago. With this PR we move the our current CI Pipeline from travis to github actions.
With this new pipeline we test for Python versions 3.6 - 3.12. During the process some regressions in our unit tests on older Python versions were discovered such as using the
tuple
instead ofTuple
in the type annotations. These small fixes are included in this PR.An interesting read regarding costs etc.:
https://docs.github.com/en/actions/administering-github-actions/usage-limits-billing-and-administration
According to this, we fall under the free category.