The first time you generate your site it will take about 10 minutes for it to show up. Subsequent builds take only seconds from the time you push the changes to your GitHub repository.
However, depending on how your have your domain configured, there may be extra time for the CDN cache to break.
Note: using a subdomain, such as yourproject.github.io is the recommended domain setup, but does mean page builds take longer to show up since it has the benefit of using the GitHub CDN.
it takes ages sometimes if you use custom, how much of a benifit is the cdn?
@SuperUberDuper the CDN will always update when you push new files. If you want to test it (or break a cache) you can append a query string like
myfile.jpg?ver=123and every time you update the string the cache will bust, and you can verify that the CDN is updating.@SuperUberDuper also, if you are not seeing your files update, another explanation could be that your build is broken. Did you receive an email from GitHub Pages saying your build is failing? Configuring Travis CI on your repo is a great way to track failing builds as well.
@JoelGlovier Post the cache-buster as an answer and I'll upvote :) . Worked like a charm!
How long does the CDN cache for?