ENGINEERING
Default-branch coverage-drop PagerDuty alert
Watches default-branch pipelines and, when total coverage falls below a hard floor or drops sharply versus the last run, opens a PagerDuty incident and notes the responsible…
How it runs
The automated pipeline, trigger to output.
- TriggerDefault-branch pipeline succeedsGitLab
- ActionRead coverage + head commitGitLab
- ActionFetch previous run coveragePostgres
- LogicCheck floor and run-over-run drop
- ActionOpen PagerDuty incident on breachPagerDuty
- OutputRecord run coveragePostgres
What it does
This workflow guards your main branch. When a default-branch pipeline reports coverage under a configured floor, or a sudden drop versus the previous successful run, it opens a PagerDuty incident tagged with the offending commit and author so the on-call owner can triage immediately.
When to use it
Use it when coverage on `main` is a release-quality signal you treat as an operational metric. It fits teams that already route engineering alerts through PagerDuty and want a coverage cliff to page someone, not just file a quiet note.
How it works
- 1A GitLab default-branch pipeline-success webhook triggers the flow.
- 2It reads the pipeline's total coverage and the head commit metadata.
- 3It fetches the previous successful run's coverage from Postgres.
- 4A logic step checks both the absolute floor and the run-over-run drop.
- 5On breach it opens a PagerDuty incident with the commit, author, and delta.
- 6It records the new run's coverage in Postgres as the next comparison point.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.