use PyPI upload workflow from OpenAstronomy

[zacharyburnett]

This PR changes the PyPI upload process to use the OpenAstronomy workflow instead of the STScI one. The workflow in this PR is configured to test the build with each pull request push, and then publish upon an official release.

Additionally, we can't use this workflow until we make a PyPI token (with write / upload permission to packages) for the STScI maintainer account. Currently, we use a username and password to PyPI; however, this method will be deprecated at some point in the future in favor of tokens.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

📢 Thoughts on this report? Let us know!.

[WilliamJamieson]

With my suggestions below,

stpipe/.github/workflows/ci.yml

Line 26 in 510e4a2

- linux: build-dist

can be removed as the workflow should be triggered by pull_requests, but not be uploaded to PyPi.

[WilliamJamieson]

I wonder why the publish workflow has not been triggered... Would a close/reopen work to trigger that?

[zacharyburnett]

I wonder why the publish workflow has not been triggered... Would a close/reopen work to trigger that?

found it, it was just a syntax error

[zacharyburnett]

unfortunately, it looks like GitHub categorizes the actions on the Actions tab by filename, so we can't rename the actual workflow files without creating a new duplicate category with the same name. If people see Publish to PyPI running on their pull request, they might panic and think it's actually publishing; thus I renamed the job to build, but am unable to rename publish-to-pypi.yml