Hi @durack1, @tcbyrd,
I’ve resolved the issue that was causing this problem in the first place for our pages (a misunderstanding on my part as to where the jekyll configuration files go relative to the markdown pages*).
Allowing users to see errors such as this when deployment failed would be really helpful – it didn’t take me long to resolve once I had seen that exception, but without it I would have been stumped.
*Too much information: I had the markdown files under /docs which was being pointed at by github pages, but the configuration information such as the
assets were at the root of the repo. This was down to my approach in attempting to evolve from a very minimal setup that we had initially without running the
jekyll new command, and a limited understanding of how jekyll works. As I was running the jekyll server from the command line at the root of the repository it all looked fine when developing.