ci: change gitmessage and travis ci configuration

change gitmessage to have a better readability, with more information. change the travis ci configuration to run on all branches reverting the change made before, and the script run to use commitlint only when is on branch master. It is still separated on 2 lines to maintain the old behavior.
Wizcorp · Jul 1, 2018 · 972813e · 972813e
1 parent 6fb33af
commit 972813e
Show file tree

Hide file tree

Showing 3 changed files with 54 additions and 31 deletions.
diff --git a/.gitmessage b/.gitmessage
@@ -1,23 +1,51 @@
-# <type>(<scope>): <subject>
-# <BLANK LINE>
-# <body>
-# <BLANK LINE>
-# <footer>
-#
-# For easy commit you can execute
-# npm run commit
-#
-# Commit message Format from Angular Commit Message Convention
-# https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines
-#
-# Types:
-# Must be one of the following:
-#
-# feat: A new feature
-# fix: A bug fix
-# docs: Documentation only changes
-# style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
-# refactor: A code change that neither fixes a bug nor adds a feature
-# perf: A code change that improves performance
-# test: Adding missing or correcting existing tests
-# chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
+###
+# Commits must follow the Angular Commit Message Convention
+# https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines
+###
+
+###
+# Please put a title above this line. The title must follow
+# the following format:
+#
+#   <type>(<scope>): <subject>
+#
+# The scope should be the name of the npm package affected (as perceived by the
+# person reading the changelog generated from commit messages.
+#
+# The subject contains succinct description of the change.
+#
+# Valid types are:
+#
+#   - build: Changes that affect the build system or external dependencies
+#     (example scopes: gulp, broccoli, npm)
+#   - ci: Changes to our CI configuration files and scripts (example scopes:
+#     Travis, Circle, BrowserStack, SauceLabs)
+#   - docs: Documentation only changes
+#   - feat: A new feature
+#   - fix: A bug fix
+#   - perf: A code change that improves performance
+#   - refactor: A code change that neither fixes a bug nor adds a feature
+#   - style: Changes that do not affect the meaning of the code (white-space,
+#     formatting, missing semi-colons, etc)
+#   - test: Adding missing tests or correcting existing tests
+###
+
+
+###
+# Insert a body above this line  (optional)
+#
+# The body should include the motivation for the change and contrast this with
+# previous behavior.
+###
+
+
+###
+# Insert a footer above this line (optional)
+#
+# The footer should contain any information about Breaking Changes and is also
+# the place to reference GitHub
+# issues that this commit closes.
+#
+# Breaking Changes should start with the word BREAKING CHANGE: with a space or
+# two newlines. The rest of the  commit message is then used for this.
+###
diff --git a/.travis.yml b/.travis.yml
@@ -28,13 +28,8 @@ before_script: greenkeeper-lockfile-update
 after_script: greenkeeper-lockfile-upload
 
 script:
-  - travis_retry npm run test
-  - travis_retry npm run report:coverage
-  - commitlint --from=master
+  - if [ "$TRAVIS_BRANCH" = "master" ]; then commitlint --from=master; fi && travis_retry npm run test
+  - if [ "$TRAVIS_BRANCH" = "master" ]; then commitlint --from=master; fi && travis_retry npm run report:coverage
 
 after_success:
   - npm run travis-deploy-once "npm run semantic-release"
-
-branches:
-  only:
-    - master
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "megadata",
-  "version": "0.0.0-development",
+  "version": "1.1.4",
   "description": "Smart messaging for games",
   "main": "./lib/index.js",
   "types": "./lib/index.d.ts",