Move to GitHub actions

[drvinceknight]

No description provided.

[drvinceknight]

This is ready to be merged now.

All the work is really done in 3 commits:

• b940b39 (Subject: Add github actions and remove travis)
• dbe8a12 (Subject: Report coverage separately.)
• 5f08050 (Subject: Remove unnecessary badges.)

All the other commits are just testing that the CI reports failures correctly. If you look through the sequence of commits they all check that GitHub actions reports the required failure and then once the corresponding commit is reverted it passes. The red cross on a reverted commit is just because appveyor's PR build wasn't keeping up (and pulling my latest commit which usually had an expected failure) with my sequences of commits (as it was taking too long I didn't wait). You can check that all the builds behaved as expected by clicking on the red cross next to a commit.

For example, for 46bf990 (Subject: Revert "Add an error so docs do not build." ):

Appveyor

To remove appveyor I need to do more than just delete appveyor.yml, I have to delete the project on the appveyor site. As there are other PRs going I won't do that until this PR is in. Once it is (and we have CI for windows and ubuntu through GitHub actions) then I'll delete the project on the appveyor site and open a PR to remove the appveyor.yml.

Once this is in I'll also open a few more issues with other things we can do (for example adding py3.8 and an OSX run - I tried doing this briefly and small bugs appeared so we can just do it separately).

The README

You can view the README here: https://github.com/Axelrod-Python/Axelrod/blob/5f080503467c6c1158d2c54619445f8e3759e851/README.rst clicking on the CI badge takes you to the GitHub actions page.

@marcharper suggested we could have a 100% coverage sticker, but can we do that in a separate PR?

[marcharper]

Thanks for taking care of this!

[Nikoleta-v3]

Everything looks good to me as well!

Once this is in I'll also open a few more issues with other things we can do (for example adding py3.8 and an OSX run - I tried doing this briefly and small bugs appeared so we can just do it separately).

@marcharper suggested we could have a 100% coverage sticker, but can we do that in a separate PR?

We should just remember to open these issues 👍

[drvinceknight]

f4bd6ab's failure is expected it's essentially checking that it would have caught the bug that #1314 fixes.

[meatballs]

Nice piece of work!