Skip to content

Commit fe324f2

Browse files
committed
Corrected steps to publish a release
1 parent da0128e commit fe324f2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -510,7 +510,7 @@ Since 0.9.2, the process of publishing a new release of `cmd2` to [PyPi](https:/
510510
mostly automated. The manual steps are all git operations. Here's the checklist:
511511

512512
1. Make sure you're on the proper branch (almost always **master**)
513-
1. Make sure all the unit tests pass wih `invoke pypi-test` or `py.test`
513+
1. Make sure all the unit tests pass with `invoke pytest` or `py.test`
514514
1. Make sure `CHANGELOG.md` describes the version and has the correct release date
515515
1. Add a git tag representing the version number using ``invoke tag x.y.z``
516516
* Where x, y, and z are all small non-negative integers

0 commit comments

Comments
 (0)