workspace manages named fleets and bounded multi-repository operations.
Fleet work needs an explicit repository set, predictable ordering, and safe preview behavior.
Use workspace when repeatedly operating on a group of repositories or when
archiving multiple compatible repositories.
Define a small workspace first and inspect it with workspace list. Use
provider-qualified targets when a fleet spans hosts or providers. Workspace
mutations run only against targets that match the active provider and host.
gitfleet workspace define --name platform --repos owner/api --repos owner/webgitfleet workspace listgitfleet workspace remove platformgitfleet workspace archive platform --dry-rungitfleet workspace archive platform --yes
Workspace definitions are local. Provider-backed workspace mutations run only against repositories matching the active provider and host; other targets are reported as skipped.
Use --dry-run before fleet mutations. workspace archive mutates repository
state and requires confirmation or --yes.
Use --json for fleet reports and automation results.
See repo, auth, and ../workflows/workspace-fleets.md.