Where do I see progress on small features when the tickets live in GitHub Issues?

Tares shows progress on small features on the project page, where each GitHub Issues ticket appears with its builder, its pull request and its review rounds. The ticket stays in GitHub and the sessions update it with their own tools. Tares only reads it, about once a minute. The Tickets page of the project shows the status of each ticket as it changes.

How it works

• The ticket stays in GitHub. One repo and one issue label pick the issues. Those issues become the project’s tickets, named GH-<number>, in issue number order.
• Sessions write, Tares reads. The sessions create and change the issues in GitHub with gh. Tares never writes to GitHub Issues. The GitHub Issues connector reads the repo and turns each change into an event on the github_issues source.
• Status comes from the issue. An open issue is todo. An open issue with the in progress label is in_progress. An issue closed as completed is done. An issue closed as not planned or as a duplicate is canceled.
• The project page joins the pieces. Each ticket on the project page shows the builder that held it, its pull request and its review rounds. A progress bar across the top has one segment per ticket, above the four steps Spec, Build, Review and Done. A ticket shows its state as to do, in progress, in review, merged or blocked, and a blocked ticket names the tickets it waits for.
• Milestones and dependencies carry over. GitHub milestones that hold labeled issues appear as milestones. An issue blocked by another makes its ticket depend on that one.

See A project, end to end for a full project with its tickets, pull requests and review rounds.

Set it up

1. Add a GitHub credential in Settings > GitHub. It must be able to read the repo’s issues. A fine-grained token needs the repo with Issues: read. A classic token needs the repo scope. A GitHub App needs the Issues permission and must be installed on the repo.

2. Link the project. On the project’s Tickets page, click Use GitHub Issues, pick or type the repo as owner/name, check the issue label and click Link. Or ask a connected agent to call the MCP tool:

   link_github_issues(repo="acme/shop", issue_label="tares:shop")

   The label is optional and defaults to tares:<project name>.

3. Plan the project and say the tickets live in GitHub Issues. Claude creates them with gh and links the project. The gh login needs the repo scope. Bring up the crew first, then plan. The steps in Get started cover the full setup.

   tares factory crew up
   tares factory spec "what you want to build"

4. Open the project page and unfold Tickets. Click Sync now on the Tickets page to read GitHub at once instead of waiting for the next minute.

5. Check the link. The Tickets page shows “Tickets live in GitHub” with the repo, the issue label and the time of the last sync. Close an issue in GitHub. Within a minute its ticket moves to done, and Recent events on the source shows the change.

What you get

• One page per project that shows each small feature as a ticket, with the builder that held it, its pull request and its review rounds.
• A ticket status that follows the issue, with no second place to update.
• A progress bar with one segment per ticket, so you see how far the build is at a glance.
• Events for every change: ticket_created, ticket_renamed, ticket_status and ticket_removed. Triggers and agents can react to them like any other event.
• Safe failures. If a sync fails, the Tickets page shows why, the tickets stay as they were and nothing is canceled. If GitHub rate limits the sync, Tares waits five minutes before it tries again.
• An issue that loses the label becomes canceled instead of disappearing, so its working doc stays reachable.

When something else fits

• The tickets are read-only in Tares. To change a title, status, milestone or dependency, change the issue in GitHub. If you want to edit tickets in Tares itself, keep them in Tares or use Stop using GitHub on the Tickets page, which returns them with their working docs.
• GitHub Issues links one repo and one issue label per project, on github.com only. If your tickets are in Linear, use the Linear connector instead.

Related