Skip to content

Migrate Pages deploy from gh-pages branch to actions/deploy-pages#10

Merged
NullSablex merged 1 commit into
masterfrom
fix-theme
May 18, 2026
Merged

Migrate Pages deploy from gh-pages branch to actions/deploy-pages#10
NullSablex merged 1 commit into
masterfrom
fix-theme

Conversation

@NullSablex

Copy link
Copy Markdown
Owner

GitHub Pages was switched to the workflow-based source (build_type=workflow) but the docs.yml job kept calling mkdocs gh-deploy --force --clean, which only writes to the gh-pages branch that the new Pages source no longer reads. Result: every Docs run was green while the live site stayed on the old Jekyll render of master.

Rewrite the deploy job to use the proper Pages deployment actions:

  • build: still runs mkdocs build --strict on push and PR. On master push, also uploads the rendered site/ as a Pages artifact via actions/upload-pages-artifact@v5.
  • deploy: replaces the mkdocs gh-deploy step with actions/deploy-pages@v5. Adds the required pages: write + id-token: write permissions and the environment: github-pages declaration GitHub requires for OIDC-signed Pages deployments.
  • concurrency: group:pages, cancel-in-progress:false prevents racing deployments without aborting one already in flight.

The gh-pages branch is no longer touched and can be deleted after the first successful workflow-based deploy.

GitHub Pages was switched to the workflow-based source (build_type=workflow)
but the docs.yml job kept calling `mkdocs gh-deploy --force --clean`, which
only writes to the gh-pages branch that the new Pages source no longer reads.
Result: every Docs run was green while the live site stayed on the old
Jekyll render of master.

Rewrite the deploy job to use the proper Pages deployment actions:

- build: still runs mkdocs build --strict on push and PR. On master push,
  also uploads the rendered site/ as a Pages artifact via
  actions/upload-pages-artifact@v5.
- deploy: replaces the `mkdocs gh-deploy` step with actions/deploy-pages@v5.
  Adds the required `pages: write` + `id-token: write` permissions and the
  `environment: github-pages` declaration GitHub requires for OIDC-signed
  Pages deployments.
- concurrency: group:pages, cancel-in-progress:false prevents racing
  deployments without aborting one already in flight.

The gh-pages branch is no longer touched and can be deleted after the first
successful workflow-based deploy.
@NullSablex NullSablex merged commit c431d02 into master May 18, 2026
9 checks passed
@NullSablex NullSablex deleted the fix-theme branch May 18, 2026 16:04
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.

1 participant