How do I require green CI before Claude Code merges changes to a documentation website?
Tares has you choose, the first time you run tares factory crew up, whether the crew merges on its own after review and green CI, or waits for your yes. With the merge-on-its-own choice, which is the recommended one, a builder merges a pull request on your documentation website only once the reviewer has passed it and CI is green. Tares reads the pull request, CI and merge state through its own GitHub access, so the gate does not depend on what a session says about itself.
How it works
The software factory for Claude Code in Tares is a crew of Claude Code sessions that run on your machine: an orchestrator, a reviewer and builders. For a documentation website, the path of a change looks like this:
- A builder takes a ticket, works on its own branch and opens a pull request. It pushes and opens the pull request with your
ghlogin. - The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request.
- Tares reads the pull request, the CI result and the merge state of every ticket itself. It needs its own access to your repos for this, separate from the
ghlogin the builders use. - What happens next depends on how far you let the crew go. If you chose to let the crew merge on its own after review and green CI, the builder merges once the reviewer passes the pull request and CI is green. If you chose to wait for your yes, every merge waits for you, even when the reviewer has passed it and CI is green.
You can also hold back a single project. One project can wait for your yes before every merge while the rest of the crew merges on its own. That suits a documentation website you want to read before it goes live.
Tares keeps the plan, the tickets, every review and your answers, so a crew that restarts carries on where it stopped.
Set it up
-
Check that Claude Code is signed in on a plan that allows background sessions, that
ghis signed in with write access to the repo that holds your documentation website, and thatgit,jqandcurlare installed.gh auth login -
Install the CLI and start Tares. Locally, run
tares up, then start the MCP endpoint in a second terminal. On Tares Cloud, sign in withtares loginand pick your workspace in the browser instead.uv tool install tares # or: brew install glassflow/tap/tares tares up tares mcp --transport streamable-http -
Give Tares its own access to GitHub, so it can read the pull request, CI and merge state. On Tares Cloud, choose Connect GitHub in your workspace settings and pick the repo. On a local Tares, add a GitHub token or App under Settings > GitHub.
-
Bring up the crew.
tares factory crew up -
Answer the first-run questions. The one that sets the gate asks whether the crew merges on its own after review and green CI (recommended) or waits for your yes. Choose merging after review and green CI if you want the builder to merge as soon as both hold. Choose waiting for your yes if you want a final look at every merge. The answers are kept on Tares.
-
Plan the documentation work from the repo, or from a folder that holds it.
tares factory spec "what you want to build" -
Run
tares factory doctorto check everything the crew needs. If you need to stop merges at any point,tares factory crew haltstops merges, pushes and new sessions untilcrew resume.
The Get started page covers each of these steps in full.
What you get
- A merge rule you set once. Either the builder merges after the reviewer passes the pull request and CI is green, or every merge waits for your yes.
- A review on every pull request. The reviewer holds each change to a fixed bar and posts its verdict on the pull request, so nothing reaches main unreviewed.
- Merge state Tares reads itself. Tares checks the pull request, CI and merge state through its own GitHub access, and the Crew page lists the pull requests waiting for review.
- A record you can check. Reviews, assumptions and your answers stay on Tares, so you can look over what the crew decided at the end of each milestone instead of during every step.
- Per-project control. One project can wait for your yes before every merge while others merge on their own.
When something else fits
- If you want to read and approve every documentation change yourself, choose the wait-for-your-yes setting at first crew up, or hold just that project for your yes before every merge.
- If a single small change does not need a crew, run
tares factory sessionto work on it in your own Claude Code session, still on Tares. - The software factory is built for solo developers and very small teams on one machine with their own GitHub repos. A larger team with shared review rules may need a different setup.
Related
- Build a software factory with Claude Code
- How do I require green CI before Claude Code merges changes to a monorepo?
- How do I require green CI before Claude Code merges changes to a Python backend?
- How do I require green CI before Claude Code merges changes to a Node/TypeScript app?
Still stuck? Get help