deploy.sh

#!/bin/bash
if [ "$TRAVIS_BRANCH" == "develop" ]; then
	set -e # exit with nonzero exit code if anything fails

	# clear and re-create the out directory
	rm -rf site/build || exit 0;
	mkdir -p site/build;

	npm install
	# run our compile script, discussed above
	grunt docs:build

	# go to the out directory and create a *new* Git repo
	cd site/build
	git init

	# inside this git repo we'll pretend to be a new user
	git config user.name "Andrew Turner"
	git config user.email "aturner@esri.com"

	# The first and only commit to this new Git repo contains all the
	# files present with the commit message "Deploy to GitHub Pages".
	git add .
	git commit -m "Deploy to GitHub Pages"

	# Force push from the current repo's master branch to the remote
	# repo's gh-pages branch. (All previous history on the gh-pages branch
	# will be lost, since we are overwriting it.) We redirect any output to
	# /dev/null to hide any sensitive credential data that might otherwise be exposed.
	git push --force --quiet "https://${GH_TOKEN}@${GH_REF}" master:gh-pages > /dev/null 2>&1
fi