Skip to content

Fix GitHub Pages deployment conflicts by preventing Jekyll processing of Hugo site#1

Open
Copilot wants to merge 7 commits into
mainfrom
copilot/remove-pages-build-action
Open

Fix GitHub Pages deployment conflicts by preventing Jekyll processing of Hugo site#1
Copilot wants to merge 7 commits into
mainfrom
copilot/remove-pages-build-action

Conversation

Copilot AI commented Sep 9, 2025

Copy link
Copy Markdown

Problem

The repository was experiencing deployment conflicts due to GitHub's automatic "pages-build-deployment" action trying to process the Hugo site with Jekyll. This caused build failures with errors like:

Liquid Exception: Invalid Date: '"{{ .Date }}"' is not a valid datetime.
ERROR: YOUR SITE COULD NOT BE BUILT

The issue occurred because:

  • GitHub Pages was configured to deploy from a branch (triggering automatic Jekyll processing)
  • Jekyll cannot parse Hugo template syntax like {{ .Date }}
  • The custom Hugo workflow was working correctly, but the automatic deployment was interfering

Solution

This PR implements the minimal file-based changes needed to resolve the conflict:

1. Added .nojekyll file

An empty .nojekyll file in the repository root tells GitHub Pages not to process the site with Jekyll, preventing template syntax conflicts.

2. Added documentation

Created GITHUB_PAGES_CONFIG.md with clear instructions for the required repository settings change:

## Required Configuration
1. Go to Settings > Pages in the GitHub repository
2. Under Source, select "GitHub Actions" instead of "Deploy from a branch"
3. Save the changes

Impact

  • Hugo workflow: Continues working perfectly (verified with test build)
  • Jekyll conflicts: Eliminated by .nojekyll file
  • Zero downtime: Changes don't affect existing deployments
  • 🎯 Complete solution: When combined with the repository settings change, will fully disable the conflicting automatic deployment

Manual Action Required

To complete the fix, the repository owner needs to change the GitHub Pages source from "Deploy from a branch" to "GitHub Actions" in the repository settings. This will disable the automatic "pages-build-deployment" action and rely solely on the working Hugo workflow.

The changes in this PR are minimal, surgical, and preserve all existing functionality while providing a clear path to resolve the deployment conflicts.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

sspirial and others added 6 commits March 1, 2025 10:47
- Created index.html for the innovation tag with a redirect.
- Added index.html for the javascript tag with complete structure and content.
- Generated index.xml for the javascript tag to provide RSS feed.
- Created index.html for the vsla tag with complete structure and content.
- Generated index.xml for the vsla tag to provide RSS feed.
- Added pagination support with index.html for both javascript and vsla tags.
- Created index.xml files for Meritocracy, Reputation Systems, and Technocracy tags with appropriate metadata and item entries.
- Developed HTML pages for each tag with canonical links and redirection to the main tag page.
- Implemented structured content for the "Entropy Meritocracy" post under each tag, including descriptions and publication details.
- Ensured all new pages are styled consistently with existing site design and functionality.
…flicts

Co-authored-by: sspirial <96319511+sspirial@users.noreply.github.com>
Copilot AI changed the title [WIP] remove the github action: pages-build-deployment Fix GitHub Pages deployment conflicts by preventing Jekyll processing of Hugo site Sep 9, 2025
Copilot AI requested a review from sspirial September 9, 2025 16:02
@sspirial sspirial marked this pull request as ready for review September 11, 2025 06:30
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