DEVOPS
Weekly stale feature-flag sweep with auto-generated GitLab removal MRs
Every Monday, scans your flag-state table for flags that have been 100% rolled out for 90+ days and opens a GitLab merge request to delete each one, assigned to its owner.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionQuery flags 100% rolled out 90+ daysPostgres
- LogicExclude experiment / kill-switch flags
- ActionOpen removal MR per flagGitLab
- ActionAssign MR to flag ownerGitLab
- OutputPost batch summary to SlackSlack
What it does
Runs a scheduled audit of your feature-flag inventory, isolates flags that have served the same fully-enabled value to all traffic for at least 90 days, and opens one GitLab merge request per stale flag that strips the flag check and assigns the flag's owner as reviewer.
When to use it
Use it when flag debt is piling up and nobody owns cleanup. Teams that ship behind flags accumulate dead conditionals that never get removed; this turns that backlog into reviewable MRs on a predictable cadence.
How it works
- 1A weekly schedule fires the workflow Monday morning.
- 2A Postgres query pulls flags where rollout = 100% and last_changed_at is older than 90 days.
- 3A filter drops flags still referenced by an active experiment or kill-switch tag.
- 4For each remaining flag, a GitLab action creates a branch, removes the flag's references, and opens an MR titled with the flag key.
- 5The same action sets the MR assignee to the flag owner pulled from the flag record.
- 6A Slack message posts the batch summary with MR links to the platform channel.
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.