GitLab-backed analysis

Adservio Code Review Analysis

A read-only analysis of recent merge request review behavior in GitLab, focused on visible review discussion, reviewer distribution, queue health, MR size, and traceability gaps.

Period: 2026-07-18 07:00 to 2026-07-26 10:00
Primary source: GitLab merge request metadata, notes, labels, commits, and approvals endpoints.

Bottom line: review throughput is not the main risk here; traceability and queue hygiene are. The team is still merging code, but most merges leave no durable visible review trail and the open queue is overwhelmingly stale.

What Matters

  • Traceability is the clearest control gap: 26 of 30 merged MRs (86.7%) showed no visible non-author review comment in GitLab.
  • `CR - Approved` is currently too weak as evidence on its own: 46.7% of merged MRs carried that label without any visible review discussion.
  • Queue health is poor: 82.3% of active open MRs are already older than 48 working hours. The oldest example is adservio/web!2091 at 268.3d open.
  • Visible review capacity is thin and concentrated: only 5 visible review touches were detected in the whole window, and the top 3 reviewers handled 100.0% of them.
  • adservio/frontend is the highest-volume review surface with 10 merged MRs and only 10.0% visible review coverage. adservio/helm2 is the next meaningful flow at 9 merges and 0.0% visible review coverage.
  • MR size is not the main story: median changed files were 2.5, and only 10.0% of merged MRs were above 20 files. Even the slowest merged example, adservio/accommodations/backend!75, took 12.8d with 7 changed files, so the dominant problem still looks like review discipline and queue ownership rather than consistently oversized MRs.

Leadership Analysis

  • The operating rhythm is serviceable at the median (4.3h created-to-merged), which means the biggest leverage is improving process fidelity rather than pushing for even more raw throughput.
  • With 82.3% of active MRs already stale, the open list is functioning more like inventory than prioritization support. adservio/web!2091 being open for 268.3d is a strong sign that ownership and review handoffs are not being actively reset.
  • Reviewer concentration is now a resilience issue, not just a fairness issue. When the top 3 reviewers carry 100.0% of visible touches, review quality, continuity, and queue health all become sensitive to a very small set of people.
  • The spread between a 2.5-file median MR and a 12.8d longest merged cycle (adservio/accommodations/backend!75, 7 changed files) suggests a few ownership-heavy exceptions are dragging on outside normal flow. Those should be managed as explicit escalations, not left to age inside the common queue.

Recommended Actions

  • Make one durable review artifact mandatory before merge: a substantive non-author GitLab review comment, a recorded approval, or both. A label alone should no longer count as sufficient evidence. The approval API coverage is also low, so the fix should include tooling or policy that leaves an auditable trace by default.
  • Run a stale-MR reset on anything older than 48 working hours: close abandoned work, re-confirm owner and reviewer on the rest, and turn the open list back into a real queue instead of a parking lot. Start with adservio/web!2091 and the rest of the oldest backlog because their age now obscures whether they are still real priorities.
  • Put adservio/helm2 under explicit review guardrails for the next cycle. It combines enough volume with weak visible review coverage, which makes it the best place to tighten the process and see impact quickly.
  • Broaden the reviewer bench beyond Dragoș Ivan and the current small reviewer set. The present concentration is a continuity risk and will keep queue health fragile when one person is away.

Improvement Ideas

  • Set explicit operating standards for the next quarter: require one auditable peer-review artifact before merge, target first review inside one working day for active MRs, and keep the stale active backlog below 15%. What gets measured this clearly is far more likely to improve.
  • Run a four-week process experiment on adservio/helm2: dedicated reviewer-of-the-week coverage, explicit reviewer assignment at MR creation, and a lightweight weekly audit of silent merges. It is the highest-yield place to test whether better ownership changes the data.
  • Create a reviewer rotation with named backup coverage for the busiest repos. Good review systems depend on redundancy, not heroics, and rotation is the fastest way to lower reviewer bus factor without slowing delivery.

Supporting Evidence

  • 26 of 30 merged MRs (86.7%) had no visible non-author review comment in GitLab.
  • 17 of 30 merged MRs (56.7%) carried the `CR - Approved` label.
  • 14 merged MRs (46.7%) were labeled `CR - Approved` without any visible non-author review comment.
  • 10.0% of merged MRs changed more than 20 files, while 3.3% changed more than 50 files.
  • Among MRs with visible review discussion, the median last-author-commit to first-review time was 3.1d.
  • The median last-author-commit to `CR - Approved` time was 3.1d.
  • The top 3 reviewers accounted for 100.0% of visible review touches.
  • 51 of 62 active open MRs (82.3%) were older than 48 working hours.
