ENGINEERING
Quarantine Flaky Tests from GitHub Actions into a ClickUp Cleanup Queue
Watches GitHub Actions for tests that pass on retry, adds the worst offenders to a quarantine list, and files an owner-assigned ClickUp task for each one.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub Actions workflow run completedGitHub
- ActionFetch jobs and test annotations for the runGitHub
- LogicKeep tests that failed then passed on retry above threshold
- ActionResolve owner from CODEOWNERSGitHub
- ActionAppend test to quarantine list and commitGitHub
- OutputCreate owner-assigned ClickUp cleanup taskClickUp
What it does
This workflow turns noisy CI retries into an actionable cleanup backlog. When a GitHub Actions run reports a test that failed then passed on rerun, it records the flake, decides whether the test crosses your instability threshold, and creates a triaged ClickUp task assigned to the code owner so the flake gets fixed instead of ignored.
When to use it
Run this when your CI relies on automatic retries and green builds are hiding intermittent failures. It is for engineering teams who want a single quarantine queue with clear ownership rather than re-discovering the same flaky test every week.
How it works
- 1A completed GitHub Actions workflow run fires the trigger.
- 2The flow pulls the run's job and test annotations to find tests that failed on first attempt but passed on retry.
- 3A filter keeps only tests whose flake count over the trailing window exceeds the threshold, dropping one-off blips.
- 4For each qualifying test it reads CODEOWNERS to resolve the responsible engineer.
- 5It appends the test to the quarantine list in the repo and opens a ClickUp task tagged 'flaky', assigned to that owner, with the failing run link.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.