pull-requests

# Pull requests Pushing is the middle of the task. The PR is done when the checks pass and a review round produces nothing left to act on. Until then the work is yours. Several bots review this repository, and they re-review on every push. A push therefore always buys a new round, and the round arrives minutes later, after the turn that pushed would otherwise have ended. Stay for it. ## Opening Open it as a draft (`gh pr create --draft`). Fill in `.github/pull_request_template.md` and pass it as the body; `gh pr create` does not apply the template on its own. Keep every section, mark the checklist honestly, and drop only the lines the template says to drop. When the change comes from an issue, link it from the Summary with a closing keyword (`Closes pnpm/pnpm#123`) and then comment on the issue itself. The cross-reference GitHub adds to the issue timeline is silent and says nothing about what was done, so the people waiting on the issue learn nothing from it. The comment carries what they need: that a PR is open, the approach it takes, and whether it covers the whole issue or one part of it. Say so plainly when it is partial. Do not close the issue by hand; the closing keyword does that when the PR merges. ## Draft until the change is worth reading CI runs on a draft here; the reviewers do not. That asymmetry is the whole point of opening as one. A failing lint job, a test you forgot to update, a bug your own review pass catches — in draft each of those costs a push an...