DEVOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerNew pull request commentGitHub
- LogicParse quarantine command and verify write access
- ActionValidate the test exists in the suiteGitHub
- ActionCommit quarantine entry to the PR branchGitHub
- ActionOpen GitHub tracking issue linked to the PRGitHub
- OutputReply on the PR comment confirming the quarantineGitHub
What it does
It lets an engineer quarantine a known-flaky test directly from a pull request by commenting a command, without leaving the review. The flow makes the manifest change on the PR branch, files a tracking issue, and confirms back in the thread.
When to use it
Use it when a reviewer spots a flake blocking an otherwise-good PR and wants a fast, auditable way to isolate it in the same branch rather than asking the author to edit config by hand.
How it works
- 1A new PR comment fires the trigger.
- 2A logic step checks the comment for the quarantine command and confirms the commenter has write access.
- 3The flow validates that the named test exists in the suite, replying with an error if not.
- 4It commits the quarantine entry to the PR's branch via GitHub.
- 5It opens a GitHub tracking issue labeled `flaky-test` and cross-links the PR.
- 6It replies to the original comment confirming the test was quarantined and linking the issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.
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.
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.