Thanks for adding this workflow, @andrew-s28! However, it doesn't seem to be triggered by Actions. Not sure why, I already renamed it from pypi-release.yaml to pypi.release.yml. Do you know what I should do to automatically have it checked by Actions?

Thanks for adding this workflow, @andrew-s28! However, it doesn't seem to be triggered by Actions. Not sure why, I already renamed it from pypi-release.yaml to pypi.release.yml. Do you know what I should do to automatically have it checked by Actions?

How you tried?
because the workflow is triggered just if the job upload-to-pypi is executed. This last job is executed just when there is a release. i.e., you need to release a version to check this job.

Thanks @VascoSch92, I didn't realise that the Action will only be triggered upon release. Before merging, I would want to check if it indeed passes all tests, as intended, though. So I now (temporarily?) added a check for every pull-request. But the test-pypi_release was skipped so not tested; do you know why?

Thanks @VascoSch92, I didn't realise that the Action will only be triggered upon release. Before merging, I would want to check if it indeed passes all tests, as intended, though. So I now (temporarily?) added a check for every pull-request. But the test-pypi_release was skipped so not tested; do you know why?

Thanks @VascoSch92, I didn't realise that the Action will only be triggered upon release. Before merging, I would want to check if it indeed passes all tests, as intended, though. So I now (temporarily?) added a check for every pull-request. But the test-pypi_release was skipped so not tested; do you know why?

Because the job upload-to-pypi is trigger just when if: github.event_name == 'release'. and the test-pypi_release need this job.

I think the beast way to test it is to delete needs: upload-to-pypi
In this way you can see if the job work and before merging you can re-add it to the workflow

Nice :-)