From 015719f9e03287090fac149683e21e4ddf3010c0 Mon Sep 17 00:00:00 2001 From: Antonio Date: Mon, 9 Oct 2017 18:12:33 +0100 Subject: [PATCH] Update README.rst --- README.rst | 28 +++++++++++++--------------- 1 file changed, 13 insertions(+), 15 deletions(-) diff --git a/README.rst b/README.rst index c4d7df0..6679b19 100644 --- a/README.rst +++ b/README.rst @@ -447,23 +447,21 @@ For example, if you want to tag and version a previous commit, do the following: .. code-block:: bash - # Update version.py if needed - - # Check the tag history: - git tag - - # Check the commit log and copy the commit reference: - git log --pretty=oneline + # Update version.py if needed + # Check the tag history: + git tag + + # Check the commit log and copy the commit reference: + git log --pretty=oneline - # Create a tag, give it a version, internal message and point it to the commit you want to tag: - git tag -a v0.1 -m "code freeze for draft 1, 23 June 2017" 7c3c7b76e4e3b47016b4f899c3aa093a44c5e053 + # Create a tag, give it a version, internal message and point it to the commit you want to tag: + git tag -a v0.1 -m "code freeze for draft 1, 23 June 2017" 7c3c7b76e4e3b47016b4f899c3aa093a44c5e053 - # Push the tag - # By default, the git push command does not transfer tags to remote servers, so run: - git push origin v0.1 - - # You'll then need to click around in the GitHub repository to formally - publish the release. + # Push the tag + # By default, the git push command does not transfer tags to remote servers, so run: + git push origin v0.1 + + # You'll then need to click around in the GitHub repository to formally publish the release. -----