-
|
Having followed the instructions on how to use this, I'm getting "Deployments" showing up in my repo. Besides the clutter, are misleading especially since there are a bunch of test deployments to test pypi created in setting up. Also deployments in github follow semantics of an environment with each deployment replacing a previous one. This isn't accurate for publishing to a repo. For now I'll disable the Github beta feature: I wanted to ask about them here, as this may be useful to future readers:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The If you drop the environment from the workflow, you'd have to allow any environment to publish, on the PyPI side, in the Trusted Publishing setup. You'd lose the ability to protect your publishing job with required reviews (a GH button click), though. Here's an example of what the deployments look like if you use unique/versioned URLs: https://github.com/cherrypy/cheroot/deployments/pypi |
Beta Was this translation helpful? Give feedback.
The
environment:setting in the job does that. Refer to GitHub's docs on cleaning them up. They could have different URLs with versions if you specify those.If you drop the environment from the workflow, you'd have to allow any environment to publish, on the PyPI side, in the Trusted Publishing setup. You'd lose the ability to protect your publishing job with required reviews (a GH button click), though.
Here's an example of what the deployments look like if you use unique/versioned URLs: https://github.com/cherrypy/cheroot/deployments/pypi