If your GitHub Enterprise Pages code contains Markdown errors, your GitHub Enterprise Pages site will not be built.
If your GitHub Enterprise Pages site fails to build because of invalid Markdown, you'll receive an email that looks like this:
Subject: Page build failed
The page build failed with the following error:
The file `example.md` contains markdown errors.
You will only receive an email if outbound email support is enabled on your Enterprise instance. For more information, contact your site administrator.
Troubleshooting Markdown errors
We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to your GitHub Enterprise instance.
The Maruku Markdown interpreter causes many builds to fail on invalid Markdown or HTML. If you're using Maruku, we highly recommend that you switch to a new Markdown interpreter.
Make sure the file mentioned in the email uses valid Markdown syntax. See Getting started with writing and formatting on GitHub for more help or the Daring Fireball Markdown guide for a more complete guide to Markdown syntax.
Once you've fixed any Markdown errors, you will need to commit your changes and push to your GitHub Enterprise Pages repository again to trigger another build on the server.
