DEVOPS
On Rollout PR Merge, Schedule a Flag Cleanup Reminder
When a pull request that flips a flag to 100% is merged, records the flag and starts a countdown; once the configured soak period passes with the flag still fully on, it files…
How it runs
The automated pipeline, trigger to output.
- TriggerRollout-labeled PR mergedGitHub
- ActionRecord flag, owner, and merge dateHTTP webhook
- LogicWait out the soak period
- ActionRe-check flag rollout stateHTTP webhook
- LogicProceed only if still 100% on
- OutputOpen Linear cleanup ticket linked to PRLinear
What it does
This workflow catches flags at the moment they hit full rollout. When a GitHub PR labeled as a rollout merges, it captures the flag key and start date, then later checks whether the flag is still 100% after the soak window and, if so, opens a Linear ticket to retire it.
When to use it
Use it when rollouts are tied to PRs and you want cleanup queued at the exact moment a flag graduates, rather than discovered weeks later in a broad audit. It links each cleanup ticket back to the originating rollout PR.
How it works
- 1A GitHub event trigger fires when a PR with the rollout label is merged.
- 2An action records the flag key, owner, and merge date to a tracking store.
- 3A logic step waits out the configured soak period.
- 4An action re-checks the flag state via the flag service.
- 5A logic step proceeds only if the flag is still 100% on.
- 6An action opens a Linear cleanup ticket referencing the original PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.