ci(semantic-release): implement semantic release flow (#1075)

* ci(semantic-release): add semantic release packages

* ci(semantic-release): add semantic release packages

* ci(semantic-release): update travis config

* ci(semantic-release): fix package.json

* ci: use node 10

* chore: update contributing guidelines

* chore: add commit script

* Update .travis.yml

* ci: update travis config

* ci: only deploy on master

* ci: well that didn't seem to do anything

.github/CONTRIBUTING.md

@@ -0,0 +1,13 @@
+## Pull Requests 
+
+Looks like you want to help out on vue-select.. awesome! Here's a few things to keep in mind when contributing.
+
+- Vue Select uses semantic release to automate the release process. This means that good commit
+ messages are critical. If you're unfamiliar with [conventional changelog](https://github.com
+ /ajoslin/conventional-changelog) you can run `yarn commit` to generate a commit message.
+- It's almost always better to ask before you jump into a PR if you want to add new functionality
+. It's not fun for anyone when you spend time on something that doesn't end up in the component. 
+- If your PR fixes or references an open issue, be sure to reference it in your message.
+- If you're adding new functionality, make sure your code has good test coverage.
+
+:tada: Thanks for contributing, and an even bigger thanks for reading these guidelines!