Skip to content

Commit 20b5e04

Browse files
authored
Merge pull request #1961 from soxofaan/issue1935-publish-topypi
Rename publish-to-test-pypi.yml to publish-to-pypi.yml #1935
2 parents d593d4a + 5e9c85e commit 20b5e04

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,13 +87,13 @@ Creating a workflow definition
8787
GitHub CI/CD workflows are declared in YAML files stored in the
8888
``.github/workflows/`` directory of your repository.
8989

90-
Let's create a ``.github/workflows/publish-to-test-pypi.yml``
90+
Let's create a ``.github/workflows/publish-to-pypi.yml``
9191
file.
9292

9393
Start it with a meaningful name and define the event that
9494
should make GitHub run this workflow:
9595

96-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
96+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
9797
:language: yaml
9898
:end-before: jobs:
9999

@@ -107,7 +107,7 @@ build the distribution packages.
107107
First, we'll define the job for building the dist packages of
108108
your project and storing them for later use:
109109

110-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
110+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
111111
:language: yaml
112112
:start-at: jobs:
113113
:end-before: Install pypa/build
@@ -119,7 +119,7 @@ And now we can build the dists from source and store them.
119119
In this example, we'll use the ``build`` package.
120120
So add this to the steps list:
121121

122-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
122+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
123123
:language: yaml
124124
:start-at: Install pypa/build
125125
:end-before: publish-to-pypi
@@ -136,7 +136,7 @@ UI nicely. Additionally, it allows acquiring an OpenID Connect token
136136
that the ``pypi-publish`` actions needs to implement secretless
137137
Trusted Publishing to PyPI.
138138

139-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
139+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
140140
:language: yaml
141141
:start-after: path: dist/
142142
:end-before: steps:
@@ -149,7 +149,7 @@ Publishing the distribution to PyPI
149149

150150
Finally, add the following steps at the end:
151151

152-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
152+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
153153
:language: yaml
154154
:start-after: id-token: write
155155
:end-before: publish-to-testpypi:
@@ -175,7 +175,7 @@ Now, repeat these steps and create another job for
175175
publishing to the TestPyPI package index under the ``jobs``
176176
section:
177177

178-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
178+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
179179
:language: yaml
180180
:start-at: publish-to-testpypi
181181

@@ -191,7 +191,7 @@ This paragraph showcases the whole workflow after following the above guide.
191191

192192
.. collapse:: Click here to display the entire GitHub Actions CI/CD workflow definition
193193

194-
.. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
194+
.. literalinclude:: github-actions-ci-cd-sample/publish-to-pypi.yml
195195
:language: yaml
196196

197197
That's all, folks!

0 commit comments

Comments
 (0)