Repository navigation
Conversation
Popups (context menus, sub-menus, flyouts, tooltips, drop-downs) are separate top-levels, so they did not inherit the zoom applied by the window template and stayed tiny when zoomed in. Apply the same zoom in the PopupRoot template, and drop InheritsTransform from the branch selector popup so it is not scaled twice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… several repositories at once Workspaces: - Each workspace now owns its repositories and groups. The tree lives in a hidden top-level group referenced by `Workspace.RootGroupId`, so a repository belongs to a single workspace. - The Welcome page, its search, the group pickers of Clone and Open Local Repository, the Move dialog and the repository palette only show the active workspace. - Everything that used to go to the tree root (add, clone, init, trust, scan, open from command line, create group, drop on empty area) goes to the active workspace. A repository already in another workspace is opened but not moved. - On first load the global tree is migrated: a group with the same name as a workspace becomes its tree (exact casing wins on ties) and everything else goes to the "Default" workspace. - Deleting a workspace moves its tree into the active workspace. Repository tree selection: - Multiple selection with Ctrl/Shift and rubber-band selection started from any empty space of the Welcome page. - Drag the whole selection onto a group, or use "Move N Items to Another Group" from the context menu. - Drag detection moved to the list itself, since the pressed item may capture the pointer; this also fixes dragging on Linux. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per-workspace repository trees
Multi-selection on the Welcome page
Zoom
Technical notes
RepositoryNodes, referenced byWorkspace.RootGroupId. This avoids rewriting every lookup that searches the global tree and guarantees a repository belongs to only one workspace.Preferences.GetScopeRoot()centralizes the "root = active workspace" rule inAddNode,MoveNode,FindOrAddNodeByRepositoryPathandFindOrCreateGroupRecursive.openspec/specs/andopenspec/changes/archive/2026-11-10-workspace-repo-groups/.Compatibility
preference.jsonfiles are migrated without data loss. An older SourceGit build opening a migrated file shows each workspace as a top-level group with the same name.Testing
dotnet format --verify-no-changespasses.preference.json: migration, switching workspaces, search, clone/open local, create/delete/rename workspace, Ctrl/Shift/rubber-band selection, dragging several items, and restarting the app.🤖 Generated with Claude Code