Merge pull request #736 from watson-developer-cloud/semantic-release

This PR adds `semantic-release` integration to automate SDK releases. With this, the SDK will be released with successful `master` builds (assuming `semantic-release` determines there should be a release - see [here](https://github.com/semantic-release/commit-analyzer#release-rules)).

Also added in this PR is `commitlint` to ensure commit messages follow the proper format, since it's necessary for `semantic-release` to work properly. Here's an example of `commitlint` in action:

![bad_commit](https://user-images.githubusercontent.com/8710772/42065334-62a40aae-7b08-11e8-9c42-b9d9709aec4d.gif)

Author: germanattanasio

.github/CONTRIBUTING.md

@@ -8,10 +8,7 @@ or [Stack Overflow](http://stackoverflow.com/questions/ask?tags=ibm-watson).
 # Code
 
 * Our style guide is based on [Google's](https://google.github.io/styleguide/jsguide.html), most of it is automaticaly enforced (and can be automatically applied with `npm run autofix`)
-* commits should start with the service name and end with the issue #
-  ```
-  [concept-insights] Added functionality to list the graphs #135
-  ```
+* Commits should follow the [Angular commit message guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines). This is because our release tool uses this format for determining release versions and generating changelogs. To make this easier, we recommend using the [Commitizen CLI](https://github.com/commitizen/cz-cli) with the `cz-conventional-changelog` adapter.
 
 # Issues
 

.releaserc

@@ -0,0 +1,13 @@
+{
+  "branch": "master",
+  "publish": [
+    "@semantic-release/npm",
+    {
+      "path": "@semantic-release/github",
+      "assets": [
+        {"path": "dist/watson.js"},
+        {"path": "dist/watson.min.js"}
+      ]
+    }
+  ]
+}

.travis.yml

@@ -17,3 +17,9 @@ script:
 after_success:
 - npm run report-coverage
 - scripts/jsdoc/publish.sh
+deploy:
+- provider: script
+  skip_cleanup: true
+  script: npx travis-deploy-once "npx semantic-release"
+  on:
+    node: stable

README.md

@@ -5,6 +5,7 @@
 [![Slack](https://wdc-slack-inviter.mybluemix.net/badge.svg)](https://wdc-slack-inviter.mybluemix.net)
 [![npm-version](https://img.shields.io/npm/v/watson-developer-cloud.svg)](https://www.npmjs.com/package/watson-developer-cloud)
 [![npm-downloads](https://img.shields.io/npm/dm/watson-developer-cloud.svg)](https://www.npmjs.com/package/watson-developer-cloud)
+[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
 
 Node.js client library to use the Watson APIs.
 

RELEASE.md

@@ -1,8 +1,4 @@
 # Release process
 
-* Run the tests
-* Update the changelog
-* Run `npm version major`, `npm version minor`, or `npm version patch`
-  to increment the version in package.json and create a git commit and tag.
-* Run `git push --follow-tags` to push the commit and tag to github.
-* Run `npm publish` to publish the changes to npm.
+* Make a PR to `master`
+* The SDK will be released to npm and GitHub once the PR is merged and the build passes

commitlint.config.js

@@ -0,0 +1,10 @@
+module.exports = {
+  extends: ['@commitlint/config-conventional'],
+  rules: {
+    'subject-case': [
+      2,
+      'always',
+      ['lower-case', 'sentence-case']
+    ]
+  }
+};