actions/pypi-publish
1
0
Fork 0
mirror of https://github.com/pypa/gh-action-pypi-publish.git synced 2024-11-09 10:23:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Test PyPI -> TestPyPI in README

Browse source 
PR #13 by @hugovk

Ref: https://github.com/pypa/packaging.python.org/pull/647#discussion_r326001958
This commit is contained in:
Sviatoslav Sydorenko 2019-09-19 11:16:02 +03:00 committed by GitHub
commit 9cebe9a0ed
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -58,7 +58,7 @@ For best results, figure out what kind of workflow fits your
project's specific needs. project's specific needs.
For example, you could implement a parallel workflow that For example, you could implement a parallel workflow that
pushes every commit to Test PyPI or your own index server, pushes every commit to TestPyPI or your own index server,
like `devpi`. For this, you'd need to (1) specify a custom like `devpi`. For this, you'd need to (1) specify a custom
`repository_url` value and (2) generate a unique version `repository_url` value and (2) generate a unique version
number for each upload so that they'd not create a conflict. number for each upload so that they'd not create a conflict.
@ -71,7 +71,7 @@ You'll need to create another token for a separate host and then
The action invocation in this case would look like: The action invocation in this case would look like:
```yml ```yml
- name: Publish package to Test PyPI - name: Publish package to TestPyPI
uses: pypa/gh-action-pypi-publish@master uses: pypa/gh-action-pypi-publish@master
with: with:
user: __token__ user: __token__