Code & Collaboration
$definepull-request--plain-english
TLDRA proposed change, put up for review.
A pull request is plating a dish and sliding it onto the pass.
You cooked on a branch. main is the dining room. You do not walk the pan to the table yourself. You set the plate on the pass: here is the diff, line by line. Someone tastes it. CI runs the tests. If it is food, you merge.
The name is leftover kitchen slang. You are asking the project to pull your work in. People say PR.
The pass exists so the dining room stays open
"I changed something" and "I proposed a change, on the record" are different jobs. The gap is why main still boots at noon.
On GitHub the PR is also the front door for strangers. They fork, fix the bug, and plate a dish they do not own. You never handed them the keys. The review is the taste.
At a hackathon the taster is often you, tomorrow. Write the PR like a note to a tired teammate. Include the why, not just the files. An agent via MCP can open the PR too. You still glance at the plate before it leaves the pass.
The conversation stays taped to the plate
Months later you can open that exact change and see what moved, who signed, and why. A commit is a page. A PR is the talk taped to the page. That is useful when the CLI scaffold from npx create-hackhaton-space-stack@latest grew three features overnight and nobody remembers which one broke auth.
What this unlocks
A dining room that only serves food someone looked at.
Plate it. Let someone taste it. Then it is dinner.
