Skip to content

Commit

Permalink
fix(generators/app/templates): remove bash command blocks' inconsis…
Browse files Browse the repository at this point in the history
…tencies
  • Loading branch information
cueedee committed Oct 24, 2017
1 parent bad7935 commit 59d7124
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions generators/app/templates/@README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@
* [grunt](http://gruntjs.com/getting-started#installing-the-cli)

```bash
$ [sudo ]npm install -g grunt-cli
[sudo ]npm install -g grunt-cli
```

* [compass v1.0.0 or greater](http://thesassway.com/beginner/getting-started-with-sass-and-compass#install-sass-and-compass)

```bash
$ [sudo ]gem install compass
[sudo ]gem install compass
```


Expand All @@ -28,12 +28,12 @@
Clone this repository somewhere, switch to it, then:

```bash
$ git config commit.template ./.gitmessage
git config commit.template ./.gitmessage
# ... Set up any local tracking branches in addition to the default one. Depends on the branching model used, if any;
# ... Initialize your branching model tools, if need be ... ex: `git flow init -d`;
$ ( cd ./.git/hooks && ln -s ../../.git-hooks/git-hook-on-npm-lockfile-change.sh post-checkout )
$ ( cd ./.git/hooks && ln -s ../../.git-hooks/git-hook-on-npm-lockfile-change.sh post-merge )
$ npm run refresh
( cd ./.git/hooks && ln -s ../../.git-hooks/git-hook-on-npm-lockfile-change.sh post-checkout )
( cd ./.git/hooks && ln -s ../../.git-hooks/git-hook-on-npm-lockfile-change.sh post-merge )
npm run refresh
```

This will:
Expand Down Expand Up @@ -119,7 +119,7 @@ To make this work, *please* ensure that your commit messages adhere to the
to have the `commit.template` as referenced below will help you with [a detailed reminder](.gitmessage) of how to do this on every `git commit`.
```bash
$ git config commit.template ./.gitmessage
git config commit.template ./.gitmessage
```
Expand All @@ -131,19 +131,19 @@ the very least it should include:\]_
* Determine what your next [semver](https://docs.npmjs.com/getting-started/semantic-versioning#semver-for-publishers) `<version>` should be:
```bash
$ version="<version>"
version="<version>"
```
* Bump the package's `.version`, update the [CHANGELOG](./CHANGELOG.md), commit these, and tag the commit as `v<version>`:

```bash
$ npm run release
npm run release
```

* If all is well this new `version` **should** be identical to your intended `<version>`:

```bash
$ jq ".version == \"${version}\"" package.json
jq ".version == \"${version}\"" package.json
```

*If this is not the case*, then either your assumptions about what changed are wrong, or (at least) one of your commits did not adhere to the
Expand Down

0 comments on commit 59d7124

Please sign in to comment.