Look at using GitHub Actions for CI

[cooperlees]

What's the problem this feature will solve? GitHub actions is generally available now and is a very strong CI option. Documentation: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/about-github-actions Example Project: https://github.com/pypa/bandersnatch/tree/master/.github/workflows

Describe the solution you'd like

• Add in CI to run on GitHub actions and reach 100% parity to what we have today
• Evaluate further possibilities with it's event integration with GitHub itself.
  • E.g. Bots

[di]

Is there an advantage here vs. Travis?

[pradyunsg]

It's significantly faster AFAICT. For pip's linting CI job:

GitHub Actions: 1m 28s Travis CI: 2m 11s

[jamadden]

Could the speed just be a result of newness and under-utilization? As more projects adopt it, that advantage could level out or disappear.

[di]

Would be nice to also be able to run our tests in the same Docker images we use for prod.