Repository navigation
feat(workspaces): group multi-run worktrees in the worktrees tab - #415
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthrough
ChangesMulti-run worktree display
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant RepoDetail
participant useMultiRuns
participant WorktreeSessionGroups
participant buildGroupEntries
RepoDetail->>useMultiRuns: Load multi-runs for repoId with showWorktrees
useMultiRuns-->>RepoDetail: Return multiRuns
RepoDetail->>WorktreeSessionGroups: Pass multiRuns and worktrees
WorktreeSessionGroups->>buildGroupEntries: Group worktrees by run directories
buildGroupEntries-->>WorktreeSessionGroups: Return grouped entries
Merge Risk: ⚪ Minimal · up to Multi-run grouping has no established merge-blocking issue; cleanup warns users before removing worktrees and their sessions. Pre-merge checks |
  |
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Docstring Coverage |  |
Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 4 files. | Write docstrings for the functions missing them to satisfy the coverage threshold. |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly and concisely describes the main change: grouping multi-run worktrees in the Worktrees tab. |
| Description check | |
The description clearly explains the feature, behavior, cleanup action, data flow, and validation results. It omits the template's Type of Change and Checklist sections, but the core required informat… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
- Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
- Commit to this branch
- Create a new PR
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
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
Multi-run worktrees now nest under their multi-run in the Worktrees tab, the same way scheduled worktrees nest under their schedule, so a run's worktrees stay together as they pile up.
useMultiRuns.Validation
vitest run src/components/repo/WorktreeSessionGroups.test.tsx src/pages/__tests__/RepoDetail.schedule-sessions.test.tsx(10 passed)tsc -b(passes)eslinton changed files (passes)Summary by CodeRabbit