Move more Travis jobs to GitHub Actions

[bhrutledge]

Closes #650.

Changes

• Add release job based on jaraco/skeleton
• Remove .travis.yml
• Update docs

TODO

• Update "Required" checks

[bhrutledge]

Looks like the Travis check is still "Required", but test/3.9, types, and docs are not. Can one of the @pypa/twine-maintainers fix that (and clear the "Expected" status on "Travis CI")?

[jaraco]

Looks like the Travis check is still "Required", but test/3.9, types, and docs are not. Can one of the @pypa/twine-maintainers fix that (and clear the "Expected" status on "Travis CI")?

I've never configured Travis except through the .yml file and uploading encrypted secrets. If some checks are required and others not, I'm not sure where that's configured.

I scrolled around the Travis and Github settings and don't see anything about configuring which checks are required or not. I also searched the Internet, but didn't find anything relevant. It's possible I don't have access either. Does anyone else know what steps are required?

[bhrutledge]

I scrolled around the Travis and Github settings and don't see anything about configuring which checks are required or not. Does anyone else know what steps are required?

@di Any thoughts? Is this possibly at the organization level?

[di]

It's configured via the branch protection rules:

I've configured test/3.9, types, and docs to be required.

[bhrutledge]

Thanks, @di! Travis is still showing up as required on this PR. Assuming you disabled it, I'm going to close and reopen this to see if it's all set.

[bhrutledge]

Hm. Doesn't look like it.

[di]

Sorry, I missed that. Done.

[jaraco]

It's configured via the branch protection rules:

Aha! Thanks for that tip.

I see that the default behavior is not to have any rules, so no checks are required. I'll probably not enable this feature on my other repos, just because of the toil it would entail to set up and maintain.