Change CI from Travis to GitHub Actions
athul opened this issue · comments
I think it should be more apt to change the CI system to GitHub Actions itself than Travis. The current project itself is a GH action and it's ironic that we use Travis for Testing 🤣 .
Since Travis only does is installing python and it's requirements and running unittest, it should be fairly easy to port to GH actions. Refer travis.yml for details
Hi, yea it is kind of ironic, but say for instance if GH Actions went down or Travis did, we could tell them apart when someone reports their workflow is failing. Just a thought.. :)
Oh wait, I'm sorry for confusing this. I meant the tests for waka-readme repo. Those are done with Travis and we need to change that to GH actions
Yes, I understand.
The probability of both the CI providers going down together is less than one going down, right.. so we can be sure that our latest commit (passes test in Travis CI and) did not cause some issue - in the scenario where GH Actions goes down (which would disrupt the WakaTime workflow for users).
But hey, I'm totally okay with having GH actions for testing, if that's what you want.