`HttpError: Not Found` is superfluous (and unhelpful)

[jsoref]

https://github.com/jsoref/observablehq-plot/actions/runs/23816526592/job/69417401777#step:8:9

Error: Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the `enablement` parameter for this action.
Error: HttpError: Not Found

annotations

deploy

HttpError: Not Found
deploy
Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the enablement parameter for this action.
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

I got this when I synced a fork of a repo. It's more or less impossible for normal people to configure all forks of all repositories that use gh pages to match their requirements when forking. In my case, main isn't the default branch in this fork (it obviously is for the upstream).

[yoannchaudet]

This just indicates Pages is not enabled in your repository.

Not all repostitories are "fork friendly". I have seen some gate their workflow just for their repository to make sure on a fork it would not run. But that's not within your control.

You could just disable the workflow if you don't intend on deploying the site yourself.

[jsoref]

There's no need to report the HttpError. The other error message is useful:

Error: Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the enablement parameter for this action.