-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: ssr and dialog ui v0 #112
Conversation
* feat: browse as home * feat: browse as home * feat: remove tabs
* feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth * feat: supabase auth
* devops: lighthouse reports on prs * chore: cleanup
* devops: lighthouse reports on prs * chore: cleanup * chore: test lighthouse ci * devops: lighthouse reports on pr * devops: use zentered/vercel-preview-url
* chore: test lighthouse ci * devops: fix version on github actions * chore: cleanup
* chore: test lighthouse ci * devops: debug github actions
* devops: debug github actions * devops: correct project id
* devops: debug github actions * devops: correct vercel team id
* devops: debug github actions * devops: use actions/checkout v4 * devops: add protocol to lhci url
* devops: debug github actions * devops: debug github actions * devops: use foo-software/lighthouse-check-action
* devops: debug github actions * devops: lhci budget path
* devops: debug github actions * devops: disable lhci budget
* devops: debug github actions * devops: run lhci on bot and user landings
* devops: debug github actions * devops: run lhci on bot and user landings * devops: run lhci on bot and user landings
* devops: debug github actions * devops: run lhci on bot and user landings
* devops: debug github actions * devops: debug lhci results comment
* devops: debug github actions * devops: debug lhci results comment
* devops: debug lhci results comment * feat: thread landing * devops: debug lhci results comment
* chore: cleanup * devops: debug lhci results comment
* devops: debug lhci results comment * devops: debug lhci results comment
* chore: cleanup * devops: lhci results table comment
* devops: test lhci results comment * devops: test lhci results comment * devops: test lhci results comment
* devops: config pkgs, eslint, prettier, tailwind, ts * devops: config pkgs, eslint, prettier, tailwind, ts * devops: config pkgs, eslint, prettier, tailwind, ts * devops: config pkgs, eslint, prettier, tailwind, ts * devops: remove first comment on lhci action * devops: fix eslint action
* chore: browse ssr improvements, supabase db types * chore: fix eslint * devops: lhci on pr
* feat: thread dialog ui * feat: thread dialog ui * feat: thread dialog ui * feat: ssr and layout improvements on u and b routes * fix: correct thread number * feat: ssr and layout improvements on u and b routes * feat: global categories nav * chore: move shared components * feat: copy shortlink * chore: disable getUserProfile * perf: only 25 items on first render * perf: only 20 items on first render
* feat: load only 15 more * fix: auth issues * devops: wait 2 minutes before running lhci
* feat: load only 15 more * fix: auth issues * devops: wait 2 minutes before running lhci
* fix: chat auth bug * fix: chat auth bug * fix: chat auth bug
* fix: icon size * fix: chat navigation
* feat: chat lists and dialog * feat: chat lists and dialog
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Important Auto Review SkippedAuto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
No description provided.