From aeca318736fcedb22130a38827ed2c7c705aa2d3 Mon Sep 17 00:00:00 2001
From: Akela Drissner-Schmid <32450038+akelad@users.noreply.github.com>
Date: Thu, 4 Oct 2018 11:29:21 +0200
Subject: [PATCH] update pushing tags command in readme

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index eb63b447716c..8340ce8b6d5c 100644
--- a/README.md
+++ b/README.md
@@ -204,7 +204,7 @@ Releasing a new version is quite simple, as the packages are build and distribut
 4. commit all the above changes and tag a new release, e.g. using 
     ```
     git tag -f 0.7.0 -m "Some helpful line describing the release"
-    git push origin master --tags
+    git push origin 0.7.0
     ```
     travis will build this tag and push a package to [pypi](https://pypi.python.org/pypi/rasa_nlu)
 5. only if it is a **major release**, a new branch should be created pointing to the same commit as the tag to allow for future minor patches, e.g.