If your GitHub Enterprise Pages repository contains a post with an invalid date, your GitHub Enterprise Pages site will not be built.

If your GitHub Enterprise Pages site fails to build because of a post with an invalid date, you'll get an email that looks like this:

Subject: Page build failed

The page build failed with the following error:

"The post `2012-02-30-time-is-an-illusion.md` does not have a valid date."

You will only receive an email if email support is enabled on your Enterprise instance. For more information, contact your site administrator.

Troubleshooting post date errors

We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to GitHub Enterprise.

  • Make sure you're using proper date formatting for filenames with dates. Dates must be formatted as YYYY-MM-DD HH:MM:SS for UTC, and must be actual calendar dates.
  • If you specify a date format in your _config.yml file, make sure you format it correctly. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT. For example: 2014-04-18 11:30:00 +0800.

Once you've fixed all post date errors, you will need to commit your changes and push to your GitHub Enterprise Pages repository again to trigger another build on the server.