If your GitHub Enterprise Pages code contains an unrecognized Liquid tag, your GitHub Enterprise Pages site will not be built.
If your GitHub Enterprise Pages site fails to build because of an unrecognized Liquid tag, you'll get an email that looks like this:
Subject: Page build failed
The page build failed with the following error:
The tag `fake_tag` in `index.html` is not a recognized Liquid tag.
You will only receive an email if email support is enabled on your Enterprise instance. For more information, contact your site administrator.
Troubleshooting unrecognized tag errors
We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to your GitHub Enterprise instance.
- Check the tags in the referenced file. They should match those in Jekyll's default variables. Make sure there are no typos in your tag names.
Check plugin output for unrecognized tags
Plugins are a common source of unrecognized tags. Since GitHub Enterprise doesn't support most plugins, a common workaround is to build locally and include the results in the Pages repository. However, this workaround can sometimes lead to tags that are not in Jekyll's default variables being included, which the build server cannot parse. For a list of supported plugins, see Using Jekyll Plugins with GitHub Enterprise Pages.
Once you've fixed any tag errors, you will need to commit your changes and push to your GitHub Enterprise Pages repository again to trigger another build on the server.
