Multi-repo rollouts
/ Fleet · BB IDE pluginRolls one change out across many repositories in rounds, reading each repository's stage from git and carrying what one repo taught into the next brief.
Each repo runs the same loop; what one repo teaches is printed into the next brief.
Rolling the same change across many near-identical repositories meant tracking by hand which repo was at which step, and rediscovering the same traps every time: silent package-auth failures, main versus master, stale bot branches.
Fleet runs the rollout in rounds. It reads each repository's stage from git, checks the known traps before work starts, briefs an agent per repo, and carries what one repo taught into the next brief. It never edits a repository itself.
- Stage is derived from git, not stored; merged is read from the default branch because squash merges delete the branch.
- Tests run against real temporary git repositories.
- Every command also speaks JSON.