From b0d80c373309de9f4a70b6f077f361cabb5db1df Mon Sep 17 00:00:00 2001 From: aziz0220 Date: Sun, 30 Aug 2026 15:50:09 +0100 Subject: [PATCH] Let the deployment create the Pages site it publishes to The first run after merging failed in configure-pages: the repository has no Pages site, and the step looks for one rather than creating it. Nothing about the page itself was wrong. Asking the step to create the site keeps the workflow self-contained instead of depending on a setting someone has to remember to flip, and it does nothing once the site exists. It still needs the workflow token to be allowed to create one, so if this run fails the same way, the setting is the only route: Settings, Pages, source GitHub Actions. --- .github/workflows/pages.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index f0587ba..21ce570 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -24,6 +24,12 @@ jobs: steps: - uses: actions/checkout@v4 - uses: actions/configure-pages@v5 + with: + # The repository had no Pages site, so this step failed the first + # deployment looking for one. Creating it needs a setting a repository + # administrator flips once; asking the action to create it lets the + # workflow stand on its own, and it is a no-op once the site exists. + enablement: true - uses: actions/upload-pages-artifact@v3 with: path: site