ENGINEERING

Open a skip-annotation PR when a quarantined test recurs

When an already-quarantined test fails again in CI, this opens a draft GitHub PR adding a skip annotation with a tracking link.

CategoryEngineering
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub check_run failed webhookGitHubGitHub
  • LogicMatch failure against quarantine list
  • ActionInsert skip annotation with tracking linkGitHubGitHub
  • ActionOpen draft skip PRGitHubGitHub
  • OutputPing assigned owner in SlackSlack

What it does

It closes the loop on tests already tagged flaky: when one of them fails yet again, it stops merely re-noting the flake and instead opens a draft PR that adds a skip/quarantine annotation to the test, referencing the tracking issue. The pipeline gets unblocked while the real fix stays owned and visible.

When to use it

Use it after you have a quarantine list and want to automate the mechanical step of skipping a known-flaky test the moment it re-breaks a build, without a human babysitting CI.

How it works

  1. 1A GitHub `check_run` failure webhook fires when a CI check fails.
  2. 2A logic step checks whether the failing test is already on the quarantine list (label or tracking issue exists).
  3. 3If it is, the test file is fetched and the runner-appropriate skip annotation is inserted with a comment linking the tracking issue.
  4. 4A draft GitHub PR is opened with that change for the owner to review and merge.
  5. 5The assigned owner is pinged in Slack with the PR link and recurrence count.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.