chore: Migrate to github actions for CI

[abhiabhi94]

• add separate environment in tox for linters and docs.
• switch to codecov for coverage since coveralls doesn't play well with github-actions.

Thanks travis for their service till now.

closes actions/toolkit#223.

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (develop@a539232). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     actions/toolkit#228   +/-   ##
==========================================
  Coverage           ?   99.89%           
==========================================
  Files              ?       55           
  Lines              ?     1969           
  Branches           ?      158           
==========================================
  Hits               ?     1967           
  Misses             ?        1           
  Partials           ?        1           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a539232...e4623e7. Read the comment docs.

[abhiabhi94]

Hey @Radi85, you may have to set up the repository on codecov, although their bot is still commenting so i guess it may not be required.

I haven't added anything related to release as of now, please let me know your thoughts regarding the potential approaches as stated in #220 (comment). any new ideas are welcome.

[Radi85]

Hey @abhiabhi94, well done. Thanks a lot for your time.
I have updated the settings, removed travis things and so on. I also synchronised codecov with the repo.
I would like to add the release at least for testing pypi and the main one will be kept to manually for now. Can you please add the test pypi release to the CI?

[abhiabhi94]

I have updated the settings, removed travis things and so on. I also synchronised codecov with the repo.

Thank you 🎉 for the updates.

I would like to add the release at least for testing pypi and the main one will be kept to manually for now. Can you please add the test pypi release to the CI?

I have updated the patch to include the release workflow. The aim is to release to test PyPI servers when there is tag pushed on the master branch. This was what I could gather from our previous travis workflow. Please inform if this doesn't seem suffice for our use-case or anything else needs attention. Happy to make the changes.

You probably would have to setup the credentials on Github, in case you haven't done it yet. This guide could be helpful.

[abhiabhi94]

hey @Radi85, is their any other change that is required in this patch or is this now good to go?

[Radi85]

hey @Radi85, is their any other change that is required in this patch or is this now good to go?

So far I think we are good to go. Let's see how things go and later on we decide whether adding the main release or just keeping it manually.

@abhiabhi94 thanks for the good work.