Setup CI

[chris-pearce]

Look at Travis CI.

Things to look at:

• http://mclear.co.uk/2013/10/06/publishing-to-npm-on-git-commit-using-github-hooks-and-travis/
• https://robots.thoughtbot.com/configure-travis-ci-for-go

[chris-pearce]

Not sure if this is needed? Tests I can run:

• Sass is compiling
• Sass is linting

Also auto updating the git tagging (version numbering).

[chris-pearce]

Currently have to do all this manually:

• Update .version file
• Update version numbers in:
  • bower.json
  • package.json
• Update CHANGELOG.md
• Run npm publish
• Update Twitter account
• New git tag:
  • git tag -a vX -m "commit msg" [sha]
  • git push origin [tagname]

[chris-pearce]

@kllevin how is this looking?

[chris-pearce]

https://codeship.com/

[chris-pearce]

Be great to auto update Twitter for each commit :) https://zapier.com/zapbook/github/twitter/1662/tweet-from-github-commit/

[chris-pearce]

Found a grunt task to manage auto versioning update of package json files and creating new git tags: http://bob.yexley.net/creating-and-maintaining-your-own-bower-package/#gruntbump.

[chris-pearce]

Another addition maybe: https://github.com/katiefenn/parker.

[chris-pearce]

Another addition maybe: https://github.com/springload/css-reporter.