DEVOPS
Confirm flag retirement and close debt issue when removal MR merges
Listens for merged GitLab MRs labeled flag-removal, marks the flag retired in Postgres, and closes the matching Linear cleanup issue so the debt ledger stays accurate.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR merged webhookGitLab
- LogicMatch flag-removal label, parse flag key
- ActionMark flag retired in PostgresPostgres
- ActionClose Linear cleanup issueLinear
- OutputConfirm retirement in SlackSlack
What it does
Reacts to the merge of a feature-flag removal merge request, updates the flag's status to retired in your flag-state table, and closes the corresponding Linear cleanup issue. It keeps the debt ledger and the backlog in sync without manual bookkeeping.
When to use it
Use it after you have a flow that opens removal MRs and tracks them in Linear. This is the closing-the-loop half: it ensures a flag is only counted as retired once its code is actually gone and merged.
How it works
- 1A GitLab webhook fires when a merge request is merged.
- 2A filter checks the MR carries the flag-removal label and extracts the flag key from the MR title.
- 3A Postgres action updates that flag's row to status retired with a retired_at timestamp.
- 4A Linear action finds the cleanup issue referencing the flag key and transitions it to Done.
- 5A Slack message confirms the retirement to the platform channel with the MR and issue links.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.