Skip to content

Commit

Permalink
Corrected steps to publish a release
Browse files Browse the repository at this point in the history
  • Loading branch information
kmvanbrunt committed Jan 9, 2019
1 parent da0128e commit fe324f2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -510,7 +510,7 @@ Since 0.9.2, the process of publishing a new release of `cmd2` to [PyPi](https:/
mostly automated. The manual steps are all git operations. Here's the checklist:

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

0 comments on commit fe324f2

Please sign in to comment.