Configure GitHub Pages to publish the website app instead of the repo root

[Copilot]

GitHub Pages was effectively behaving like a branch-based publish from the repository root, which allowed the root README.md to be served instead of the built site from website/. This change aligns the repo with the GitHub Actions Pages flow already used to build the app.

• Pages workflow

  • Adds the official Pages configuration step to .github/workflows/pages.yml so the deployment is explicitly set up for GitHub Actions publishing.
  • Keeps the existing build target unchanged: website/dist.

  - name: Configure GitHub Pages
    uses: actions/configure-pages@v5

• Repository guidance

  • Documents in README.md that the Pages source should be set to GitHub Actions.
  • Clarifies why branch publishing is not suitable here: it only supports the repo root or /docs, not /website.

• Result

  • Pages deployment remains driven by the existing website build, but the repo is now clearly configured and documented to publish the built app rather than falling back to root content.

• Screenshot

  • 

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• digablesolutions.github.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
  • Triggering command: /usr/bin/curl curl -I -L --max-time 20 REDACTED (dns block)
• https://api.github.com/repos/actions/configure-pages/git/ref/tags/v5
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)
• https://api.github.com/repos/actions/deploy-pages/git/ref/tags/v4
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)
• https://api.github.com/repos/actions/upload-pages-artifact/git/ref/tags/v4
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Can we deploy to github pages this repos website from the folder website. Now it deploys README

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

Aligns GitHub Pages publishing with the existing GitHub Actions build so Pages serves the built site from website/dist instead of the repository root content (e.g., README.md).

Changes:

• Adds an explicit GitHub Pages configuration step to the Pages workflow.
• Documents the required GitHub Pages setting (Source: GitHub Actions) and why branch publishing doesn’t work for /website.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
README.md	Documents how Pages is deployed and the required Settings → Pages configuration.
.github/workflows/pages.yml	Adds actions/configure-pages to make Actions-based Pages publishing explicit.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.