Repository navigation
feat: group dashboard projects by git remote with workspaces under each - #239
Merged
Merged
Conversation
Runs now record the repo group from the git remote (org/repo) and the checkout as a workspace (ws), so every clone and worktree of one repo shares a group. The Runs and Analyzer tabs filter by a whole repo or one workspace, and the Analyzer projects table expands each repo into its workspaces.
Contributor
|
This PR is included in v3.28.0 🎉 Claude Code If the update still shows the old version, the marketplace re-pin is a few minutes behind; run it again shortly. Codex, Kiro, Cursor, OpenCode plugins: update deliberation from your host's plugin manager. MCP server (any host): |
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.
What
The dashboard groups runs by the git remote (
org/repo) and lists each checkout as a workspace under it. Before, a separate clone or a checkout in/tmpshowed up as its own project named after its folder, and there was no way to look at one workspace.core/project.jsreads theoriginremote (else the first remote) from the main git dir'sconfig. It reads files only and never runsgit.nameisorg/repoandidhashes host plus path.wsfield hashes the checkout path.org/repois stored, never the URL, because https remotes can carry tokens.wsexisted are regrouped when the dashboard reads them, as long as their root still exists. The journal is not rewritten.?project=now matches every workspace of a repo. The new?ws=matches one workspace and wins over?project=. Both work on/api/runsand/api/analyzer.org/repo (path).Testing
npm run check(typecheck and 1192 tests) andnpm run sync:checkpass.wsfilter, nested Analyzer numbers, the?ws=400 response, and the dropdown tree.org/reporow.Not done