DEVOPS
Detect Flaky Tests from CI Reruns and Open Linear Tickets
Watches GitHub Actions test results and flags any test that passed on rerun after failing on the same commit.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub workflow_run completedGitHub
- ActionFetch job annotations and rerun historyGitHub
- LogicFailed then passed on same SHA?
- ActionSearch Linear for existing flaky ticketLinear
- ActionCreate labeled Linear issue if newLinear
- OutputPost ticket link as GitHub commit statusGitHub
What it does
This workflow catches intermittent test failures the moment CI proves them flaky — a test that failed, then passed on a rerun against the identical commit SHA. Each newly confirmed flaky test gets a deduplicated Linear ticket so it stops silently eroding trust in the pipeline.
When to use it
Run this when your CI has rerun-on-failure enabled and red builds turn green without a code change. It converts the noise of "just hit rerun" into accountable, tracked work instead of letting flaky tests pile up unowned.
How it works
- 1A GitHub workflow_run completion event fires when a test job finishes.
- 2The flow fetches the job's annotations and rerun history for that commit SHA.
- 3A logic step compares attempts: if the same test failed then passed on the same SHA, it is flagged flaky; otherwise the run is ignored.
- 4It checks Linear for an existing open ticket matching the test's fully-qualified name to avoid duplicates.
- 5If none exists, it creates a Linear issue with the `flaky-test` label, failure rate, and a link to the failing run.
- 6The new ticket URL is posted back as a GitHub commit status for visibility.
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
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-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…
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.
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.
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.
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.