ENGINEERING
Block flaky GitLab MR failures and notify the author in Discord
When a GitLab merge request pipeline fails, retries the failing job once, and if it passes on retry posts a Discord alert tagging the MR author with the flaky-test name so they…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline failsGitLab
- ActionRetry the failed job onceGitLab
- LogicPass on retry = flaky, else real break
- ActionLabel and comment quarantine on the MRGitLab
- OutputNotify MR author in DiscordDiscord
What it does
Gives GitLab MR authors instant, accurate feedback when their pipeline failure was flaky rather than their fault. It retries the failed job, detects pass-on-retry, and tells the author directly in Discord which test flaked, so they stop guessing whether to re-run.
When to use it
Use on teams running GitLab CI where intermittent failures stall merge requests. Lighter-weight than full quarantine automation: it focuses on fast author notification and a quarantine flag, keeping humans in the loop on the fix decision.
How it works
- 1A GitLab pipeline failure webhook fires for a merge request.
- 2The flow retries the single failed job via the GitLab API.
- 3A branch checks the retry: still failing means a genuine break and the flow stops; passing means flaky.
- 4For flaky cases, it adds a quarantine label and comment to the merge request.
- 5It resolves the MR author handle.
- 6It posts a Discord message in the team channel tagging the author with the flaky test name and retry evidence.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect DiscordCommunity channels + voice + bots.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.