setup-cloudflare-continuous-delivery

To automate Cloudflare Pages deployments, you need a GitHub Actions workflow and a wrangler.toml file to configure branch or tag based continuous delivery. This setup eliminates manual configuration by generating pipeline files and storing required repository secrets via the gh CLI.

Continuous delivery for Cloudflare Pages automates project deployments on every code push. The wrangler.toml file defines the required project settings, enabling local deploys via a Makefile and automated remote deployments through the generated GitHub Actions workflow.

Yes, the gh CLI is required to configure and store GitHub repository secrets for Cloudflare Pages. The automation uses the gh CLI to securely inject necessary credentials into your repository, which the GitHub Actions workflow then uses to authenticate with Cloudflare.

Yes, the setup process can create the Cloudflare Pages project automatically if it is missing. It handles project creation, writes the configuration files, and provides guidance for the initial local deploy to ensure your end-to-end continuous delivery pipeline is fully established.

Running a local deploy requires a generated Makefile and wrangler.toml to configure the environment. The setup process generates these files and provides specific guidance for the initial local deploy, allowing you to validate the configuration before pushing to the automated pipeline.

Setting up the pipeline requires credentials for both GitHub and Cloudflare to validate the configuration. The setup process validates required credentials, creates the Pages project if missing, and configures GitHub repo secrets using the gh CLI to ensure the workflow can deploy automatically.