DEVOPS
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook from nightly stability runnerHTTP webhook
- LogicCheck each test for required consecutive clean passes
- ActionRestore stable tests to required suite in GitHubGitHub
- ActionClose the corresponding GitHub tracking issueGitHub
- OutputPost un-quarantined tests to SlackSlack
What it does
It's the exit half of quarantine. When a quarantined test has passed cleanly across a streak of runs, this workflow returns it to the required suite and closes its tracking issue, so the gate stays meaningful.
When to use it
Use it when you have a nightly job that re-runs quarantined tests in isolation and you want stable ones promoted back automatically rather than leaving them excluded forever. Pairs naturally with any auto-quarantine workflow.
How it works
- 1The nightly stability runner posts results to the webhook trigger.
- 2A logic step checks each quarantined test for the required number of consecutive clean passes.
- 3Tests still flaking are left untouched and skipped.
- 4For tests that cleared the streak, the flow commits a manifest change in GitHub to restore them to the required suite.
- 5It closes the corresponding GitHub tracking issue with a note on the passing streak.
- 6It posts which tests were un-quarantined to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.
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.