Merged MRs
Merged MRs inside the analysis window.
30
Open MRs
All currently open group MRs.
74
Active open MRs
Open MRs excluding drafts.
62
Draft open MRs
Open MRs marked draft/WIP.
12
Visible review rate
Merged MRs with at least one visible non-author GitLab comment.
13.3%
Merged without visible review comment
Merged MRs with zero visible non-author comments.
86.7%
CR - Approved label coverage
Merged MRs carrying the CR-approved label.
56.7%
Approval API coverage
Merged MRs with at least one approver in the GitLab approvals API.
23.3%
CR - Approved without visible review comment
CR-approved MRs with no visible non-author comment.
46.7%
Median MR created -> first review
Working time from MR creation to first visible non-author comment.
4.0d
Median last author commit -> first review
Working time from last author commit before review to first visible non-author comment.
3.1d
Median first review -> CR - Approved
Working time from first visible comment to CR-approved label after review start, else merge.
0.8h
Median MR created -> CR - Approved
Working time from MR creation to CR-approved label after review start, else merge.
4.1d
Median last author commit -> CR - Approved
Working time from last author commit before review to CR-approved label after review start, else merge.
3.1d
Median MR created -> merged
Working time from MR creation to merge.
4.3h
Median changed files
Median GitLab `changes_count` value.
2.5
MRs > 5 files
Merged MRs where `changes_count` is above 5.
26.7%
MRs > 10 files
Merged MRs where `changes_count` is above 10.
10.0%
MRs > 20 files
Merged MRs where `changes_count` is above 20.
10.0%
MRs > 50 files
Merged MRs where `changes_count` is above 50.
3.3%
Top 3 reviewer touch share
Share of visible review touches handled by the top 3 reviewers.
100.0%
Active open backlog rate
Non-draft open MRs older than 48 working hours.
82.3%

These headline timing medians bring back the anchor-to-anchor numbers directly, using working time with weekends excluded.

Median MR created -> first review4.0d
Median last author commit -> first review3.1d
Median MR created -> CR - Approved4.1d
Median first review -> CR - Approved0.8h
Median last author commit -> CR - Approved3.1d
Median MR created -> merged4.3h
Dragoș Ivan2340.0%
Marian Andrei2540.0%
Ioana Ivan1120.0%
adservio/frontend1010.0%80.0%3.0
adservio/helm290.0%33.3%1
adservio/web560.0%60.0%4
adservio/billing/backend20.0%100.0%6.0
adservio/accommodations/backend10.0%0.0%7
adservio/services/notifications10.0%0.0%112
adservio/social10.0%100.0%35
adservio/uni/backend10.0%0.0%7

Visible Review Discussion MRs

Compact by default: key CR metrics stay visible, and each row expands inline for the full audit trail. The table starts sorted by Last Commit -> First Review.

Details
adservio/web!2660[ADS-8315]: Remove sanID from activity functionality2/5 Light3.1h0.2h4.5h
adservio/web!2646[ADS-8262] Responsive conduită / listă elevi2/5 Light3.2d2.1d3.2d
adservio/frontend!2026[ADS-7343] [Stiri] - Distribuie Updates2/5 Light5.1d4.0d5.1d
adservio/web!2650[ADS-7343] [Stiri] - Distribuie Updates4/5 Strong4.8d4.8d4.9d

No Visible Review Comment Audit

These merged MRs had no visible non-author GitLab comment under the current heuristic. Use this section to audit whether the gap is a real review-process issue or a GitLab traceability issue.

Total MRs26
With CR Label14
With Approval API5
  • Open the MR link and check the Overview tab for CR - Approved and any approval widget signal.
  • Check Activity / Discussions for real human reviewer comments.
  • If you only see system notes, merge notes, mentions, or bot activity, it stays in this audit set.
  • If you find a genuine reviewer comment from someone other than the author, treat that MR as a false positive of this heuristic.
