Fix automatic release deployment

[dmtucker]

Resolve #104

This will not work until the project has repository secrets for PYPI_USERNAME and PYPI_PASSWORD:
https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository

I don't have permission to do that, so @dbader will have to do it.

[dbader]

@dmtucker Since you're a maintainer on the PyPI project (https://pypi.org/project/pytest-mypy/) as far as I know you should be able to set up CI deploys through that. (Personally, I'm not a fan of putting PyPI credentials on CI for security reasons.)

[dmtucker]

@dbader It's a lack of permissions on the GitHub side (I don't have access to the Settings tab for the repo).

Personally, I'm not a fan of putting PyPI credentials on CI for security reasons.

We can leave it manual if you'd prefer... FWIW, PyPI now offers per-project tokens that can be revoked on-demand. That's what Travis has been using so far (encrypted there, of course).

[dmtucker]

@dbader Would you mind making me an admin on this GitHub repo? Auto-deploy through Travis no longer works, and I can't set it up via GitHub Actions without admin.

[dbader]

@dmtucker Happy to make you an admin -- I don't think that's possible on a personal GitHub account (which this repo is on). What I could do is move this repo over to the github.com/realpython org account and then add you as a repo admin. Or do you know if there's a way to accomplish this with an individual account? (All I see is the option to add collaborators)

[dmtucker]

@dbader Interesting, I didn't realize that, but the docs seems to confirm it:

Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.

Moving to realpython works for me 👍

[dbader]

@dmtucker Done, I've migrated the repo to the @realpython org and gave you admin access 👍

[dmtucker]

Right on, thank you!