DEVOPS
Weekly quarantine-debt review reported to Notion and digested in Slack
Each week an agent reviews all open flaky-quarantine issues across GitHub and Linear, ranks the worst offenders by age and impact, writes a Notion review page.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull open quarantine issues from GitHub and LinearGitHub
- LogicAgent ranks items by age, frequency, and ownership
- ActionWrite ranked review page to NotionNotion
- OutputPost quarantine-debt digest to SlackSlack
What it does
Quarantined tests have a way of being forgotten. This weekly workflow gathers every open flaky-quarantine item from GitHub and Linear, and an agent ranks them by how long they have been skipped, how often they were hit, and which area of the codebase they cover. It writes a structured review page in Notion and posts a short Slack digest highlighting the stalest tests that need an owner this week.
When to use it
Use it to keep your quarantine list honest and prevent permanent skips. Ideal for teams that want a recurring ritual to pay down test debt instead of letting it accumulate.
How it works
- 1A weekly schedule starts the review.
- 2The workflow pulls open quarantine-labeled issues from GitHub and Linear.
- 3An agent scores and ranks each item by age, hit frequency, and ownership gaps.
- 4It composes a Notion page with the ranked table and trend versus last week.
- 5It posts a Slack digest naming the top items and their suggested owners.
- 6The Notion page URL is returned as output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect NotionPages, databases, comments.
- 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.
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.
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.
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.