ENGINEERING

Weekly GitLab review-load fairness digest

Once a week, computes per-reviewer review volume, turnaround time, and current backlog from the assignment ledger.

CategoryEngineering
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionAggregate per-reviewer stats from ledgerPostgreSQLPostgres
  • LogicRank reviewers and flag overload
  • ActionEnrich flagged entries with open MR titlesGitLabGitLab
  • OutputPost fairness digest to SlackSlack

What it does

This workflow turns the raw assignment history into a weekly leaderboard. It aggregates how many MRs each reviewer handled, their median time-to-first-review, and how deep their current backlog is, then renders a clear digest that highlights who is overloaded and who has spare capacity.

When to use it

Use it when you want a recurring, data-backed view of review fairness rather than gut feel. It is ideal for an engineering manager who runs weekly health checks and wants the numbers handed to them automatically.

How it works

  1. 1A weekly schedule trigger fires at a set time.
  2. 2The workflow queries Postgres for assignment counts, turnaround times, and open backlog per reviewer over the trailing seven days.
  3. 3A logic step ranks reviewers and flags anyone above the overload threshold or with stale backlog.
  4. 4It pulls current open-MR titles from GitLab to enrich the flagged entries.
  5. 5It formats a ranked digest with per-person stats and callouts.
  6. 6The digest posts to the engineering-leads Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect GitLabRepos, MRs, pipelines, registry.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.