We have an EBP bot on PyPI so that we can push out new releases via a single account instead of manually giving each team member push access to repositories. This lets us push with GitHub Actions.
To do this, we need to include a secret token along with our GitHub actions build. Currently we put this token in each repository (and probably create it per project as well).
An alternative option is that we could store a single token for executablebooks that could be re-used in any repository. That way, any repository has the ability to push to PyPI. To do that we need to add it here
To do
We have an EBP bot on PyPI so that we can push out new releases via a single account instead of manually giving each team member push access to repositories. This lets us push with GitHub Actions.
To do this, we need to include a secret token along with our GitHub actions build. Currently we put this token in each repository (and probably create it per project as well).
An alternative option is that we could store a single token for
executablebooksthat could be re-used in any repository. That way, any repository has the ability to push to PyPI. To do that we need to add it hereTo do
ebp-botshared access and documentation for publishing to PyPI & NPM #10