Implement GitHub Actions for tests, releases

[josh-hadley]

• added GitHub Actions workflow to run tests (runs on push, pull_request, and manual trigger)
• added GitHub Actions workflow for creating release & publishing to PyPI (runs on tag push)
• implemented setuptools_scm versioning
• removed Travis and AppVeyor config files
• updated README

[coveralls]

Coverage decreased (-0.4%) to 87.532% when pulling dde3d9186939f1aef6a0b75df3807a9e6ea1514d on jh-actions into baa9560e886537d50f0583be010001a3d80d6d70 on master.

[benkiel]

@josh-hadley This is fantastic. Thank you!

[josh-hadley]

@josh-hadley This is fantastic. Thank you!

Sure thing Ben. You should be able to trigger a release/build/PyPI publish by pushing a tag to master with the desired version. I recommend testing with a pre-release tag first like 0.4.3a0 or some such, just in case something breaks.

Oh also, note: the Release action always sets the 'pre-release' tag on the GitHub release, even for a "final" release tag. This is kind of a safety valve. So after running it, if all looks good, go to the GitHub Release and un-tick the "This is a pre-release" checkbox on "final" releases.

I'll keep my eyes out for any issues with this and try to get on top of them as needed.

[benkiel]

Ah, I lived dangerously (well, I didn't see this) and pushed a non pre-release tag. It all worked, thank you so much for this.

[josh-hadley]

oh -- ha! awesome 😀

[benkiel]

To note, I made the release through GitHub, not via a tagged push.

[josh-hadley]

Ah -- OK that's what I figured -- the Action fails to create the release (because it's already created) but the rest of the workflow runs, so I think I'm gonna call it a day on this for now. Maybe revisit down the road, there are some other little tweaks that would be good (like only uploading coverage to Coveralls once...).

[benkiel]

@josh-hadley Yes, sorry, was being lazy and just did it through the web interface. Good to know it all works, thank you again.