DEVOPS
Stale Feature Flag Harvester: Open GitLab Removal MRs Past Kill-Date
Weekly scan of your flag registry for flags whose kill-date has passed, then auto-opens a GitLab merge request that strips each stale flag's conditional branches from the code.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the flag scan
- ActionQuery flag registry for kill-dates in PostgresPostgres
- LogicFilter to flags past kill-date and still active
- ActionGenerate removal patch and open MR per flagGitLab
- OutputPost cleanup digest to SlackSlack
What it does
Reads your feature-flag registry, finds every flag whose configured kill-date is now in the past, and for each one opens a GitLab merge request that removes the flag's dead conditional branches. It posts a digest to Slack so the owning team sees the cleanup queue.
When to use it
Run this when flags accumulate faster than teams remove them and your codebase is littered with `if (flags.x)` branches that resolved months ago. Best for teams that tag each flag with an explicit kill-date and want the removal toil automated rather than nagged.
How it works
- 1A weekly schedule fires the harvester.
- 2It pulls the flag registry from Postgres and filters to flags whose `kill_date` is earlier than today and still marked active.
- 3For each stale flag it searches the GitLab repo for references, generates a patch that deletes the flag guard and keeps the live branch, and opens an MR assigned to the flag owner.
- 4A branch checks whether any stale flags were found.
- 5It posts a Slack summary listing the new MRs, owners, and how long each flag was overdue.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.