Set up travis to automatically deploy to gh-pages when master is pushed about built-with-cycle HOT 7 OPEN

I can take this up!

from built-with-cycle.

Actually @Widdershin I was thinking why can't we make master the gh-pages source so that we don't have to maintain another branch separately for deployment. We can change the source in settings of this repo.

from built-with-cycle.

If it makes it significantly easier to get this issue done I have no qualms with that :)

from built-with-cycle.

Currently what do we do? We trigger a build script and then push to branch gh-pages?

from built-with-cycle.

BTW would need some admin access to this repo etc. for this task, I suppose.

from built-with-cycle.

I don't know if this is what you need, but I use it in my project for single command deploys. This is my setup:

"homepage": <gh-page-address>
...
"gh-pages": "^0.12.0",
....
"predeploy": "npm run test && npm run build",
"deploy": "gh-pages -d build",
...

from built-with-cycle.

Found this useful tutorial: https://github.com/voorhoede/front-end-tooling-recipes/blob/master/travis-deploy-to-gh-pages/README.md

Currently setting this up for my personal project

from built-with-cycle.