Every repo and your board, in step.
Connect as many repositories as your team ships from, and the board follows the code in all of them. Put a task’s code in a commit or a pull request in any repo, and the task moves on its own with the PR’s live state on it.
In Progress
T-238 
Faster search across docs and chat
EngineeringT-252 
Flaky billing tests
#214In Review
T-231 
Proration when seats change mid-cycle
BillingDone
T-227
Onboarding rework: four steps
T-252
Flaky billing tests
#214How it works
-
Connect your repos
Add every repo your team works in, in Settings, each with a line on what it holds.
-
Reference the task
Put T-42 in a commit subject, a branch name or a pull request title, in any connected repo.
-
Let the rules move it
Each repo’s workflow rules move tasks forward when code is pushed, a PR opens or a PR merges.
A board kept honest by git.In every repo, with agents that read the code.
Live pull request state
The pill on a task shows draft, open, merged, changes requested, failing checks or conflicts.
Forward only
Rules only move a task forward, so a late push never drags finished work back.
Reviews on the task
Review comments show on the task. Press Address and an agent replies in each GitHub thread.
Code questions answered
Ask where the retry logic lives and the AI picks the right repo, reads it and cites the paths.
A map of your repos
Study works out what each repository is for and draws how they depend on each other.
The right repo, every run
A task names the repo its work is in, and a coding agent opens the pull request there.
Good to know
- GitHub only. GitLab and Bitbucket aren’t supported.
- Nothing merges on its own, and review comments are answered when a member presses Address.