From 9afc4e6e47e58f2d0b1f35226595b68c416c0f8e Mon Sep 17 00:00:00 2001 From: Arnaud Dezandee Date: Fri, 15 Jan 2016 13:29:59 +0100 Subject: [PATCH] docs(how): npm script tweaks --- HOW.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/HOW.md b/HOW.md index 4914f4d..7d036d6 100644 --- a/HOW.md +++ b/HOW.md @@ -36,14 +36,14 @@ This is what `apm publish` really do: In the background, Atom registry will download a tar ball of your project from git based on this tag. It will then try to read the package.json to determine the real version you wish to release. -**And here is the catch**, semantically released package doesn't have a "git saved" `package.version`, that's the whole point ! +**And here is the catch**, semantically released package doesn't have a "git saved" `package.version`. So here is the NPM scripts I'm using to make it work: ```json "scripts": { - "git:push": "git commit -am \"Prepare v$npm_package_version release [ci skip]\"", - "postgit:push": "git push", + "pregit:push": "git commit -am \"Prepare $npm_package_version release\"", + "git:push": "git push", "apm:publish": "apm publish -t v$npm_package_version", "semantic-release": "semantic-release pre && npm run git:push && semantic-release post && npm run apm:publish" },