You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: {{cookiecutter.project_name}}/docs/template_usage.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,8 @@ There you can see the execution history, logs, and (re-)trigger workflows manual
147
147
148
148
## Automating the PyPI release using GitHub actions
149
149
150
-
Tags adhering to `"*.*.*"` that are pushed to the `main` branch will trigger the release Github workflow that automatically builds and uploads the Python package to [PyPI][].
150
+
Releases created via the [Github releases UI][github-releases]
151
+
will trigger the release Github workflow that automatically builds and uploads the Python package to [PyPI][].
151
152
152
153
For this to work, you'll need to setup GitHub as a [trusted publisher][] on PyPI.
153
154
To set this up, login to [PyPI][], and proceed depending on whether you already have your project on there or not:
@@ -159,6 +160,10 @@ The "Workflow name" needs to bet set to `release.yaml`.
159
160
Set "Environment name" to “pypi” to match `environment: pypi` in `.github/workflows/release.yaml`.
160
161
For more details, please refer to the official [PyPI guide for setting up trusted publishing][trusted publisher].
161
162
163
+
If you added a new pending publisher to set up your project,
164
+
the project will be published only once you release your package for the first time (see above).
0 commit comments