[Fix #4673] Migrate EvalAI CI/CD Workflow to Github Actions
As a fix for Issue #4673 , his PR aims to :
- Completely migrate EvalAI's current CI/CD workflow from Travis CI to Github Actions.
- Setup CI checks for linting, migrations, and static type checks.
- Decommission .travis.yml and remove Travis-specific config/integration from the repository.
- Update documentation to reflect the CI migration : make changes in README.md and other files to reflect the changes made.
The github actions default variables to replace the travis CI variables are provided this link : https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 69.67%. Comparing base (
96968d6) to head (d677b49). Report is 1188 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #4685 +/- ##
==========================================
- Coverage 72.93% 69.67% -3.26%
==========================================
Files 83 21 -62
Lines 5368 3608 -1760
==========================================
- Hits 3915 2514 -1401
+ Misses 1453 1094 -359
see 73 files with indirect coverage changes
see 73 files with indirect coverage changes
Continue to review full report in Codecov by Sentry.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update ce48ed6...d677b49. Read the comment docs.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
Hi @RishabhJain2018 this PR is ready for review.
I've updated all the travis variables to github actions variables
-TRAVIS_BRANCH <->GITHUB_REF_NAME
-TRAVIS_PULL_REQUEST <-> checks to see if GITHUB_EVENT_NAME == "pull request" & so on.
-All the Travis CI checks are passed by Github actions.
-Package and Deploy is for main/master branch only, so it skips.
The docs have also been been updated to reflect Github Actions now instead of Travis CI. Let me know if any changes are to be made.