DEVOPS
Open GitLab MRs that auto-remove expired feature-flag branches
For each flag past its kill-date, an agent rewrites the code to keep the shipped branch, deletes the dead branch and the flag check.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run with expired flag list
- ActionRead flag references and rollout stateGitLab
- LogicDetermine surviving branch and edits to make
- ActionCommit removal to a per-flag branchGitLab
- ActionOpen draft merge request, tag reviewerGitLab
- OutputLink the originating Linear cleanup ticketLinear
What it does
Does the tedious removal work itself. Given a flag whose kill-date has passed and whose rollout was 100%, an agent edits the affected files to inline the live branch, strips the now-dead `else` path and the flag import, then opens a draft merge request scoped to that one flag.
When to use it
When the cleanup backlog is real removal work, not just tickets. Best for flags that fully shipped and just need the scaffolding deleted. The draft MR keeps a human in the loop for the final merge.
How it works
- 1A schedule or manual run provides the list of expired, fully-rolled-out flags.
- 2The agent reads each flag's references and determines the surviving branch from its rollout state.
- 3It rewrites the code to inline that branch and remove the flag check, import, and config entry.
- 4It commits the change to a new branch per flag and opens a draft GitLab merge request.
- 5It tags the owning reviewer and links the originating cleanup ticket.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.