How do I get Claude Code to deploy after the pull request merges?

Say yes to releasing when you run tares factory crew up and Tares adds a releaser to your crew. The releaser is a Claude Code session that tags and deploys. Without it, the crew stops at merged on main. Merging has its own setting, so you decide whether builders merge on their own or wait for your yes.

How it works

The software factory for Claude Code is a crew of Claude Code sessions that run in the background on your machine. Each member has one job:

• Orchestrator: hands out work and brings you the questions that need you. It is the only session you talk to.
• Reviewer: reviews every pull request to a fixed bar and posts its verdict.
• Builders: one per milestone and repo. Each takes a ticket, works on its own branch, opens a pull request, and merges it once the reviewer passes it and CI is green.
• Releaser: only if you ask for one. It tags and deploys.

Releasing is off unless you ask for it. If you do not ask for a releaser, tickets end at merged on main and nothing tags or deploys.

The releaser comes after merging, so the merge setting matters too. At L4-ship, a builder merges once the reviewer approves and CI is green. At L3-review, every merge waits for your yes. A single project can also wait for your yes before every merge, even when the rest of the crew merges on its own.

Tares keeps the plan, the tickets, every review and your answers. If a session stops, the watch brings it back under the same name and it carries on from the record on Tares. The orchestrator also checks for work every 20 minutes, so an idle crew still notices a merged pull request that unblocks the next ticket.

Set it up

1. Check what you need. Claude Code must be signed in on a plan that allows background sessions. gh must be signed in with write access to the repos the crew works in. You also need git, jq and curl. Tares needs its own access to your repos too: on Tares Cloud choose Connect GitHub in your workspace settings, and locally add a GitHub token or App under Settings > GitHub. See Build a software factory with Claude Code for the full setup.

2. Install Tares and sign in. For a local Tares, replace tares login with tares up and start the MCP endpoint the sessions share.

   uv tool install tares     # or: brew install glassflow/tap/tares
   tares login

3. Bring up the crew.

   tares factory crew up

4. Answer the crew settings on the first run. Tares asks how far the crew may go: whether it merges on its own after review and green CI (recommended) or waits for your yes, whether it releases, whether a second model checks every commit, how many builders run at once, and anything you always allow. Say yes to releasing. Tares keeps your answers.

5. Plan a project.

   tares factory spec "what you want to build"

   The interview ends by asking whether to hand the project to the crew. Say yes, and the orchestrator picks it up.

6. Answer questions as they come. Attach to the orchestrator, where each question arrives one at a time with a recommendation.

   tares factory crew attach orchestrator

7. Check the crew at any point with tares factory crew status, which shows the stations, the questions for you and a line per project. tares factory doctor checks everything the crew needs.

What you get

• A releaser session in your crew that tags and deploys, so the work does not end at a merged pull request.
• A clear split of decisions. Merging is your setting, and releasing is a choice you make once at crew up.
• A crew that keeps running while you are away. The watch revives stopped stations, and the orchestrator checks for work every 20 minutes.
• A record on Tares of the plan, tickets, reviews and your answers, so a restarted crew carries on where it stopped.
• One crew for many projects. The releaser is one of the shared stations, alongside the orchestrator and reviewer, and each project lists its own builders on the Crew page.

The autonomous Claude Code sessions page explains how the sessions keep running and what still needs you.

When something else fits

Leave the releaser off if you want to deploy yourself. The crew then stops when work is merged to main, and you tag and ship on your own schedule. This is the default.

If you want a human check before anything reaches main, set merging to L3-review, so every merge waits for your yes. The reviewer still reviews every pull request to the same bar.

If a project needs your hands for a while, work on it in your own Claude Code session with tares factory session <project>. When the crew has the project, the session asks whether to take it over. Say yes and the crew stops, its builders push what they have and write their progress, and your session carries on from their branches and pull requests. Say no and the crew keeps it.

Related