Lunny Xiao efd26a3d61 Deploy a Cloudflare Pages preview for pull requests (#498) ...

Pull requests now get a Cloudflare Pages preview deployment after the site build succeeds, and the preview URL is written back as the last line of the pull request description.

- `concurrency` cancels the previous preview build when a pull request is pushed again.
- After `make build`, the workflow copies `cloudflare/_headers` into `build/` (same as the production deployment, so the file is never published to S3/CloudFront) and runs `wrangler pages deploy build --project-name docs-gitea-com --branch pr-<number>`, then extracts the `*.pages.dev` URL from the wrangler output.

Notes:
- Pull requests from forks do not receive the secrets, in that case the preview steps are skipped with a log message and the build check still runs.
- Requires `CLOUDFLARE_ACCOUNT_ID` / `CLOUDFLARE_API_TOKEN` (Pages edit permission) and `DEPLOY_TOKEN` (pull request write permission).

<!-- cloudflare-preview --> Preview: https://pr-498.docs-gitea-com.pages.dev

Reviewed-on: https://gitea.com/gitea/docs/pulls/498
Reviewed-by: Zettat123 <[email protected]>

2026-08-10 01:57:33 +00:00

..

build-and-publish.yaml

Add Cloudflare Pages cache headers for static assets (gitea/docs#473)

2026-07-27 20:30:17 +00:00

test.yaml

Deploy a Cloudflare Pages preview for pull requests (#498)

2026-08-10 01:57:33 +00:00

update_runner_reference.yaml

Add runner 2 and 3 documentations (#488)

2026-08-07 21:02:26 +00:00

update_swagger.yaml

Fix the swagger update cron job (#481)

2026-08-02 23:25:17 +00:00