Skip to content

Add .nojekyll to stop Jekyll from choking on vcpkg patch files - #136

Closed
liuzicheng1987 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-pages-build-failure
Closed

Add .nojekyll to stop Jekyll from choking on vcpkg patch files#136
liuzicheng1987 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-pages-build-failure

Conversation

Copilot AI commented Sep 6, 2026

Copy link
Copy Markdown

The Pages deployment failed with Invalid YAML front matter in vcpkg/ports/gsl/0001-configure.patch — Jekyll was parsing the patch file's leading --- as front matter.

Root cause

  • The docs site is built via Hugo and deployed through .github/workflows/docs.yaml, but nothing prevented Jekyll (e.g. a legacy branch-based Pages source) from crawling the full checkout, including vcpkg/.
  • A prior PR (Delete .nojekyll #135) had removed an existing .nojekyll file, which likely reintroduced this exposure.

Changes

  • Repo root: added .nojekyll at the top level to disable Jekyll processing if the repo is ever served via a branch-based Pages source.
  • Hugo output: added docs/static/.nojekyll, which Hugo copies into docs/public/ (the actual deployed artifact), so the marker travels with the built site.
  • Workflow: set include-hidden-files: true on the actions/upload-pages-artifact step in docs.yaml, since dotfiles are stripped from the artifact by default and would otherwise drop .nojekyll before deployment.

Co-authored-by: liuzicheng1987 <19538706+liuzicheng1987@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix GitHub Pages build failure due to invalid YAML front matter Add .nojekyll to stop Jekyll from choking on vcpkg patch files Sep 6, 2026
Copilot AI requested a review from liuzicheng1987 September 6, 2026 21:55
@liuzicheng1987
liuzicheng1987 marked this pull request as ready for review September 7, 2026 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants