Descriptive error messages for failed GitHub Pages builds

Image of Ben Balter

It’s tough to be the bearer of bad news. Fortunately, today we’re making it a bit easier to quickly publish beautiful pages for you and your projects.

When you push a change to your GitHub Pages site — whether via Git command line, one of the desktop apps, or — we email you if for any reason we can’t build your site.

Starting today, you’ll also get a descriptive, human-readable error message for any failed build so that you can more easily troubleshoot what went wrong:

example failed build email

We’ve started by supporting the most common error messages seen on GitHub Pages, and will continue to roll out support for additional errors in the coming weeks.

For more information on troubled builds, see the Jekyll troubleshooting guide or contact GitHub Support. Happy publishing!

Join us at GitHub Universe

Our largest product and community conference is returning to the Palace of Fine Arts in San Francisco, November 13-14. Hear what's next for the GitHub platform, find inspiration for your next project, and connect with developers who are changing the world.

Get tickets

GitHub Actions now supports CI/CD

GitHub Actions makes it easier to automate how you build, test, and deploy your projects on any platform, including Linux, macOS, and Windows. Try out the beta before GitHub Actions is generally available on November 13.

Sign up for the beta