full audit table (26 MRs). Click again to collapse.
adservio/helm2!315adservio/helm2ads-8251 admission-api interim mitigation: enable HPA min 2 max 4 and set...Rojan Shrestha2026-07-20
adservio/helm2!317adservio/helm2ads-7941 enable send_resolved and status-aware slack titles for alert recovery notificationsRojan Shrestha2026-07-20
adservio/helm2!319adservio/helm2tune TraefikServiceHighLatency: add request-rate guard, widen to 5m window and...Rojan Shrestha2026-07-20
adservio/helm2!320adservio/helm2ads-8251 move admission-api resources under api so KEDA cpu trigger validatesRojan Shrestha2026-07-20
adservio/web!2654adservio/web[ADS-8282] Add max lengthMarian Andrei2026-07-20Yes
adservio/helm2!321adservio/helm2ads-8251 raise admission-api memory to 512Mi/1Gi to stop node heap-OOM crashloopRojan Shrestha2026-07-20
adservio/uni/backend!232adservio/uni/backend[hotfix-laravel-log] Add structured logging to Laravel UniCatalin Cojan2026-07-20Yes
adservio/helm2!322adservio/helm2ads-8251 admission-api: fix memory heap-OOM crashloop and disable misfiring HPARojan Shrestha2026-07-20
adservio/web!2645adservio/web[ADS-8120] Parenting profile updatesMarian Andrei2026-07-21
adservio/helm2!323adservio/helm2fix tempo trace retention to 3 days via correct tempo.retention key...Rojan Shrestha2026-07-21YesYes
adservio/helm2!324adservio/helm2ads-8266 split Traefik service latency into 500ms warning and 1s critical over 5mRojan Shrestha2026-07-21YesYes
adservio/helm2!325adservio/helm2[UNI-CORE] Add jwt-globalAndrei Alexandru2026-07-21Yes
adservio/frontend!2033adservio/frontendfix Course Syllabus evaluation readiness raceValentin Pal2026-07-22Yes
adservio/frontend!2032adservio/frontendtest: synchronize Uni Files session readinessValentin Pal2026-07-23Yes
adservio/services/notifications!10adservio/services/notifications[S: ADS-6159][ADS-8239]: Notifications flow refactor - Local CacheDragoș Ivan2026-07-23
adservio/billing/backend!263adservio/billing/backend[ads-6064] - new client invoices exportGeorge Murgoci2026-07-24Yes
adservio/frontend!2036adservio/frontend[ADS-6064] - new clients export updatesGeorge Murgoci2026-07-24Yes
adservio/frontend!2037adservio/frontend[ADS-8247] - swapped first/last name in candidate cerate account flowGeorge Murgoci2026-07-24
adservio/frontend!2038adservio/frontend[ADS-8247]-fixes for first/last name swapGeorge Murgoci2026-07-24Yes
adservio/frontend!2035adservio/frontend[ADS-8316] Load eligible services for Groups marksValentin Pal2026-07-24Yes
adservio/billing/backend!262adservio/billing/backend[ADS-8316] Filter services by group eligibilityValentin Pal2026-07-24Yes
adservio/accommodations/backend!75adservio/accommodations/backend[ADS-8153] Fix large student balance PDF exportValentin Pal2026-07-24
adservio/frontend!2042adservio/frontend[ads-8247] - reorder fields in create candidate accountGeorge Murgoci2026-07-24Yes
adservio/social!36adservio/social[ADS-7343] [Stiri] - Distribuie UpdatesAlex Murarescu2026-07-24YesYes
adservio/frontend!2039adservio/frontend[ADS-8315]: Remove sanID from activity functionalityIoana Ivan2026-07-24
adservio/frontend!2040adservio/frontend[ADS-8322]: Tabel Studenti - afisare dinamica atribute custom, ascunse by defaultDana Mihaela Maritca2026-07-24YesYes

Oldest Active Open MRs (> 48 Working Hours)

adservio/web!2091adservio/webAndrei Dragan268.3d5
adservio/helm2!137adservio/helm2Raul Popovici244.3d0
adservio/services/websocket!8adservio/services/websocketRaul Popovici241.3d0
adservio/services/videothumb!5adservio/services/videothumbRaul Popovici241.3d0
adservio/services/fet-generator!9adservio/services/fet-generatorRaul Popovici241.3d0
adservio/ai/backend!62adservio/ai/backendRobert142.3d0
adservio/frontend!1556adservio/frontendGeorge Murgoci133.0d0
adservio/web!2344adservio/webGeorge Murgoci132.1d0
adservio/library/backend!26adservio/library/backendRaul Popovici112.2d0
adservio/subscriptions/backend!103adservio/subscriptions/backendEdgar Alexa110.2d4
adservio/accommodations/backend!75adservio/accommodations/backendValentin Pal12.8d70
adservio/frontend!2026adservio/frontendAlex Murarescu6.2d392
adservio/social!36adservio/socialAlex Murarescu6.2d350
adservio/web!2650adservio/webAlex Murarescu4.9d54
adservio/web!2645adservio/webMarian Andrei4.9d40
adservio/web!2646adservio/webPetronel Pavel3.2d21
adservio/frontend!2032adservio/frontendValentin Pal36.4h10
adservio/services/notifications!10adservio/services/notificationsDragoș Ivan28.9h1120
adservio/helm2!315adservio/helm2Rojan Shrestha28.1h20
adservio/helm2!317adservio/helm2Rojan Shrestha19.5h20

Methodology And Limits

  • This report uses visible non-author GitLab comments as the strongest review-start proxy.
  • GitLab approval API coverage is shown separately; missing approval API data should be read as traceability gap, not proof that no approval happened.
  • Review completion uses the first `CR - Approved` label-add event after review starts when GitLab label history provides one; otherwise it falls back to merge time.
  • Last-author-commit metrics use the latest non-merge MR commit authored by the MR author strictly before review starts.
  • Timing metrics in this report exclude Saturday and Sunday hours using the Europe/Bucharest calendar.
  • Review-quality scoring is heuristic: it rewards visible substantive comments, multiple reviewers, and post-review pushes, and it penalizes large MRs with shallow visible discussion.
  • `Active open backlog rate` excludes draft MRs and uses a > 48 working-hour age threshold.
  • Open MR backlog age is a queue-health signal, not proof that every old open MR is actively waiting for review right now.