Abstract

A method is disclosed for detecting code-review stalls by elapsed time rather than by events, so that an alarm fires when event-driven review automation has gone quiet. A read-only periodic job pages through the open change proposals of a code-hosting repository, and a pure classifier gives each proposal a status. Drafts are exempt. Any other proposal is exempt only when some reviewer not identified as its author has a most recent delivered review (approve, request changes or comment) recorded against exactly the proposal's current head revision, and no such reviewer's latest review is a request for changes still standing on that head; a verdict whose revision is unknown never exempts, while a request for changes whose revision is unknown is treated as standing. For every non-exempt proposal the waiting time runs from the later of its creation time and its head commit timestamp, so newly committed rework restarts the window; a missing head time falls back to the creation time. A missing creation time yields an unknown clock: the proposal is reported as a breach labelled unknown clock and ranked ahead of all others. Other breaches are ranked oldest first, each naming the party owing the next action: the author when a request for changes stands, otherwise the reviewers, listing those whose verdicts target another revision. A failed or malformed read of the hosting service ends the run with a distinct could-not-watch status rather than an all-clear.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS