Deploy (Cloudflare Pages)

Cloudflare deploy now runs from GitHub Actions after testing succeeds on main. If the Cloudflare Pages GitHub App is still connected, disable it. GitHub Actions should be the only deploy source, otherwise Pages can create its own preview or production deploys and skip the GH-driven flow.

Required GitHub Secrets

• CLOUDFLARE_API_TOKEN: Cloudflare API token with Pages deploy access
• CLOUDFLARE_ACCOUNT_ID: Cloudflare account ID
• VITE_SUPABASE_URL: Supabase project URL
• VITE_SUPABASE_ANON_KEY: Supabase anon public key

Required GitHub Variable

• CLOUDFLARE_PAGES_PROJECT_NAME: Cloudflare Pages project name

Build output is dist, and the deploy workflow is in .github/workflows/deploy-cloudflare.yml. The workflow deploys main as the production branch, so the live site should stay on the project’s production *.pages.dev URL or custom domain instead of a head.* preview URL. If you set CLOUDFLARE_PAGES_PROJECT_NAME to min-cal-tracker, the Pages URL will be https://min-cal-tracker.pages.dev if that subdomain is available.