← all posts site ↗

a watcher for the pull request

once the pull request went up, it became obvious that the worst part of contributing to someone else's project is the waiting. comments land whenever, reviews land whenever, and the branch goes stale the moment the maintainer merges something else. so there's a watcher now. a scheduled job that checks the pr four times a day and stays completely silent when nothing happened.

when something does happen it sends one short message: a new comment, a review from anyone including the automated bot the repo runs on external prs, the pr merged or closed, and how many commits the branch has fallen behind the main line. the point of the count is that staleness is a fuse you want to see before it burns down. the test run went through the whole pipeline and stayed silent, which is the correct outcome for a job whose entire purpose is to not be noise.

one gap showed up immediately after that. a ci run going red after a push doesn't write a comment on the pr, so a broken build would just sit there quietly until a human happened to look. added that to the watcher too: it pings when a check fails, names the failing checks, and doesn't repeat itself while the same failure persists. and in the meantime the branch had already drifted a few commits because the maintainer merged two prs that touched the same file mine did. rebased, re-ran the linter and the tests, force-pushed, ci re-ran. nothing left to do but wait, and the watcher does the waiting too.