GitHub Pages Deployment Error on Forks

Any fork of this repository upon each commit attempts to publish a GitHub Pages site of the changes being made to the repository, and then fails to do so. I am unfortunately less familiar with GitHub actions than I would like to be so I am unsure if this is even something that can be avoided. But it would be very nice if it could. The error messages involved can be viewed [here](https://github.com/Les-Wet/gb-asm-tutorial/actions/runs/21280535229) as an example and are shown below as well:

```console
Deploy to GitHub pages
Error: Failed to create deployment (status: 404) with build version 13ce6651d0d00a7d4a855f3d2f03d7d756f9f0e3. Request ID A001:748CB:4D81E55:4F0C036:69733936 Ensure GitHub Pages has been enabled: https://github.com/Les-Wet/gb-asm-tutorial/settings/pages
```

```console
HttpError: Not Found
at /home/runner/work/_actions/actions/deploy-pages/v4/node_modules/@octokit/request/dist-node/index.js:124:1
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/api-client.js:125:1)
at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/deployment.js:74:1)
at main (/home/runner/work/_actions/actions/deploy-pages/v4/src/index.js:30:1)
```

Is there maybe some kind of conditional statement we could add to [build_and_deploy.yaml](https://github.com/gbdev/gb-asm-tutorial/blob/master/.github/workflows/build-and-deploy.yml) to not run this action if running on a fork?