Set up CI

[chris-pearce]

CI Tasks

When a PR is pushed to the Shell repo

• Passes all CSS linting rules (could use Gulp).
• Sass compiles (currently a Grunt command exists: grunt testShell, in the test/ folder).
• Versioning:
  • Grab the version from the .version file and apply it to the "version" object key in the package.json file.
  • Create a git tag: git tag -a vX -m "Version X" where "X" is the version number pulled from the .version file.

When a PR is merged to the master branch

• Run npm publish.
• Run git push origin [tagname].

Travis is a good option I think: https://travis-ci.org/.

[chris-pearce]

Really important now we're about to go to 1.0.0.

[chris-pearce]

Feedback from @williamtsoi1:

I'd suggest taking the 'version' workflow out of the PR, because for example:
1. master branch is at version 1.0.1
2. person A makes a fork/branch, does his work and bumps the version on his repo to v1.0.2
3. person B makes a fork/branch, does his work and bumps the version on his repo to v1.0.2
4. person B issues a PR
5. PR is merged, master branch is now at v1.0.2
6. person A issues a PR <- now the versioning is stuffed

[11:25] 
you'd probably want to bump the version AFTER every merged PR, rather than as part of the PR

[11:25] 
because there's no guarantee in relation to the "order of merging"```

[DaveOrDead]

This is worth having a read of in terms of auto publishing to npm: npm/npm#7042