From dc3105854228cd62546370bca5df7c491870a5b4 Mon Sep 17 00:00:00 2001 From: Bhagirath Mehta Date: Fri, 22 May 2026 12:39:51 -0500 Subject: [PATCH] Auto-enable Pages on first deploy The GitHub Pages site has never been provisioned for this repository, so the post-merge deploy job in deploy-docs-pages.yml fails when actions/configure-pages@v5 looks up the site and gets a 404 (HTTP Not Found from the Pages API). Pass `enablement: true` to actions/configure-pages so the action provisions the Pages site on first run instead of erroring out. The workflow already grants the `pages: write` and `id-token: write` permissions that the action needs to do this. If the org-level GITHUB_TOKEN restrictions still prevent automatic enablement, a repository admin only needs to flip Settings -> Pages -> Build and deployment -> Source to `GitHub Actions` once; subsequent deploys will then succeed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/workflows/deploy-docs-pages.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/deploy-docs-pages.yml b/.github/workflows/deploy-docs-pages.yml index 09ecd2d35..f010ed508 100644 --- a/.github/workflows/deploy-docs-pages.yml +++ b/.github/workflows/deploy-docs-pages.yml @@ -72,6 +72,8 @@ jobs: steps: - name: Configure GitHub Pages uses: actions/configure-pages@v5 + with: + enablement: true - name: Deploy to GitHub Pages id: deployment