DEVOPS
Auto-unquarantine tests that have been stable for 14 days
Weekly, checks Datadog for quarantined tests that have passed every run for 14 consecutive days, removes them from the quarantine manifest via a GitHub PR.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionRead quarantine manifest from GitHubGitHub
- ActionQuery Datadog for 14-day pass/fail historyDatadog
- LogicClean streak and minimum run count met?
- ActionOpen GitHub PR removing stable testsGitHub
- OutputClose matching Linear issues as resolvedLinear
What it does
Closes the loop on quarantine. On a weekly schedule it reviews every test on the quarantine list, confirms via Datadog that it has had zero failures across a 14-day window, then opens a GitHub pull request removing it from the manifest and closes the corresponding Linear issue. Quarantine stops being a graveyard and becomes a temporary holding pen.
When to use it
Use this when fixed-but-still-quarantined tests accumulate because nobody remembers to re-enable them. It restores real coverage automatically once a test has proven itself stable.
How it works
- 1A weekly schedule fires.
- 2The flow reads the current quarantine manifest from GitHub.
- 3For each test, it queries Datadog for the pass/fail history over the last 14 days.
- 4A filter keeps only tests with a clean streak and a minimum run count.
- 5It opens a GitHub PR removing those tests from the manifest, citing the stability evidence.
- 6The final step closes each matching Linear issue with a resolution note and links the cleanup PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 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.