Pull requests and revisions

How a delivery relates to commits, revisions, pull requests and checks. Evidence and approvals are pinned to a revision.

A delivery is about an outcome, but the outcome ships as code. Blume ties the two together with revisions: each version of the code that was sent for review, pinned to a commit.

Blume records the code revision with every piece of evidence and every approval:

  • Evidence is current or it is older. Evidence from older code is still shown, as evidence of older code.
  • An approval belongs to the code it approved. New code, newly opened work or a failing check withdraws it.
  • A pull request is reviewed at its head. A push after you were asked closes the request, and the agent asks again.

Blume works without GitHub: agents report their pull request links. Connect GitHub to see checks and reviews, and to let Blume observe merges and deployments.

Revisions

A revision is created when the delivery enters the outcome review on new code. Revisions are numbered R1, R2 and so on, each with a short name that says what changed.

A revision card on a delivery's Revisions tab: R1, marked Current, at commit c501327, with its Outcome review (due now, with a Review button), Merge review (not yet) and Release review (none needed) side by side, and its six acceptance checks with their test types.A revision card on a delivery's Revisions tab: R1, marked Current, at commit c501327, with its Outcome review (due now, with a Review button), Merge review (not yet) and Release review (none needed) side by side, and its six acceptance checks with their test types.
A revision on the Revisions tab of a delivery in Blume, with its three reviews and its acceptance checks.

Each card shows its commit, its state (Current or Superseded), its acceptance checks and its three reviews: outcome, merge and release.

When an approval carries. If the merge review sends work back for a fix and every acceptance check passes again at the new code, the new revision carries the earlier outcome approval. A failed check, a changed plan or a revoked approval drops the carry.

Pull requests

The PRs tab shows one card per pull request. With GitHub connected, each card shows its checks and whether its head still matches the revision you reviewed (Matches) or has moved (Pushed since).

A pull request card on a delivery's PRs tab: number 3, Open, with What it is (the latest commit, 3 files, 2 commits, opened 7 minutes ago) and Can it merge (tests: 3 failed at the current commit; preview passing).A pull request card on a delivery's PRs tab: number 3, Open, with What it is (the latest commit, 3 files, 2 commits, opened 7 minutes ago) and Can it merge (tests: 3 failed at the current commit; preview passing).
A pull request card on the PRs tab of a delivery in Blume: what the pull request is on the left, whether it can merge on the right.

After the outcome approval, the agent makes each pull request ready to merge, then asks the merge review once per pull request.

  • An approval on GitHub counts when it comes from a person other than the author, for this head. Bots do not approve.
  • Approving a merge review does not merge anything. The agent merges, or you do.
  • When every pull request has reached the default branch, the delivery moves to Release, or to Done when it has nothing to release.