DEVOPS
Re-verify Quarantined Tests and Auto-Unquarantine Stable Ones
On a schedule, triggers isolated reruns of every quarantined test, and for any test that passes consistently across all attempts.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionDispatch isolated reruns of quarantined testsGitHub
- LogicPassed every attempt = stable?
- ActionOpen PR removing skip annotationGitHub
- ActionClose matching Linear ticketLinear
- OutputReturn list of reinstated tests
What it does
This workflow closes the loop on quarantine. Quarantined tests tend to stay skipped forever; this re-runs each one in isolation many times and, when a test proves stable again, automatically proposes returning it to the blocking suite and closes its tracking ticket.
When to use it
Use this when quarantine has become a graveyard. It keeps the skip list honest by continuously re-testing flagged tests and reinstating the ones that have quietly become reliable — often after an unrelated infra or dependency fix.
How it works
- 1A scheduled trigger fires (e.g. daily).
- 2The flow reads the current quarantine list and dispatches an isolated GitHub Actions run that executes each quarantined test N times.
- 3A logic step evaluates results: a test passing every attempt is deemed stable.
- 4For each stable test it opens a GitHub PR removing the skip annotation.
- 5It transitions the matching Linear ticket to Done with a comment linking the verification run.
- 6A list of reinstated tests is returned as the output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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.