DEVOPS
Open GitLab MRs that prune stale flags and their config entries
Finds flags at 100% for 30+ days, then opens a GitLab merge request that removes both the code guards and the flag's definition from your flag-config file.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the run
- ActionRead rollout state and ages from DatadogDatadog
- LogicFilter to flags at 100% for 30+ days
- ActionFind code refs and config entry in GitLabGitLab
- ActionOpen MR pruning code guards and config keyGitLab
- OutputList new MRs in Slack for reviewSlack
What it does
This workflow produces complete flag removals on GitLab. Many cleanups delete the code branch but leave the flag definition rotting in a config file. This finds flags at 100% for 30+ days and opens a single merge request that strips both the code guards and the matching entry in your flag-config file, so the flag disappears from the codebase entirely.
When to use it
Use it if your team is on GitLab and stores flag definitions in a tracked config file (JSON, YAML, or similar) alongside code. It is the right fit when half-done removals — code gone but config orphaned — are the recurring mess you want to stop creating.
How it works
A weekly schedule triggers the run. The workflow reads rollout state and last-change dates from Datadog and filters to flags at 100% for 30+ days. For each stale flag it searches the GitLab repo for both the code references and the config-file entry. It creates a branch, removes the guards and deletes the config key, and opens a merge request describing the flag and its rollout history. A Slack note lists the new MRs for review.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.