DEVOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionRead quarantine manifest and run history from GitHubGitHub
- LogicRank by age and flake frequency, map to owning team
- ActionCreate or update Linear issue per owning teamLinear
- ActionPublish ranked report to ConfluenceConfluence
- OutputPost top offenders to SlackSlack
What it does
It produces a weekly view of every quarantined test, how long it has been isolated, and how often it still flakes, then turns that into prioritized Linear tickets so quarantined tests actually get fixed instead of rotting.
When to use it
Use it when quarantine is already in place but tests pile up in the isolated state and nobody fixes them. This closes the loop by assigning ownership and surfacing the oldest, most disruptive offenders each week.
How it works
- 1A weekly schedule starts the run.
- 2The flow reads the quarantine manifest and recent run history from GitHub.
- 3A logic step ranks quarantined tests by age and recent flake frequency and maps each to an owning team via CODEOWNERS.
- 4For each test it creates a Linear issue, or updates the existing one with the latest stats, assigned to the owning team.
- 5It writes the full ranked report to a Confluence page for visibility.
- 6It posts the top offenders and overall quarantine count to the engineering channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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.
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.