Why so many Pages actions?

GitHub Pages can be updated in more than one way:

  • Official artifact + deploy actions — Recommended in GitHub docs: build static assets, upload-pages-artifact, then deploy-pages with OIDC.

  • Third-party push actions — For example peaceiris/actions-gh-pages, which commits or pushes a branch (gh-pages) from your workflow.

Antora Site Builder intentionally does not choose a deploy mechanism: it runs Antora and exposes site-path so you can plug in whichever pattern your org standardizes on.

GitHub Marketplace does not forbid .github/workflows/ in an action repository: CI, tests, and lint workflows for the action itself are common. What you do not get is a workflow that automatically appears in a consumer’s repo—users add their own workflows and uses: your action. This repository publishes this documentation site to GitHub Pages via .github/workflows/publish-docs.yml. Maintainer checklist: Publishing to Marketplace.