ENGINEERING
Warehouse merged-MR coverage and module deltas nightly
On a nightly schedule, it collects coverage and affected-module data from the day's merged MRs and writes per-module trend rows to Postgres for dashboards and regression alerts.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionList MRs merged in last 24hGitLab
- ActionFetch coverage and changed files per MRGitLab
- ActionCompute per-module coverage and ownershipShell
- OutputUpsert module trend rows to PostgresPostgres
What it does
This workflow builds the historical record behind the inline MR notes. Each night it gathers every merge request that merged that day, pulls each one's final coverage report and affected-module map, and writes one row per module per MR into a Postgres warehouse table. Over time this powers coverage-trend dashboards and lets you spot modules that are quietly losing coverage.
When to use it
Use it once your team is posting coverage and module data on individual MRs and now wants the aggregate view: which modules are trending down, which teams ship the riskiest changes, and how coverage moves week over week.
How it works
- 1A nightly schedule triggers the run.
- 2The workflow queries the GitLab API for MRs merged in the last 24 hours.
- 3For each MR it fetches the final coverage report and changed-file list.
- 4A shell step computes per-module coverage and ownership for every merged MR.
- 5It upserts per-module trend rows into the Postgres warehouse, keyed by date, project, and module.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.