DEVOPS
Quarantine a Flaky Test from CI and File a ClickUp Owner Ticket
When a CI run reports a test that passed on retry, this workflow opens a quarantine PR that skips the test for one cycle, files a ClickUp ticket assigned to the test's code owner.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub Actions workflow_run completesGitHub
- LogicKeep only tests that failed then passed on retry
- ActionOpen quarantine PR skipping the test for one cycleGitHub
- ActionCreate ClickUp ticket assigned to the code ownerClickUp
- OutputPost quarantine summary to SlackSlack
What it does
Catches tests that fail then pass on automatic retry (the classic flaky signature), removes them from the blocking suite for exactly one cycle, and makes sure a human owns the fix. The build stays green without anyone silently disabling coverage.
When to use it
Use it when intermittent failures are stalling merges and your team keeps hitting "re-run jobs" instead of fixing the root cause. It turns that reflex into an auditable quarantine with a deadline.
How it works
- 1A GitHub Actions webhook fires when a workflow run completes and includes retry metadata.
- 2A filter keeps only runs where a test failed on the first attempt but passed on retry.
- 3The workflow looks up the test's owner from CODEOWNERS and opens a PR adding a skip annotation tagged with the current cycle.
- 4It creates a ClickUp task assigned to that owner, due in one sprint, linking the PR and the failing run.
- 5A Slack message posts the quarantine summary to the team channel as the final delivery.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.