History Sidebar - #293
Conversation
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe ConflictResolver history panel now uses an aside with explicit close and grouped undo/redo controls. Its CSS implements a fixed right-edge slide-in layout with updated header, action, list, item, hover, and focus styling. ChangesConflict history UI
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/web/client/src/components/ConflictResolver.tsx`:
- Around line 543-551: Update ConflictResolver’s history close flow to keep a
ref to the history-toggle trigger and focus that element when the history close
button’s onClick hides the sidebar. Ensure the focus restoration occurs after
closing so focus does not remain inside the aria-hidden history content.
In `@packages/web/client/src/styles.ts`:
- Around line 287-300: Update the .history-dropdown width from the fixed 320px
value to a viewport-relative 20vw width, retaining max-width: 90vw or adding
only necessary usability bounds.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 79a60917-2ec5-4c6a-b9e1-8e3e175bbea3
📒 Files selected for processing (2)
packages/web/client/src/components/ConflictResolver.tsxpackages/web/client/src/styles.ts
|



Changes the logic for opening the history sidebar to expand and take 20% of the right side.
Summary by CodeRabbit
Accessibility
UI Improvements