Skip to content
Codebase · Reviewing a change5 pages

Reviewing a change

Partly built

What a change shows you before it lands, and what you can do with it.

Codebase opens on what needs your attention: four counted groups, Waiting on you, Ready to ship, Blocked and Landed. Each change is a card with a title, the project it belongs to, who or which agent made it, and the reason it is in that group, in words (“Changes the behaviour of 1 function”).

Opening a change

The page for one change answers a single question: may this go in? It starts with the verdict and the reason for it, then a one-line summary of the checks (type check, tests, permissions). Below that:

  • What changed, as sentences. Click one to see the code before and after.
  • Other functions follow along automatically. Definitions that use something the change edits are updated for you. They are counted, not listed one by one, and folded away until you ask.
  • What else is affected.
  • Copy as a git patch. The change leaves Codebase as an ordinary patch you apply with git.

A section called Technical details holds the exact parts, hashes, signatures and the full text difference, for when you want them. The rest of the page uses none of those words.

How a verdict is reached

The verdict is worked out from the facts the planner finds, never from what an agent wrote about its own change. Ready to ship means the planner judged the change low risk and its dry run, on a scratch copy, did not fail. Blocked means the official version changed the same definition differently, or the change needs another one first.

Text that comes from a branch is shown as plain text. It is data to read; it never decides anything.

What is not built

Approve is shown but disabled, and says why: there are no rules for a project yet, so nothing can actually be shipped. Landed stays empty until something can land. Tests before and after a change are not recorded, and a change’s title still carries the planner’s own wording, for example “(+9 re-derived)”.