The pull request

On Thursday Finn opens a page titled “Cheer messages v1: text only,” and for the next day and a half, this page is where the feature lives.

It is a pull requestConcept · lights on your mappull requestA formal proposal to merge a branch into main, opened on GitHub, showing every change, discussed in comments, and merged only once approved. “PR” in every conversation. Where a team’s standards actually live., PR in every sentence anyone will ever say about it: a formal proposal that says here is my branch, please pull it into main, and here is every line I touched so you can judge it. Nothing reaches Traversal’s main timeline without one. Nothing. Not Finn’s work, not Priya’s, not the founders’.

Reading the change itself

The page’s centrepiece is the diffConcept · lights on your mapdiffThe line-by-line difference between two versions: removed lines marked with a minus in red, added lines with a plus in green. Reviews read diffs, not whole files.: every removed line in red with a minus, every added line in green with a plus. Nobody re-reads the whole file. The diff is how engineers read each other, and learning to skim one, red out, green in, is the fastest-paying literacy in this entire path.

Then the team reads it, and the reading has a name. code reviewConcept · lights on your mapcode reviewTeammates reading a PR’s diff and commenting, questions, concerns, suggested improvements, before it may merge. The norm at every serious company, for everyone. Quality gate, knowledge-spreader, and style-keeper at once. arrives as comments pinned to lines. A teammate suggests a clearer name for a variable. Sam, wandering in from the platform team, asks what happens if the notification service is down mid-race, which becomes a ticket of its own. Priya asks whether dropped cheers are counted anywhere, and that one stings slightly, in the way of good questions.

None of this is an insult. That is the cultural fact the whole ritual rests on: the review judges the code, never the person, and Finn reviews Priya’s PRs with the same pen.

The blessing

When the comments are answered and the names are clearer, the reviewers grant approvalConcept · lights on your mapapprovalThe reviewer’s formal sign-off on a pull request, usually required before merging is even possible. The moment a change stops being one person’s work and becomes the team’s., the green tick that unlocks the merge button. Two of them, at Traversal, for anything touching delivery. Friday morning, Finn merges, and the cheer feature stops being Finn’s and becomes the team’s, which is the entire point of the ceremony.

Merged is not shipped. Between those two words sit twenty scenes and a small race in the mountains.