DEVOPS
Scan test history in BigQuery and open a PR that skips chronic flakes
Runs nightly over your test-results warehouse in BigQuery, flags tests whose pass rate dips below a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery rolling pass rate per test in BigQueryBigQuery
- LogicKeep tests below pass-rate threshold with enough samples
- ActionOpen GitHub PR adding quarantine annotationsGitHub
- OutputReturn pull request URL
What it does
This scheduled job queries a BigQuery table of historical test outcomes, computes each test's pass rate over a rolling window, and identifies chronic offenders that fail intermittently across many runs. For tests that cross the instability threshold it opens a GitHub pull request adding a skip/quarantine annotation, so the flake stops blocking unrelated merges while it waits for a real fix.
When to use it
Use it when you already export CI results to a warehouse and want data-driven quarantine decisions rather than reacting to single failures. Best for large suites where one bad test can stall the whole team.
How it works
- 1A nightly schedule fires the workflow.
- 2A BigQuery query aggregates pass rate and run count per test over the last N days.
- 3A filter keeps tests below the pass-rate threshold with enough samples to be statistically meaningful.
- 4The workflow generates the quarantine annotation edits for each offending test file.
- 5It opens a GitHub PR with the changes, listing each test's pass rate and run count in the description.
- 6The PR URL is returned as output for the on-call engineer to review.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.