Add Wiki and Dashboard workspace tabs with Command Palette actions and mobile parity#9
Open
Huynhthuongg wants to merge 8 commits into
Open
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughSummary by CodeRabbitGhi chú phát hành
WalkthroughThêm hai tab mới Wiki và Dashboard vào workspace GitBot (desktop + mobile), cập nhật CommandPalette để điều hướng tới các tab này, tích hợp Vercel Analytics vào Next.js frontend, đổi tiêu đề trang Vite, bổ sung README mô tả toàn bộ dự án, và cấu hình domain tùy chỉnh. ChangesWiki & Dashboard Tab Feature
Vercel Analytics + Housekeeping
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
✨ Simplify code
Warning Review ran into problems🔥 ProblemsLinked repositories: Your configuration references 1 linked repositories, but your current plan allows 0. Analyzed ``, skipped 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 |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Kilo Code Review could not run — your account is out of credits. Add credits or switch to a free model to enable reviews on this change. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bc60a40eee
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7deecc31c3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
# Vercel Web Analytics Installation Report
## Summary
Successfully installed and configured Vercel Web Analytics for both the Vite/React root project and the Next.js frontend following the latest official Vercel documentation.
## What Was Done
### 1. Root Project (Vite + React)
**Status:** Already configured ✓
- The `@vercel/analytics` package (v2.0.1) was already installed in package.json
- The Analytics component was already imported and used in `src/App.tsx`
- No changes needed for the root project
### 2. Next.js Frontend (gitbot/frontend)
**Status:** Newly configured ✓
#### Files Modified:
- **gitbot/frontend/package.json**
- Added `@vercel/analytics: ^2.0.1` to dependencies
- **gitbot/frontend/app/layout.tsx**
- Imported Analytics component: `import { Analytics } from '@vercel/analytics/next';`
- Added `<Analytics />` component inside the body tag, after children
- Follows Next.js App Router best practices from official docs
#### Files Created:
- **gitbot/frontend/package-lock.json**
- Generated during npm install with --legacy-peer-deps flag
- Necessary for dependency consistency
## Implementation Details
### Documentation Source
Fetched latest installation instructions from: https://vercel.com/docs/analytics/quickstart
### Framework-Specific Configuration
- **Vite/React:** Used `@vercel/analytics/react` import
- **Next.js App Router:** Used `@vercel/analytics/next` import
### Installation Method
- Root project: Already had the package installed
- Next.js frontend: Installed using `npm install @vercel/analytics --legacy-peer-deps` due to React 19 peer dependency conflicts with lucide-react
## Verification
### Build Status
✓ Root project builds successfully with `pnpm run build`
✓ No breaking changes introduced
✓ TypeScript compilation passes for analytics-related code
### Code Quality
- Preserved existing code structure
- Added minimal necessary changes
- Followed framework-specific best practices
- Analytics components placed in recommended locations per docs
## Notes
- The Next.js frontend has pre-existing TypeScript errors unrelated to this change (missing component modules)
- Both projects now have Vercel Web Analytics properly configured
- Analytics will start collecting data once deployed to Vercel
- No test scripts available in either project to run
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
* Install and configure Vercel Web Analytics
# Vercel Web Analytics Installation Report
## Summary
Successfully installed and configured Vercel Web Analytics for both the Vite/React root project and the Next.js frontend following the latest official Vercel documentation.
## What Was Done
### 1. Root Project (Vite + React)
**Status:** Already configured ✓
- The `@vercel/analytics` package (v2.0.1) was already installed in package.json
- The Analytics component was already imported and used in `src/App.tsx`
- No changes needed for the root project
### 2. Next.js Frontend (gitbot/frontend)
**Status:** Newly configured ✓
#### Files Modified:
- **gitbot/frontend/package.json**
- Added `@vercel/analytics: ^2.0.1` to dependencies
- **gitbot/frontend/app/layout.tsx**
- Imported Analytics component: `import { Analytics } from '@vercel/analytics/next';`
- Added `<Analytics />` component inside the body tag, after children
- Follows Next.js App Router best practices from official docs
#### Files Created:
- **gitbot/frontend/package-lock.json**
- Generated during npm install with --legacy-peer-deps flag
- Necessary for dependency consistency
## Implementation Details
### Documentation Source
Fetched latest installation instructions from: https://vercel.com/docs/analytics/quickstart
### Framework-Specific Configuration
- **Vite/React:** Used `@vercel/analytics/react` import
- **Next.js App Router:** Used `@vercel/analytics/next` import
### Installation Method
- Root project: Already had the package installed
- Next.js frontend: Installed using `npm install @vercel/analytics --legacy-peer-deps` due to React 19 peer dependency conflicts with lucide-react
## Verification
### Build Status
✓ Root project builds successfully with `pnpm run build`
✓ No breaking changes introduced
✓ TypeScript compilation passes for analytics-related code
### Code Quality
- Preserved existing code structure
- Added minimal necessary changes
- Followed framework-specific best practices
- Analytics components placed in recommended locations per docs
## Notes
- The Next.js frontend has pre-existing TypeScript errors unrelated to this change (missing component modules)
- Both projects now have Vercel Web Analytics properly configured
- Analytics will start collecting data once deployed to Vercel
- No test scripts available in either project to run
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
* build(deps): Bump golang.org/x/crypto
Bumps the go_modules group with 1 update in the /gitbot/backend directory: [golang.org/x/crypto](https://github.com/golang/crypto).
Updates `golang.org/x/crypto` from 0.19.0 to 0.45.0
- [Commits](golang/crypto@v0.19.0...v0.45.0)
---
updated-dependencies:
- dependency-name: golang.org/x/crypto
dependency-version: 0.45.0
dependency-type: direct:production
dependency-group: go_modules
...
Signed-off-by: dependabot[bot] <support@github.com>
* Update README.md
* Design professional wiki page
* Add GitBot docs intro and logo
* V0/rkix 34f21390 (#13)
* build(deps): Bump golang.org/x/crypto
Bumps the go_modules group with 1 update in the /gitbot/backend directory: [golang.org/x/crypto](https://github.com/golang/crypto).
Updates `golang.org/x/crypto` from 0.19.0 to 0.45.0
- [Commits](golang/crypto@v0.19.0...v0.45.0)
---
updated-dependencies:
- dependency-name: golang.org/x/crypto
dependency-version: 0.45.0
dependency-type: direct:production
dependency-group: go_modules
...
Signed-off-by: dependabot[bot] <support@github.com>
* Update README.md
* Design professional wiki page
* Add GitBot docs intro and logo
* Install and configure Vercel Web Analytics
# Vercel Web Analytics Installation Report
## Summary
Successfully installed and configured Vercel Web Analytics for both the Vite/React root project and the Next.js frontend following the latest official Vercel documentation.
## What Was Done
### 1. Root Project (Vite + React)
**Status:** Already configured ✓
- The `@vercel/analytics` package (v2.0.1) was already installed in package.json
- The Analytics component was already imported and used in `src/App.tsx`
- No changes needed for the root project
### 2. Next.js Frontend (gitbot/frontend)
**Status:** Newly configured ✓
#### Files Modified:
- **gitbot/frontend/package.json**
- Added `@vercel/analytics: ^2.0.1` to dependencies
- **gitbot/frontend/app/layout.tsx**
- Imported Analytics component: `import { Analytics } from '@vercel/analytics/next';`
- Added `<Analytics />` component inside the body tag, after children
- Follows Next.js App Router best practices from official docs
#### Files Created:
- **gitbot/frontend/package-lock.json**
- Generated during npm install with --legacy-peer-deps flag
- Necessary for dependency consistency
## Implementation Details
### Documentation Source
Fetched latest installation instructions from: https://vercel.com/docs/analytics/quickstart
### Framework-Specific Configuration
- **Vite/React:** Used `@vercel/analytics/react` import
- **Next.js App Router:** Used `@vercel/analytics/next` import
### Installation Method
- Root project: Already had the package installed
- Next.js frontend: Installed using `npm install @vercel/analytics --legacy-peer-deps` due to React 19 peer dependency conflicts with lucide-react
## Verification
### Build Status
✓ Root project builds successfully with `pnpm run build`
✓ No breaking changes introduced
✓ TypeScript compilation passes for analytics-related code
### Code Quality
- Preserved existing code structure
- Added minimal necessary changes
- Followed framework-specific best practices
- Analytics components placed in recommended locations per docs
## Notes
- The Next.js frontend has pre-existing TypeScript errors unrelated to this change (missing component modules)
- Both projects now have Vercel Web Analytics properly configured
- Analytics will start collecting data once deployed to Vercel
- No test scripts available in either project to run
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/App.tsx (1)
1152-1190:⚠️ Potential issue | 🟠 Major | ⚡ Quick winNút “Gửi” trên mobile chưa thực hiện gửi bình luận.
Line 1183-1186 chỉ hiện thông báo hướng dẫn, trong khi logic POST chỉ nằm ở Enter của input (Line 1156-1179). Người dùng bấm nút “Gửi” sẽ không gửi được dữ liệu.
💡 Đề xuất chỉnh nhanh (dùng chung 1 submit handler cho Enter + click)
+ const [quickComment, setQuickComment] = useState(''); + + const submitQuickComment = async () => { + if (!quickComment.trim()) return; + try { + const res = await fetch(`/api/v1/repos/${currentRepoId}/pulls/${currentPrId}/comments`, { + method: 'POST', + headers: { 'Content-Type': 'application/json' }, + body: JSON.stringify({ + file_path: selectedFilePath || 'parser.go', + line_number: 14, + author: "gitbot_mobile_dev", + content: quickComment + }) + }); + if (res.ok) { + setQuickComment(''); + fetchCommentsForPR(currentRepoId, currentPrId); + setNotificationMsg("💬 Đăng bình luận nhanh thành công!"); + setTimeout(() => setNotificationMsg(""), 2000); + } + } catch (err) { + console.error(err); + } + };- <input + <input type="text" + value={quickComment} + onChange={(e) => setQuickComment(e.target.value)} placeholder="Viết nhanh bình luận chung cho PR..." ... - onKeyDown={async (e) => { - if (e.key === 'Enter' && e.currentTarget.value.trim()) { - const input = e.currentTarget; - try { - const res = await fetch(`/api/v1/repos/${currentRepoId}/pulls/${currentPrId}/comments`, { - method: 'POST', - headers: { 'Content-Type': 'application/json' }, - body: JSON.stringify({ - file_path: selectedFilePath || 'parser.go', - line_number: 14, - author: "gitbot_mobile_dev", - content: input.value - }) - }); - if (res.ok) { - input.value = ''; - fetchCommentsForPR(currentRepoId, currentPrId); - setNotificationMsg("💬 Đăng bình luận nhanh thành kông!"); - setTimeout(() => setNotificationMsg(""), 2000); - } - } catch (err) { - console.error(err); - } - } - }} + onKeyDown={(e) => { + if (e.key === 'Enter') submitQuickComment(); + }} /> <button - onClick={() => { - setNotificationMsg("💡 Gợi ý: Gõ văn bản rồi nhấn Enter trong ô nhập để gửi bình luận nhanh từ di động!"); - setTimeout(() => setNotificationMsg(""), 3500); - }} + onClick={submitQuickComment}🤖 Prompt for 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. In `@src/App.tsx` around lines 1152 - 1190, The "Gửi" button on lines 1183-1186 only displays a notification instead of actually submitting the comment, while the actual POST request logic is isolated in the input's onKeyDown handler on lines 1156-1179. Extract the comment submission logic (the fetch call with POST to /api/v1/repos endpoint and the subsequent state updates) from the onKeyDown handler into a separate function, then call this shared function from both the Enter key handler and the button's onClick handler to ensure users can submit comments either by pressing Enter or clicking the "Gửi" button.
🤖 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 `@README.md`:
- Around line 1-5: The README.md file starts with HTML tags (<p> and <h1>)
instead of a markdown heading, which violates the markdownlint MD041 rule that
requires files to begin with a markdown heading. Replace the HTML content at the
beginning of the file with proper markdown syntax: convert the <img> tag to a
markdown image using  format and replace the
<h1 align="center">GitBot</h1> tag with the markdown heading # GitBot. You can
combine these on a single line if desired for a cleaner look.
In `@src/App.tsx`:
- Around line 213-217: The dashboardCards array (lines 214-216) and line 1065
use the `||` operator to provide fallback values (2, 248, 64), which incorrectly
treats valid zero values as falsy and replaces them with defaults, causing
incorrect dashboard data. Replace all `||` operators with the nullish coalescing
operator `??` in the expressions for activeOpenPRs, totalDiffAdditions, and
totalDiffDeletions in the dashboardCards definition and at line 1065, so that
zero values are preserved and only true nullish values (null or undefined)
trigger the fallback.
- Line 225: The wikiToc array in the App.tsx file declares six menu items, but
the corresponding wiki section anchors only exist for the first four items
(wiki-0 through wiki-3). This creates broken internal links for the last two
items ('Triển khai Vercel' and 'FAQ'). Either remove the last two items from the
wikiToc array at line 225 to match the existing content sections, or add the two
missing section blocks with ids wiki-4 and wiki-5 in the content area (lines
559-620) to match all six declared menu items.
---
Outside diff comments:
In `@src/App.tsx`:
- Around line 1152-1190: The "Gửi" button on lines 1183-1186 only displays a
notification instead of actually submitting the comment, while the actual POST
request logic is isolated in the input's onKeyDown handler on lines 1156-1179.
Extract the comment submission logic (the fetch call with POST to /api/v1/repos
endpoint and the subsequent state updates) from the onKeyDown handler into a
separate function, then call this shared function from both the Enter key
handler and the button's onClick handler to ensure users can submit comments
either by pressing Enter or clicking the "Gửi" button.
🪄 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
Run ID: 268f3749-d4a6-40ff-bff5-fc79021148f4
⛔ Files ignored due to path filters (2)
gitbot/frontend/package-lock.jsonis excluded by!**/package-lock.jsonpublic/gitbot-logo.svgis excluded by!**/*.svg
📒 Files selected for processing (6)
README.mdgitbot/frontend/app/layout.tsxgitbot/frontend/package.jsonindex.htmlsrc/App.tsxsrc/components/CommandPalette.tsx
github-project-automation
Bot
moved this to To triage
in @Huynhthuongg's untitled project
github-project-automation
Bot
moved this from To triage
to In progress
in @Huynhthuongg's untitled project
Huynhthuongg
added
bug
Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
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
1 participant
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.
Motivation
CommandPaletteand ensure feature parity on both desktop and mobile simulated viewports.Description
wikianddashboard, extendedactiveWorkspaceTabtype and default state, and added UI buttons/tabs to switch them in both desktop and mobile layouts.activeOpenPRs,mergedPRs,totalDiffAdditions,totalDiffDeletions,pipelineSuccessRate) anddashboardCardsto render the live overview panels and signals widgets.wikiSections,wikiToc) including an overview, docs list, code snippet sample, and checklist, with responsive desktop and mobile render paths.CommandPaletteto add actions for opening the Wiki and Dashboard, expanded imports for new icons, adjusted combined item handling, and preserved existing repo/PR/file deep-link behavior.App.tsxandCommandPalette.tsxincluding consistent JSX spacing, select/input attributes, and additional mobile navigation hooks.Testing
tsc --noEmit, which completed successfully.npm run build, which succeeded without build-time errors.wiki,dashboard,pr,pipeline, anddocsrendered as expected.Codex Task
Summary by cubic
Adds new Wiki and Dashboard workspace tabs with Command Palette actions, full mobile parity, GitBot branding, and Vercel Analytics for both the React and Next.js apps. Sets the custom domain to gitbot.dev, updates the README, and adds a license document.
New Features
wikianddashboardtabs with desktop/mobile UIs and Command Palette actions..gitbot-ci.yml.public/gitbot-logo.svg, updated favicon and app title; README with logo, architecture, local run, and Vercel deploy steps.@vercel/analytics/reactin the root app and@vercel/analytics/nextingitbot/frontend/app/layout.tsx; added@vercel/analyticsto the Next.js frontend.Migration
activeWorkspaceTabis nowwiki(waspr); update tests/docs that assume the PR tab opens first.Written for commit 85ecb48. Summary will update on new commits.