You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 Re-apply PR #382: Move Files Changed to top and remove stickiness (#402)
## Problem
PR #382 was merged but was accidentally reverted by commit `00e5b179` (🤖
Restore ReviewPanel and FileTree from good state) during the Tailwind
migration. This PR re-applies those changes to the current
Tailwind-based codebase.
## Changes
### Layout Restructuring
- **Search bar moved outside scrollable area** - Always visible at top,
not part of the scrolling content
- **Single scrollable container** - Created one `overflow-y-auto` div
containing both file tree and hunks
- **File tree on top in all viewports** - No longer side-by-side on wide
screens
- **No sticky behavior** - File tree scrolls away naturally with content
### Technical Implementation
- Search bar: Fixed position at top with `border-b`
- ScrollableContent: `flex min-h-0 flex-1 flex-col overflow-y-auto`
- FileTree: First child with `flex-[0_0_auto]` (sizes to content,
doesn't grow)
- Hunks: Below file tree with `flex-[0_0_auto]` (sizes to content)
## Before vs After
**Before (reverted state):**
- File tree in sidebar (wide) or top section (narrow)
- Two separate scrollable areas (tree + hunks)
- File tree stayed visible when scrolling hunks
**After (this PR):**
- File tree always at top, full width
- Single scrollable area containing both
- File tree scrolls away naturally
## Related
- Original PR: #382
- Reverted by: `00e5b179` (Tailwind migration cleanup)
- Maintained: Common prefix extraction removal (already absent in
current code)
_Generated with `cmux`_
Copy file name to clipboardExpand all lines: docs/AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This ensures transparency about AI-generated contributions.
24
24
25
25
## PR Management
26
26
27
-
**Prefer to reuse existing PRs** by force-pushing to the same branch, even if the branch name becomes irrelevant. Avoid closing and recreating PRs unnecessarily - PR spam clutters the repository history.
27
+
**Prefer to reuse existing PRs** by force-pushing to the same branch, even if the branch name becomes irrelevant. Avoid closing and recreating PRs unnecessarily - PR spam clutters the repository history.**Never close PRs without explicit user instruction.** Always force-push to the existing branch instead of creating new PRs.
28
28
29
29
After submitting or updating PRs, **always check merge status**:
0 commit comments