If a file in your GitHub Enterprise Pages repository references a symlinked file, your GitHub Enterprise Pages site will not build.
If your GitHub Enterprise Pages site fails to build because of a reference to a symlinked file, you'll get an email that looks like this:
Subject: Page build failed
The page build failed with the following error:
A file was included in `example.html` that is a symlink or does not exist in your `_includes` directory.
Troubleshooting a symlinked file error
We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to your GitHub Enterprise instance.
- Use your favorite text editor to open the file mentioned in the build failure email.
- Search for the
include
tag to see where you've referenced other files. For example:{% include cool_header.html %}
. - Copy or move any symlinked files into the
_includes
directory of your GitHub Enterprise Pages repository. - Commit and push to your GitHub Enterprise Pages repository on your GitHub Enterprise instance to trigger another build on the server.