docs-publish-github-pages

Fix GitHub Pages deployment workflows by validating the deploy path, verifying Pages is enabled, and patching triggers, gating logic, and deployment steps in your docs-publish.yaml file to ensure correct site publication. Apply patches only after confirming the current deploy path.

Published GitHub Pages sites may show wrong versions when deploy triggers mismatch the intended source. Validate the workflow to distinguish between the published site version and the git tag or package version, ensuring the site publishes from the correct branch or workflow.

Validate published HTML pages for GitHub Pages deployments by directly inspecting the live site content rather than inferring asset URLs. Identify the repository and Pages site, review the docs-publish.yaml workflow, and confirm the published site matches the intended version.

GitHub Pages deploy workflows require Pages to be explicitly enabled to ensure the site is published from the intended source. Inspect the docs-publish.yaml workflow triggers and Pages enablement settings to verify the workflow run succeeds and deployment completes correctly.

The best way to adjust publish triggers for GitHub Pages documentation is to patch triggers, gating logic, and deployment steps after validating the current deploy path. Ensure the workflow distinguishes the published site version from the git tag or package version.

Avoid using inferred asset URLs for GitHub Pages validation when you need to confirm site integrity. Instead, validate the published HTML pages directly to ensure the deployed site matches the intended version and that the workflow run succeeds end to end.