GitHub Pages Not Reflecting Latest Build from main Branch

[kevinevans1]

As a maintainer of the documentation or static site,
I want GitHub Pages to consistently deploy the latest content from the main branch,
so that the published site remains accurate and up to date for users and contributors.

⸻

✅ Acceptance Criteria
• GitHub Pages source is correctly set to main (or the appropriate subdirectory like /docs)
• A recent commit to main triggers a successful GitHub Pages build and updates the live site
• Old or stale build artifacts (e.g. cached versions, .nojekyll files) are ruled out or removed
• Pages are verified to reflect the latest changes (e.g. via curl or incognito browser)
• If using GitHub Actions, deploy workflow correctly pushes static site output (e.g. _site/) to gh-pages and GitHub Pages source is set accordingly
• Build process logs are reviewed and confirmed to be running as expected with no silent failures

⸻

🛠️ Technical Notes
• Rebuilding locally with bundle exec jekyll build should match deployed output
• Consider toggling GitHub Pages source settings temporarily to force a clean rebuild
• Investigate the use of .nojekyll file — present only if serving static HTML without Jekyll

⸻

📎 Related
• GitHub Pages documentation
• GitHub Actions for static site deployment
• Internal issue: “GitHub Pages is 3 weeks behind despite successful builds”