Originally posted September 2014 at https://charliegleason.com

Deploying To GitHub Pages With Gulp

Charlie Gleason
Jan 20, 2017 · 5 min read

The older I get, the more I realise that I do not like doing things more than once.

When I first starting making the Internets, I would spend a massive amount of cognitive energy transferring things via FTP; dragging files to Transmit, hoping I hadn’t inadvertently overwritten something super important. It was dark, people. It was a dark time.

No, FTP. No.

Fortunately, this is no longer the case. You don’t have to live like this. We don’t have to live like this.

I’ve been using GitHub Pages to deploy static sites for a while now. It’s quick, easy, and pretty painless. You can easily get a static site set up and hosted in no time, and it’s free. Win win! I actually used it for the client side of Tweetflight.

If you’ve run through my Harp, Gulp and Browsersync tutorial, you can use that as the basis for deployment. If you haven’t, all you need is a repo and a directory to deploy. Easy as.

First up, you’ll want to install gulp and gulp-gh-pages, which will handle the deployment.

So, you’ll need a package.json file, to use manage the required Node packages.

npm init

If you don’t have Node.js, you can install it here.

It will ask you some questions about your project, and it’s pretty friendly. Good for you, NPM. Good. For. You.

Right. To celebrate, let’s enjoy a photo of a cat in the snow.

Yes. You are the best cat.

So good.

Add Gulp, which powers this glorious, gorgeous beast.

npm install gulp --save-dev

Then you’ll need to add gulp-gh-pages.

npm install gulp-gh-pages --save-dev

Now, in your gulpfile.js, add the following:

var gulp        = require('gulp');
var deploy = require('gulp-gh-pages');

* Push build to gh-pages
gulp.task('deploy', function () {
return gulp.src("./dist/**/*")

We’re defining a task, called deploy. You could get gulp to run a build task here, if you needed to, prior to deploying it. To do so, just update ‘deploy’, function() { to ‘deploy, [‘build’], function () { (or whatever the name of you gulp build task is) and gulp will take care of it. It’s one of the many reasons gulp is wild.

I used gulp four times in that paragraph. Calm down, Charlie.

/dist is the directory we’re deploying, and /**/* means it will deploy recursively. All files and directories inside of /dist will be included.

So, given that you’re deploying to GitHub, you’re going to need to have your site in a repository. You can see an example I set up at testing-gulp-gh-pages. If you don’t already have your site on GitHub, you should anyway. It’s awesome, and means you’ll be using proper version control for your site. Which is a huge piece of mind. Which you obviously deserve.

You’ll want to avoid pushing your whole /node_modules directory on GitHub, as it’s being managed by your package.json file. To stop this happening, make a file called .gitignore. That’s essentially a space where you can list files you don’t want to end up in source control, each on a new line.

Just make sure node_modules is listed:


That way, when you push to GitHub, you won’t accidentally push all of your sites Node depedencies.

If you don’t want to commit your /dist, or the folder that is holding your built site, you can add that too:


It really depends on how you’re managing your folder structure. There’s no wrong way, but it’s worth noting that if your repo is public you should avoid putting any fancy paid fonts or similar in there.

In that case you’re likely better hosting them remotely with S3 or Rackspace. I use Rackspace, personally.

If you want to use a custom domain for your GitHub hosted site, you’ll need to do two things first.

  1. Make a text-based CNAME file that will end up in the root of the directory you’re deploying. For example, /dist/CNAME. All it needs inside is the url you want to point to your new site. For me, it’s charliegleason.com.
  2. Update your DNS records. GitHub has a pretty good walkthrough of how to do this.

When you’re ready to deploy, the folder you’re pushing to GitHub should have CNAME in the root. As long as that’s in there, you’re golden.

One thing I should also mention—people have flagged that because their website was hosted from my_username.github.io, their custom domain wasn’t working. Using a repository name other than my_username seemed to fix things. Just an FYI. (Thanks Nikolas!)

And then you’re all set.

When you’re ready to deploy, push the latest changes to your repo to GitHub.

git add . # Add any untracked files
git commit -va # Commit the changes
git push # Push it to GitHub

You’ll also need to make sure you have a gh-pages branch, if you don’t already. (Be careful when using git rm -rf ., too!)

git checkout --orphan gh-pages
git rm -rf .
touch README.md
git add README.md
git commit -m "Init gh-pages"
git push --set-upstream origin gh-pages
git checkout master

So, now you just need to run your deploy task.

gulp deploy

And voila. You can visit your fancy new site at your-username.github.io/your-reponame, or (if the DNS has propogated) at the custom domain you set up.

You can see one I prepared earlier, which is using the testing-gulp-gh-pages repo.

Yes, Github Pages. Yes.

You’re great. Good for you. If you have any problems, I can probably help. Just email me.


Tutorials and thoughts on front end development