DEVOPS
PR Canary Cold-Start Comparison Comment for Cloudflare Workers
When a PR deploys a Cloudflare preview Worker, measures the canary's cold-start latency against the current production tag and posts a pass/fail comparison comment back…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR preview deploy eventGitHub
- ActionMeasure preview cold-start p95Cloudflare
- ActionFetch production tag baselineCloudflare
- LogicPass or fail on delta threshold
- OutputComment verdict on the pull requestGitHub
What it does
When a pull request opens a Cloudflare preview deployment, this workflow benchmarks the preview Worker's cold start, fetches the production tag's current cold-start baseline, computes the delta, and writes a clear pass or fail comparison directly as a comment on the originating GitHub pull request so reviewers see the cost before merging.
When to use it
Use it to shift cold-start awareness left: catch a dependency or bundle-size change that inflates startup time while it is still in review, not after it ships. Ideal for teams who already run Cloudflare preview deployments per PR.
How it works
- 1A GitHub pull request preview-deploy event triggers the run.
- 2Measure the preview Worker's cold-start p95 from Cloudflare analytics.
- 3Fetch the live production tag's cold-start baseline for comparison.
- 4Branch: classify the PR as pass or fail based on the percentage delta.
- 5Post a GitHub PR comment showing both numbers, the delta, and the verdict.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.