GitHub Actions actions/configure-pages "Pages not enabled"

By Daniel Zoghalchali·Latchkey

actions/configure-pages queries the repository Pages configuration. If Pages is disabled, or its build source is not set to GitHub Actions, the lookup fails before deploy.

What this error means

A configure-pages step fails getting the Pages site, suggesting Pages is not enabled or the source is wrong.

Error: Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, rather than from a branch.
Error: HttpError: Not Found

Common causes

Pages disabled for the repo

configure-pages needs Pages turned on in repository settings.

Source set to a branch, not Actions

When the Pages build source is a branch, the Actions deploy flow cannot configure it.

How to fix it

Enable Pages with the Actions source

1. In Settings > Pages, set Source to GitHub Actions.
2. Add pages: write and id-token: write permissions to the deploy job.
3. Use enablement: true on configure-pages to auto-enable where supported.

permissions:
  pages: write
  id-token: write
steps:
  - uses: actions/configure-pages@v5
    with:
      enablement: true

How to prevent it

• Set the Pages source to GitHub Actions before running the deploy workflow.
• Keep pages: write and id-token: write on the deploy job.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions