DEVOPS
On-Merge Flag Audit: Nudge Owners When Their Flag Goes Stale
When a merge request lands, scans the diff for newly-introduced or long-lived feature flags past their kill-date and posts a threaded GitLab note plus a Slack DM to the flag owner.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge-event webhook firesGitLab
- ActionFetch MR diff and extract flag referencesGitLab
- ActionLook up kill-dates in registryPostgres
- LogicBranch if any referenced flag is overdue
- OutputComment on MR and DM owner in SlackSlack
What it does
Reacts to every merged GitLab MR, scans the touched files for feature-flag references, and flags any whose registered kill-date has already passed. It leaves a note on the MR and direct-messages the owner so cleanup happens at the moment the code is fresh in their mind.
When to use it
Use this to keep flag debt from compounding silently. Catching stale flags at merge time, while a developer is already in the file, is far more likely to result in actual removal than a batch report they ignore.
How it works
- 1A GitLab merge-event webhook triggers the workflow.
- 2It fetches the MR diff and extracts every flag key referenced in the changed files.
- 3It looks each key up in the Postgres registry and compares kill-dates against today.
- 4A branch decides whether any referenced flag is overdue.
- 5If so, it posts a threaded comment on the MR listing the stale flags and sends the owner a Slack DM with the removal checklist.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.