What happens when the reviewer asks for changes to dependency upgrades?
When the reviewer asks for changes on a dependency upgrade ticket, Tares sends the pull request back to the builder, who makes the changes, and a second review round decides it. Smaller issues the reviewer finds outside the ticket become a new ticket, so the plan grows on its own. The ticket is handled like any other ticket in the software factory for Claude Code.
How it works
A dependency upgrade ticket moves through the same steps as every ticket in the software factory for Claude Code. The builder works one ticket at a time: it makes a branch, does the work and opens a pull request. The reviewer reviews every pull request and posts its verdict.
When the verdict is changes requested, the round trip looks like this:
- The reviewer posts its findings on the pull request.
- The builder that holds the ticket makes the changes.
- A second review round runs on the updated pull request.
- Once the verdict passes and CI is green, the builder merges.
Most tickets pass on the first round. In the project walked through in A project, end to end, two tickets took a second round: the reviewer asked for changes, the builder made them, and the next round passed.
The reviewer can also find smaller issues outside the ticket it is reviewing. The orchestrator turns them into a new ticket and places it in the plan, in the walkthrough project in the milestone before the integration tests. A builder fixes them there, so the findings do not stall the original pull request. The orchestrator records this choice as an assumption, which it brings to you at the end of the milestone.
Set it up
You do not configure the review round trip. It is part of how the crew works once a project is running. To get a project running, follow the setup in Get started, in this order:
- Check that Claude Code is signed in, that
ghis signed in with write access to the repos the crew works in, and that git, jq and curl are installed. - Install the CLI.
- On a local Tares, start Tares, then in a second terminal start the MCP endpoint every crew session shares. On Tares Cloud, run
tares logininstead and pick your workspace in the browser. There is no MCP endpoint to start. - Give Tares access to GitHub: in Settings > GitHub for a local Tares, or Connect GitHub on Tares Cloud.
- Bring up the crew.
- Plan the project, for example the dependency upgrades you want, with a spec.
gh auth login
uv tool install tares # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http # second terminal
tares factory crew up
tares factory spec "what you want to build"- Open the Crew page in the console,
http://127.0.0.1:8787/crewlocally, to watch the work. The review queue lists pull requests waiting for the reviewer, and questions waiting for you appear at the top. - Open the project page and the Tickets fold to see each ticket with its builder, its pull request and its review rounds.
What you get
- A pull request that does not merge until the reviewer’s verdict passes and CI is green.
- A visible record of every review round on each ticket, with the builder that held it and its pull request.
- Smaller findings that are not lost. They become a ticket of their own instead of widening the pull request under review.
- A plan that adjusts by itself. In the walkthrough project the plan grew by one ticket without anyone editing it.
- A written trail of choices. The orchestrator lists the new ticket among the assumptions, and you keep or change it when it asks at the end of the milestone.
- Nothing for you to do mid-round. The orchestrator answers the builders and brings you only what needs you, as a question in its session.
When something else fits
- If you want to steer a ticket while a round is in progress, talk to the orchestrator, which answers the builders and brings you what needs you.
- If a finding is one you do not want the crew to handle on its own, say so in the orchestrator’s session. Your answer can stand for this project or for every project.
- If a project is already finished and you want more changes, hand it to the crew again, for example with a follow-up spec.