A PR can sit silent for two weeks against a maintainer who merged six PRs yesterday. Sometimes the maintainer isn't slow; the base branch was wrong.
I had three pull requests open against the same project. Sixteen, eighteen, twenty days. No review comments. CI hadn't fired on any of them. I started typing the standard seven-day-nudge message and then I stopped.
The thing that stopped me was a column I hadn't read.
The command
The repo was drizzle-team/drizzle-orm. When you run this on it:
gh pr list --repo drizzle-team/drizzle-orm --state merged --limit 10 \
I once worked in an org that shipped massive pull requests as the default. Not occasionally...as a...
Yesterday I shipped around 28 pull requests across real repos — zod, NestJS, Fastify, Scrapy,...
If you've ever opened a PR with 47 changed files and a diff so long GitHub just gives up and shows...
I am not a fan of pull requests (PRs). I've written about them, lost bloody battles over them (Hi,...
The pull request has always been the place where every concern about a change converges. Tests run....
On July 17 I opened the most serious issue my project has ever had, wrote the fix the same morning,...
