Dan reads every pull request, reruns the flaky test, nudges the reviewer who forgot, and keeps one pinned comment saying exactly what's blocking. You keep the merge button.
Red CI, nothing wrong. Someone has to notice and click rerun.
Requested Monday. It's Thursday. Nobody wants to be the one who pings.
Forty comments deep. Is it ready? Scroll and find out.
Every pull request, the moment it opens. Nothing ships without him reading it first.
Flaky test? Rerun before you see red. Real failure? He reproduces it first (no repro, no patch), then fixes and validates.
Reviewer gone quiet? After three days Dan mentions them, cheerfully, and offers to find a stand-in. The awkward ping is his job now.
One pinned comment tracks every gate and the single thing still in the way, then announces the moment it's truly ready. He never merges.
Dan edits a single readiness dashboard on every PR: every gate, and the one thing still blocking. No scrolling through forty stale bot comments.
Advisory only. He judges; he never merges.
No commands, no syntax. Mention @hamster-dan in a comment and say what you want, like you would to a colleague. A small, furry, extremely available colleague.
One thing: a rollback for the migration. Everything else is green.
Snoozed till Monday 9:00. I respect a snooze. I do not forget a snooze.
Done. Ana's requested, Kika's off the hook. Anything risky I'll stage and ask you first.
Straight from the demo repo. Dan's beef is with broken tests and slow calendars, never with you.