GitHub repo renames (studio-native → wp-build today) have no registry counterpart: no workspace rename <old> <new> that updates the registry row, moves the primary directory, and rewires worktree handles. The workaround is clone-the-new-name + manually migrate worktrees + remove the old registration — slow and error-prone with many worktrees. Real case: chubes4/studio-native renamed to chubes4/wp-build with 16 live worktrees.
GitHub repo renames (studio-native → wp-build today) have no registry counterpart: no
workspace rename <old> <new>that updates the registry row, moves the primary directory, and rewires worktree handles. The workaround is clone-the-new-name + manually migrate worktrees + remove the old registration — slow and error-prone with many worktrees. Real case: chubes4/studio-native renamed to chubes4/wp-build with 16 live worktrees.