chore: add Flue deploy workflow on merge to production - #32772
Draft
mvvmm wants to merge 4 commits into
Draft
Conversation
kodster28
approved these changes
Aug 14, 2026
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://334ad134.preview.developers.cloudflare.com |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a GitHub Actions workflow that automatically deploys the Flue bot Worker (
cloudflare-docs-flue) whenever.flue/**changes are merged toproduction..github/workflows/flue-deploy.yml— new workflow: triggers on push toproduction(path-filtered to.flue/**), runspnpm run flue:deploy, uses the existingCLOUDFLARE_API_TOKENsecret, serializes deploys withcancel-in-progress: false, and posts a Google Chat failure alert on errorpackage.json— drops--secrets-file .envfromflue:deploy; Worker runtime secrets are preconfigured on the Worker and preserved across deploys by Wrangler.flue/wrangler.jsonc— addssecrets.requiredlisting all 10 production runtime secrets sowrangler deployfails explicitly if any are missing.github/workflows/ci.yml— addsflue-deploy.ymltopaths-ignoreso the main docs CI does not run on deploy-workflow-only changesDocumentation checklist