As described in issue #923, I migrated the Travis CI pipeline to GitHub Actions.
Some actions are required from your side before merging the pull request.
GitHub Actions and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to GitHub Actions.
In some cases Github actions is better than Travis similarly Travis CI has its own benefits.
How Has This Been Tested?
I tested the job steps in the forked(only steps are like checking out code, testing code)
Screenshots (In case of UI changes):
No UI changes done.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Migration of pipeline to Github Actions
Description
As described in issue #923, I migrated the Travis CI pipeline to GitHub Actions. Some actions are required from your side before merging the pull request.
Related Issue
https://github.com/scorelab/Bassa/issues/923
Motivation and Context
GitHub Actions and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to GitHub Actions. In some cases Github actions is better than Travis similarly Travis CI has its own benefits.
How Has This Been Tested?
I tested the job steps in the forked(only steps are like checking out code, testing code)
Screenshots (In case of UI changes):
No UI changes done.
Types of changes
Checklist: