Migrate to GitHub Actions.

[jezdez]

Travis CI has a new pricing model which places limits on open source.

• https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
• https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works

Many projects are moving to GitHub Actions instead, including Jazzband projects:

• https://github.com/orgs/jazzband/projects/1
• Should we disable travis? help#206

This is based on jazzband/contextlib2#26.

No more mention of Travis CI in the codebase:

$ git grep -i travis
$

TODO:

• @jezdez to add JAZZBAND_RELEASE_KEY to the repo secrets.

[codecov]

Codecov Report

Merging #246 (b2847a7) into master (4d8cc6b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   80.10%   80.10%           
=======================================
  Files          27       27           
  Lines        1659     1659           
  Branches      191      191           
=======================================
  Hits         1329     1329           
  Misses        227      227           
  Partials      103      103           

---

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 4d8cc6b...bcb6866. Read the comment docs.

[WhyNotHugo]

I was unaware of the Travis plan changes. Thanks for sharing the details behind this.

Can we also push the packages to GH releases? (kinda like this)

[WhyNotHugo]

LGTM.

[jezdez]

I was unaware of the Travis plan changes. Thanks for sharing the details behind this.

Can we also push the packages to GH releases? (kinda like this)

Woops, I missed this comment, let me check how this could work in combination with the PyPA GitHub action we're using to publish the release to the Jazzband package index. I'll open a ticket.

[aleksihakli]

LGTM :)