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-05-09 07:00 to 2026-05-16 07: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: 36 of 46 merged MRs (78.3%) showed no visible non-author review comment in GitLab.
  • `CR - Approved` is currently too weak as evidence on its own: 56.5% of merged MRs carried that label without any visible review discussion.
  • Queue health is poor: 72.7% of active open MRs are already older than 48 working hours. The oldest example is adservio/web!2091 at 216.9d open.
  • Visible review capacity is thin and concentrated: only 10 visible review touches were detected in the whole window, and the top 3 reviewers handled 70.0% of them.
  • adservio/frontend is the highest-volume review surface with 17 merged MRs and only 23.5% visible review coverage. adservio/web is the next meaningful flow at 11 merges and 18.2% visible review coverage.
  • MR size is not the main story: median changed files were 4.0, and only 8.7% of merged MRs were above 20 files. Even the slowest merged example, adservio/web!2464, took 14.4d 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 (23.1h created-to-merged), which means the biggest leverage is improving process fidelity rather than pushing for even more raw throughput.
  • With 72.7% of active MRs already stale, the open list is functioning more like inventory than prioritization support. adservio/web!2091 being open for 216.9d 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 70.0% of visible touches, review quality, continuity, and queue health all become sensitive to a very small set of people.
  • The spread between a 4.0-file median MR and a 14.4d longest merged cycle (adservio/web!2464, 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/web 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 Achim Stefan 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/web: 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

  • 36 of 46 merged MRs (78.3%) had no visible non-author review comment in GitLab.
  • 35 of 46 merged MRs (76.1%) carried the `CR - Approved` label.
  • 26 merged MRs (56.5%) were labeled `CR - Approved` without any visible non-author review comment.
  • 8.7% of merged MRs changed more than 20 files, while 2.2% changed more than 50 files.
  • Among MRs with visible review discussion, the median last-author-commit to first-review time was 14.2h.
  • The median last-author-commit to `CR - Approved` time was 23.6h.
  • The top 3 reviewers accounted for 70.0% of visible review touches.
  • 32 of 44 active open MRs (72.7%) were older than 48 working hours.
Merged MRs
Merged MRs inside the analysis window.
46
Open MRs
All currently open group MRs.
49
Active open MRs
Open MRs excluding drafts.
44
Draft open MRs
Open MRs marked draft/WIP.
5
Visible review rate
Merged MRs with at least one visible non-author GitLab comment.
21.7%
Merged without visible review comment
Merged MRs with zero visible non-author comments.
78.3%
CR - Approved label coverage
Merged MRs carrying the CR-approved label.
76.1%
Approval API coverage
Merged MRs with at least one approver in the GitLab approvals API.
15.2%
CR - Approved without visible review comment
CR-approved MRs with no visible non-author comment.
56.5%
Median MR created -> first review
Working time from MR creation to first visible non-author comment.
3.3d
Median last author commit -> first review
Working time from last author commit before review to first visible non-author comment.
14.2h
Median first review -> CR - Approved
Working time from first visible comment to CR-approved label after review start, else merge.
2.7h
Median MR created -> CR - Approved
Working time from MR creation to CR-approved label after review start, else merge.
4.2d
Median last author commit -> CR - Approved
Working time from last author commit before review to CR-approved label after review start, else merge.
23.6h
Median MR created -> merged
Working time from MR creation to merge.
23.1h
Median changed files
Median GitLab `changes_count` value.
4.0
MRs > 5 files
Merged MRs where `changes_count` is above 5.
41.3%
MRs > 10 files
Merged MRs where `changes_count` is above 10.
21.7%
MRs > 20 files
Merged MRs where `changes_count` is above 20.
8.7%
MRs > 50 files
Merged MRs where `changes_count` is above 50.
2.2%
Top 3 reviewer touch share
Share of visible review touches handled by the top 3 reviewers.
70.0%
Active open backlog rate
Non-draft open MRs older than 48 working hours.
72.7%

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

Median MR created -> first review3.3d
Median last author commit -> first review14.2h
Median MR created -> CR - Approved4.2d
Median first review -> CR - Approved2.7h
Median last author commit -> CR - Approved23.6h
Median MR created -> merged23.1h
Achim Stefan3930.0%
Marian Andrei2320.0%
George Murgoci2620.0%
Daniel Onisoru1210.0%
Andrei Alexandru1110.0%
Ioana Ivan1310.0%
adservio/frontend1723.5%88.2%4
adservio/web1118.2%63.6%5
adservio/docgen2/backend520.0%100.0%7
adservio/helm2425.0%50.0%1.0
adservio/social333.3%66.7%22
adservio/uni/backend333.3%100.0%5
adservio/accommodations/backend10.0%0.0%2
adservio/admission/backend10.0%0.0%7
adservio/devops/iac10.0%100.0%4

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!2486[S-7536][ADS-7281][ADS-7465] User profile - check if user is not deleted3/5 Solid2.0h1.6h23.1h
adservio/frontend!1780[S: ADS-6750][ADS-7280]: Ministry Incidents3/5 Solid2.6d2.6h2.6d
adservio/frontend!1805[ADS-7516] Semneaza condica UI responsive improvements3/5 Solid26.5h6.0h44.9h
adservio/helm2!241[dev-obs] add overrides-dev.yaml for observability rollout3/5 Solid10.8h10.0h4.4d
adservio/frontend!1773[ADS-7481] Issues news uni4/5 Strong5.0d18.5h5.0d
adservio/social!15[ADS-7481] Issues news uni4/5 Strong5.0d18.8h5.1d
adservio/docgen2/backend!115[S:6341] [ADS-7400] [ADS-7402] Raport anual 7hills3/5 Solid23.4hn/a26.2h
adservio/uni/backend!191ADS-6823 Modificari in catalogul PDF pentru DPPD2/5 Light4.1d25.0h4.2d
adservio/frontend!1768[S:6341] [ADS-7400] [ADS-7402] Raport anual 7hills3/5 Solid4.1dn/a4.2d
adservio/web!2464[ADS-7346] School config - import & sync3/5 Solid11.5d11.5d14.1d

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 MRs36
With CR Label26
With Approval API6
  • 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 (36 MRs). Click again to collapse.
adservio/web!2475adservio/web[S: ADS-6341][ADS-7401]: Add academic reports configuration to API responseAndrei Dragan2026-05-09Yes
adservio/frontend!1791adservio/frontend[ADS-7433] Numerotarea elevilor in tabelul "topul elevilor"Petronel Pavel2026-05-11Yes
adservio/helm2!243adservio/helm2deploy social module on tuiasi clusterRojan Shrestha2026-05-11YesYes
adservio/frontend!1790adservio/frontend[ADS-7347] [BUG] - Imposibilitate modificare data sesiuneAchim Stefan2026-05-11Yes
adservio/uni/backend!192adservio/uni/backend[ADS-7347] Actualizare Data examinare pentru grupa de restanțieriAndrei Alexandru2026-05-11Yes
adservio/frontend!1794adservio/frontend[ADS-7549]: Login provider exclude cookiebot for mobileIoana Ivan2026-05-11Yes
adservio/accommodations/backend!66adservio/accommodations/backend[ADS-7539] student retry payment after 10 minIonut Ciolan2026-05-11
adservio/docgen2/backend!117adservio/docgen2/backend[ADS-7352] Numarul de telefon al tutorelui legal nu este preluat in catalogul PDFPetronel Pavel2026-05-11Yes
adservio/frontend!1797adservio/frontend[hotfix-student-invoice-payment] added time window checkEdgar Alexa2026-05-12
adservio/web!2489adservio/web[ADS-7448] Delete and recover grades code refactorIonut Ciolan2026-05-12Yes
adservio/web!2485adservio/web[ADS-7525] Add message code refactorIonut Ciolan2026-05-12Yes
adservio/web!2474adservio/web[ADS-6750]: Add county-based filtering to incident reportsAndrei Dragan2026-05-12Yes
adservio/devops/iac!25adservio/devops/iacAdd persistent 5GB /home volume for bastion + import prod scratch volumeRojan Shrestha2026-05-12YesYes
adservio/frontend!1796adservio/frontend[ADS-7548]: Filter grade types on init alsoIoana Ivan2026-05-13Yes
adservio/docgen2/backend!119adservio/docgen2/backend[ADS-7499] Lipsa titulaturii in josul paginii pe catalogul pdfAchim Stefan2026-05-13Yes
adservio/web!2488adservio/web[S: ADS-7548][ADS-7562]: Add force update endpoint for grade systems configurationAndrei Dragan2026-05-13Yes
adservio/admission/backend!138adservio/admission/backendRemove sex and dateOfBirth columns from applications tableGeorge Murgoci2026-05-13
adservio/frontend!1804adservio/frontendfix for apply to sessionsGeorge Murgoci2026-05-13
adservio/web!2490adservio/web[HOTFIX] Log errors fixedIonut Ciolan2026-05-13
adservio/web!2491adservio/web[ADS-7576] school config - removed general students settings for uniIonut Ciolan2026-05-13
adservio/web!2492adservio/web[ADS-4638] Grades rankings - grades per class chartIonut Ciolan2026-05-13
adservio/social!18adservio/social[ADS-7226]: Add tests for NewsPaul Tanasuca2026-05-13
adservio/helm2!244adservio/helm2Add tests for socialDaniel Onisoru2026-05-13
adservio/docgen2/backend!118adservio/docgen2/backend[ADS-6823]: Modificari in catalogul PDF pentru DPPDIuliana Gugeanu2026-05-14Yes
adservio/frontend!1795adservio/frontend[ADS-6823]: Modificari in catalogul PDF pentru DPPDIuliana Gugeanu2026-05-14Yes
adservio/frontend!1801adservio/frontend[ADS-7546]:Update ministry incidents mapIoana Ivan2026-05-14YesYes
adservio/frontend!1808adservio/frontend[ADS-7587] Noi carduri in modulul de documenteAchim Stefan2026-05-14Yes
adservio/web!2494adservio/web[HOTFIX] check subscription - removed teacher exceptionIonut Ciolan2026-05-14
adservio/frontend!1799adservio/frontend[ADS-7555] Fix period selection for grades and absencesPetronel Pavel2026-05-15Yes
adservio/docgen2/backend!120adservio/docgen2/backend[ADS-4257] In catalogul PDF al claselor volumul de la numarul matricol nu este bine incadratPetronel Pavel2026-05-15YesYes
adservio/helm2!245adservio/helm2[ads-7483] Loosen web readiness probe + stabilise HPA scale-downRojan Shrestha2026-05-15YesYes
adservio/uni/backend!194adservio/uni/backend[ADS-7526][ADS-7573][ADS-6981]: Some FixesAndrei Alexandru2026-05-15YesYes
adservio/social!19adservio/socialsocial-tests-envPaul Tanasuca2026-05-15Yes
adservio/frontend!1807adservio/frontend[ADS-7510] UI Enhancement for Single-Image PostsAlex Murarescu2026-05-15Yes
adservio/frontend!1806adservio/frontendSync select container size fixAchim Stefan2026-05-15Yes
adservio/frontend!1812adservio/frontend[ADS-6981] Adaugare permisiune adaugare/editare/stergere grupaAchim Stefan2026-05-15Yes

Oldest Active Open MRs (> 48 Working Hours)

adservio/web!2091adservio/webAndrei Dragan216.9d5
adservio/devops/site-sentry!11adservio/devops/site-sentryDaniel Onisoru200.3d0
adservio/helm2!137adservio/helm2Raul Popovici192.9d0
adservio/services/websocket!8adservio/services/websocketRaul Popovici189.9d0
adservio/services/videothumb!5adservio/services/videothumbRaul Popovici189.9d0
adservio/services/fet-generator!9adservio/services/fet-generatorRaul Popovici189.9d0
adservio/ai/backend!62adservio/ai/backendRobert90.9d0
adservio/frontend!1556adservio/frontendGeorge Murgoci81.6d0
adservio/web!2344adservio/webGeorge Murgoci80.7d0
adservio/library/backend!26adservio/library/backendRaul Popovici60.8d0
adservio/web!2464adservio/webIonut Ciolan14.4d71
adservio/web!2474adservio/webAndrei Dragan9.4d120
adservio/web!2475adservio/webAndrei Dragan7.5d100
adservio/frontend!1773adservio/frontendAlex Murarescu5.2d203
adservio/social!15adservio/socialAlex Murarescu5.2d363
adservio/uni/backend!191adservio/uni/backendFrancisc Gabriel Virlan4.8d81
adservio/frontend!1780adservio/frontendIoana Ivan4.6d642
adservio/frontend!1768adservio/frontendDron Gabriel4.5d433
adservio/helm2!241adservio/helm2Rojan Shrestha4.4d12
adservio/frontend!1799adservio/frontendPetronel Pavel2.9d30

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.