DEVOPS
Comment quarantine decision on PRs touching flaky tests
When a pull request modifies a test file that is currently quarantined, posts a PR comment explaining the test is flaky, links the tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull_request opened or synchronizedGitHub
- ActionDiff changed files against quarantine manifestGitHub
- LogicQuarantined test re-enabled without approval label?
- ActionComment with flake history and Linear issue linkGitHub
- OutputSet gating commit status on the PRGitHub
What it does
Guards the quarantine list at review time. When a pull request changes a test file that appears on the active quarantine manifest, the flow comments on the PR with the test's flake history and tracking issue, and blocks accidental un-quarantining unless a maintainer explicitly approves it with a label.
When to use it
Use this when developers keep re-enabling known-flaky tests in unrelated PRs, reintroducing red builds. It surfaces the quarantine context exactly where the change happens and enforces a deliberate decision.
How it works
- 1A GitHub `pull_request` synchronize event fires when a PR is opened or updated.
- 2The flow diffs the PR's changed files against the quarantine manifest.
- 3A branch checks whether any quarantined test was touched, and whether the diff re-enables it.
- 4If a quarantined test is being re-enabled without the `approve-unquarantine` label, it requests changes via a PR comment linking the Linear tracking issue.
- 5If the change is safe, it posts an informational comment with the test's flake history.
- 6The final step sets a commit status so merge is gated until the decision is acknowledged.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.