DEVOPS
Re-run quarantined tests and auto-unquarantine the ones that stabilize
When a quarantined test issue is labeled ready-recheck in GitHub, runs the test in isolation many times.
How it runs
The automated pipeline, trigger to output.
- TriggerIssue labeled ready-recheck in GitHubGitHub
- ActionRun targeted test N times via shellShell
- LogicBranch: stable above threshold vs still flaky
- ActionOpen PR removing skip and close issueGitHub
- OutputReturn PR URL or recheck verdict
What it does
This workflow closes the quarantine loop by safely returning healthy tests to the suite. When an engineer labels a quarantine issue ready-recheck, it runs the named test in isolation a configurable number of times via a shell runner. If the test passes on every iteration above the confidence threshold, it opens a GitHub PR removing the skip annotation and closes the tracking issue; if it flakes again, it comments with the failure rate and keeps the quarantine in place.
When to use it
Use it after a suspected fix lands and you want objective proof a test is stable before un-skipping it, rather than trusting a single green run.
How it works
- 1A GitHub issue labeled ready-recheck triggers the workflow.
- 2A shell step runs the targeted test N times in isolation and records the pass count.
- 3A branch checks whether the pass rate clears the stability threshold.
- 4If stable, it opens a GitHub PR removing the quarantine annotation and closes the issue.
- 5If still flaky, it comments the measured failure rate and leaves the quarantine.
- 6The PR URL or the recheck verdict is returned as output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.