Where do I see progress on dependency upgrades when the tickets live in GitHub Issues?

Tares shows progress on dependency upgrades on the project page, where each GitHub Issues ticket appears with its pull request and its review rounds. The issues stay in GitHub and your sessions update them with their own tools. Tares reads them about once a minute and keeps the project page in step.

How it works

The ticket stays in your tracker. One GitHub repo and one issue label pick the issues, and those issues become the project’s tickets, named GH-<number>. Sessions create and change the issues in GitHub with gh. Tares only reads.

Tares reads the repo about once a minute, and Sync now on the Tickets page reads at once. Each issue maps to a ticket status:

An issue that is blocked by another makes its ticket depend on that one. GitHub milestones that the labeled issues belong to become the project’s milestones, so you can group your dependency upgrades there.

On the project page, the Tickets fold lists each ticket with the builder that held it, its pull request and its review rounds. Mid-build, each ticket shows its state: to do, in progress, in review, merged or blocked, and a blocked ticket names the tickets it waits for. Across the top, four steps (Spec, Build, Review, Done) and a progress bar with one segment per ticket show how far the project has come. The project end to end walkthrough shows these views on a real build.

Set it up

1. Add a GitHub credential in Settings > GitHub. A fine-grained token needs the repo with Issues: read, a classic token needs the repo scope, and a GitHub App needs the Issues permission and an installation on the repo.

2. Plan the project with /tares:spec and say the tickets should live in GitHub Issues. Claude creates them with gh and links the project. If you start from the terminal, run the spec command in your repo:

   tares factory spec

3. To link an existing set of issues instead, open the project’s Tickets page, click Use GitHub Issues, pick or type the repo (owner/name), check the issue label and click Link. A connected agent can do the same with the MCP tool:

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

   The issue label is optional and defaults to tares:<project name>. Tares creates the github_issues source the first time a project is linked.

4. Hand the project to the crew:

   tares factory crew up

   If this is your first time, Get started lists every setup step in order.

5. Open the project page in the console. Locally the crew page is at http://127.0.0.1:8787/crew, and each project you hand to the crew has a page of its own.

6. Check the link. The Tickets page shows “Tickets live in GitHub” with the repo and issue label, and when it last synced. Close an issue in GitHub and within a minute the ticket moves to done. The source’s Recent events shows the change.

A project that already has tickets of its own, or that keeps them in Linear, cannot be linked. A repo and issue label belong to one project.

What you get

• One place to read progress. Each dependency upgrade shows its ticket status, the builder that held it, its pull request and its review rounds on the project page.
• Review history at a glance. A ticket that needed a second round shows both rounds, so you can see where a risky upgrade took extra work.
• Events you can act on. Every change in GitHub becomes an event on the github_issues source, with ticket_created, ticket_renamed, ticket_status or ticket_removed as its type, keyed by the ticket name such as GH-12. Triggers and agents can react to them like any other event.
• Safe failure. 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.
• Nothing lost when issues change. An issue that loses its label, is deleted or moves to another repo becomes canceled in Tares, 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, use Tares tickets, or choose Stop using GitHub on the Tickets page to return them to Tares. The issues in GitHub stay as they are.
• GitHub Issues links one repo and one issue label per project, up to 1000 issues and 100 milestones, on github.com only. GitHub Enterprise Server and GitHub Projects boards are not supported. If your upgrades are tracked in Linear, use the Linear connector in the same way. The GitHub Issues connector page has the full details.

Related