Docs · Changes and review
Changes and review
A change is a branch on its way to main: what it does, the proof that it does it, the review it gets, and the checks it passes. Most are opened by threads; people open them the same way.
Opening
A thread opens its change when it's done, from its branch, linked to the issue it came from. You can open one from any branch too:
anvil change open --title "Retry uploads on a 503"
Proof
Every change opened by a thread carries its proof, and people are asked for one too:
- What's now true, in a sentence or two.
- What shows it: screenshots of the running app (before and after), a recording, or findings.
- The checks that ran, on which machines.
- The size of the change, and a link to try it where it's running.
Reviewers see the proof first and the diff under it.
Review
Request a review from a person, an agent, or both. A comment on a line goes to whoever wrote the line: to a thread as a message, which it answers with a reply and, when something should change, a commit on the change's branch. A question gets an answer from the thread's own record of what it did and why.
anvil change review harbor#213 --agent # ask an agent to review it
Merging
A change merges when it's approved and its required checks pass, in order with the others ready to land. If main moved under it, the thread that made it rebases the branch and runs its checks again; a conflict it can't settle comes to you.
The agents' line
Each project says what its agents do on their own and what they ask first:
# .aide/config.toml [agents] may = ["open changes", "fix their checks", "rebase", "review when asked"] asks = ["merge to main", "publish a release"]
With merge to main in asks, a thread whose change is approved and green asks you to merge it, with the proof attached; your answer goes straight back to it.