Skip to content

State in the README that accepting a review does not merge the work #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MJohnson459 merged 1 commit into from
Aug 14, 2026
Merged

State in the README that accepting a review does not merge the work #171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <id>` as
`branch:`, and landing it is one command in the project checkout: `git merge
<branch>`.

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.

Expand Down