Skip to content

chore: add Flue deploy workflow on merge to production - #32772

Draft
mvvmm wants to merge 4 commits into
productionfrom
flue-deploy-workflow
Draft

chore: add Flue deploy workflow on merge to production#32772
mvvmm wants to merge 4 commits into
productionfrom
flue-deploy-workflow

Conversation

@mvvmm

@mvvmm mvvmm commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a GitHub Actions workflow that automatically deploys the Flue bot Worker (cloudflare-docs-flue) whenever .flue/** changes are merged to production.

  • .github/workflows/flue-deploy.yml — new workflow: triggers on push to production (path-filtered to .flue/**), runs pnpm run flue:deploy, uses the existing CLOUDFLARE_API_TOKEN secret, serializes deploys with cancel-in-progress: false, and posts a Google Chat failure alert on error
  • package.json — drops --secrets-file .env from flue:deploy; Worker runtime secrets are preconfigured on the Worker and preserved across deploys by Wrangler
  • .flue/wrangler.jsonc — adds secrets.required listing all 10 production runtime secrets so wrangler deploy fails explicitly if any are missing
  • .github/workflows/ci.yml — adds flue-deploy.yml to paths-ignore so the main docs CI does not run on deploy-workflow-only changes

Documentation checklist

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
* @cloudflare/product-owners
/.github/ @cloudflare/content-engineering, @kodster28, @mvvmm, @colbywhite, @ahaywood, @MohamedH1998
package.json @cloudflare/content-engineering

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants