DEVOPS
Pre-Merge Cache-Config Guard on GitLab MR
On every GitLab merge request that touches Cloudflare config, predicts cache-efficiency risk from the diff and posts a pass/block verdict as an MR comment before the change can…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened/updated on cache-config pathGitLab
- ActionFetch MR diff for changed rule filesGitLab
- ActionRead live Cloudflare rulesetCloudflare
- LogicScore diff for hit-ratio-killing patterns
- ActionPost pass/block comment + set merge statusGitLab
- OutputPing author on block verdictSlack
What it does
This is a preventative guard, not a post-incident sentinel. When a GitLab MR opens or updates files in your Cloudflare config path, the workflow reads the diff, checks the proposed cache rules against Cloudflare's current ruleset, and flags edits known to wreck hit ratio — overly broad bypass rules, removed cache-everything rules, or TTLs set to zero. It posts a verdict comment and sets the MR to blocked when risk is high.
When to use it
Use it to stop cache regressions before they merge, when config-as-code reviewers can't always eyeball every Cloudflare rule change. It shifts cache-efficiency review left into the MR itself.
How it works
- 1GitLab MR event (opened or updated) triggers on the cache-config path.
- 2GitLab returns the MR diff for the changed rule files.
- 3Cloudflare provides the live ruleset to diff intent against current behavior.
- 4A logic step scores the change for known hit-ratio-killing patterns.
- 5GitLab posts a pass/block comment and updates the MR's merge status.
- 6Slack pings the author only when the verdict is a block.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.