Create Gitub Actions workflow to build, check and deploy to PyPI

[dvandyk]

• Uses the manylinux2014 docker image. I use the same for EOS. Can be changed later to e.g. manylinux2010 or even manylinux1?
• Builds for python3 only. Do we really need python2.x?
• Builds wheel for every commit, but only deploys to PyPI for tagged commits.
• Builds and deploys documentation for every commit. Should this step deploy only on tagged commits?

[dvandyk]

Hm, apparently the actions are only run once the workflow is committed to this repository. Can I get push access to the branch 'testing'?

[fredRos]

Hm, apparently the actions are only run once the workflow is committed to this repository. Can I get push access to the branch 'testing'?

I actually got the travis integration working again, see https://travis-ci.org/github/fredRos/pypmc/jobs/759802045 But we have to fix the doc deployment, also relates to the secrets etc. I would actually like docs to be deployed for every commit. So I'm not sure what the benefit of the github action is then.

We should only have one of the two services enabled

[fredRos]

@dvandyk I'm closing this PR for now to clean the house so there is no PR open before migrating the repo. Please open it again in the new home, then you can configure the secrets and everything. Should be much simpler for both of us

[dvandyk]

Sounds reasonable!