-
Notifications
You must be signed in to change notification settings - Fork 2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You sir, are a legend. Thanks for getting this started!
check: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- uses: actions/checkout@v2 | |
- uses: actions/checkout@v3 |
I'll update post merge
steps: | ||
- uses: actions/checkout@v2 | ||
- name: Set up Python 3.10 | ||
uses: actions/setup-python@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uses: actions/setup-python@v2 | |
uses: actions/setup-python@v3 |
env: | ||
TWINE_USERNAME: '__token__' | ||
TWINE_PASSWORD: ${{ secrets.TWINE_PASSWORD }} | ||
run: python setup.py sdist bdist_wheel && twine upload --skip-existing dist/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should prob move this to the new "build" hotness
🎉 Happy for you to update everything of course, my expedient template is definitely aging. It'd also be good to add |
I've set this up for automatic releases; you'll just need to issue a PyPI token and set it as the
TWINE_PASSWORD
repo secret.The only trick there is that (until pypi/warehouse#6378) for the first release, you'll need to use a full-user-scoped token, and then once the package exists you can replace that with a single-package-scoped release-only token. The commands in
.github/workflows/ci.yml
should also be obvious if you want to run the first one locally instead.