ENGINEERING
Auto-Skip Quarantined Flaky Tests on GitLab MRs
When a GitLab pipeline fails only on tests already known to be flaky, the bot marks those as skipped and posts a green-light note on the merge request.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline failedGitLab
- ActionPull failed tests from JUnit reportGitLab
- LogicSplit known-flaky vs genuine failures
- ActionFile untracked flaky tests in LinearLinear
- OutputPost advisory-pass or keep MR blockedGitLab
What it does
This workflow unblocks merge requests that fail solely because of tests already on the flaky list. It cross-references the failing tests in a GitLab pipeline against a registry of known-flaky tests, skips (quarantines) matches, and tells reviewers the failure is non-blocking. Any flaky test not yet tracked is filed as a Linear issue for follow-up.
When to use it
Use this when known-flaky tests repeatedly block otherwise-clean MRs and developers waste time re-running pipelines. It keeps real failures blocking while letting quarantined ones pass.
How it works
- 1A GitLab pipeline `failed` event triggers the workflow.
- 2The bot pulls the failed test names from the pipeline's JUnit report via the GitLab API.
- 3A decision step splits failures into known-flaky (in the registry) versus genuine failures.
- 4If every failure is known-flaky, it posts a note on the merge request marking the pipeline as advisory-pass; if any genuine failure exists, it leaves the MR red.
- 5Flaky tests missing from the tracker get a Linear issue created with the pipeline link and occurrence timestamp.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 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 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.