From 8da215147690859f4bf930bf50574c996f618542 Mon Sep 17 00:00:00 2001 From: Michael Johnson Date: Fri, 14 Aug 2026 18:08:12 +0100 Subject: [PATCH] State in the README that accepting does not merge the work Quickstart step 5 read as though accepting landed the change: a first-time user on a no-remote project accepts, checks the repo, and finds main untouched. Accept is a pure state transition and stays that way; what was missing was the sentence saying so, and naming what does land the work on each path. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01PDRHqMspvgbNVVP6vvJikF --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 831a7c3..bbdb56a 100644 --- a/README.md +++ b/README.md @@ -137,6 +137,14 @@ editor you do use instead. With the account and the diff in front of you, press `enter` (`⏎ review`) to accept or reject the work; rejecting with a note re-dispatches the agent to address it. +Accepting records your verdict and completes the task — it does not merge +anything. On a project you review through GitHub the work lands when its pull +request is merged, which you will usually have done already, with the merged +diff in front of you. On a project with no remote the work stays on the branch +the agent reported, recorded on the task and printed by `voro show ` as +`branch:`, and landing it is one command in the project checkout: `git merge +`. + Other keys worth knowing on a selected task: `s` change state, `x` the score breakdown, `h` its history, `e` edit, `l` the session log, and `q` to quit.