Repository navigation
Metrics single-row toolbar, analytics header tabs, and GitHub repo-access crash fix - #1279
Conversation
The page stacked three rows above the content: the header with the time range, a four-card stat rail, and a search + view toggle row. The stat cards were really a type filter, so they become a single dropdown with per-type metric counts in its menu, and search, type and view now sit in the sticky page header beside the time range.
The summary can be stale across a time-range change or lag the results, and a zero All count made the filter impossible to clear. Counts are now informational only. All types also gets its data-point total title.
The Overview / AI traffic tabs sat in their own row under the range controls. They now ride in the header's titleContent slot, so wide screens get one row and narrow ones stack tabs above the controls, matching the Hosts view tabs.
A repo newly granted to the GitHub App syncs in as pending with zero branches, so BranchSelector returned before calling useAsyncAction. Once the background sync filled in branches, the next poll rendered an extra hook and React crashed the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Maple review🟡 Confidence 3/5 · needs attention Warning This review ended early; what follows is what it established. The pull request hoists
What was checked
Files not reviewed (1)The review ended before it read these diffs, so nothing above vouches for them.
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (6)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
What changed
Metrics / analytics header
GitHub integration crash fix
BranchSelectorreturned early for repos with zero branches before callinguseAsyncAction. A newly granted repo syncs in with no branches, so once the background sync filled them in, the next status poll rendered one more hook and React threw "Rendered more hooks than during the previous render".Reviewer notes
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit