How MemoAgent decides a review is stuck
A full working day in the reviewer's own time zone, checked against GitHub before anyone hears. Here is what counts, and what doesn't.
MemoAgent calls a review stuck after it has waited a full working day. Here is how it counts, and why each rule is there.
Working days, on the reviewer's clock
The clock runs Monday to Friday, in the reviewer's own time zone, taken from their Slack profile. Weekends don't count, so a review requested on Friday afternoon isn't stuck by Monday morning. A reviewer in another time zone is counted on their own clock, because they are the one who has to act.
Clocks that change
When clocks change for daylight saving, a day can be 23 or 25 hours long. MemoAgent counts real hours, so a review doesn't stall an hour early or late that week.
Asking again starts over
If the author asks the same reviewer again, the wait restarts from the new request.
Requested changes
When a reviewer asks for changes, the author has two working days, in the author's time zone, to push a commit, get an approval or ask again. A comment on its own doesn't answer a change request, just as on GitHub. After that, it goes on the author's list under Your priorities.
Merge conflicts count at once
If GitHub says a pull request can't be merged cleanly, it goes on the author's list straight away.
Checked again before anyone hears
Webhooks can arrive late or out of order. Before a Brief, an alert or a nudge goes out, MemoAgent reads the pull request from GitHub again, and anything already fixed drops out. Each night it also repairs what a missed webhook left behind.
Who hears about it
The author hears about their stuck pull request in their Brief and, during their working hours, within 15 minutes. The reviewer sees it in their own Brief, under Waiting on you. Nobody else is told, and a reviewer gets a nudge only when the author asks for one.