workspace¶
Manage workspaces. A workspace groups a set of repositories together and holds all issue contexts for that group.
A default workspace is created automatically on first run.
Running rf workspace with no subcommand prints command help, followed by the currently selected workspace and its repo count.
rf workspace switch¶
Switch to a workspace by name, or run with no argument for an interactive picker. If no workspace with the given name exists, it is created automatically.
Name rules: letters, numbers, hyphens, and underscores only.
Notes:
- With no argument, opens an interactive list of existing workspaces (current one marked), or, if none exist yet, prompts "No workspaces found. Enter a name to create one".
- Switching to the workspace you're already in is a no-op (prints "Already in workspace ...").
- On switching, prints whether the workspace was newly created or just switched to, then lists its repos if it has any.
Examples:
rf workspace switch # interactive picker
rf workspace switch default
rf workspace switch backend
rf workspace switch mobile-team
rf workspace remove¶
Remove a workspace along with all its issues and snapshots. Repositories on disk are not affected; only the RepoFleet metadata is deleted.
Prompts for confirmation before deleting, showing how many repos, issues, and snapshots will be removed. You cannot remove the active workspace; switch to another one first.
Examples:
$ rf workspace remove old-project
Remove workspace "old-project"? This will delete 2 repo(s), 5 issue(s), 8 snapshot(s). [y/N] y
✓ Removed workspace "old-project"
rf workspace config¶
View or update configuration for the current workspace. Running without flags prints the current settings.
Flags:
| Flag | Description |
|---|---|
--branch-pattern <pattern> |
Set the branch naming pattern for new issues |
Branch pattern tokens:
| Token | Value |
|---|---|
{workspace} |
Workspace name |
{issue} |
Issue ID |
{name} |
Issue name |
{description} |
Issue description |
{kind} |
Issue kind (bug, feature, task, story) |
{type} |
Issue type (feat, fix, chore, docs, refactor, test) |
Examples: