Repository navigation
Showcase: a Next.js 16 review desk for PR, CI, and fork-sync evidence #95893
Replies: 1 comment 2 replies
|
Hi @AaronZ345! Great job on Codebase Argus! The focus on fixing hydration mismatches and optimizing small-screen layouts really polished the experience. Regarding your feedback request on the static-demo boundary: What works well: The distinction between public repository inspection (static/Pages) vs. agent/git-backed features (server/local) makes sense logically once read. Suggestion for clarity: To make the boundary immediately clear to first-time visitors on the GitHub Pages demo, consider adding a small visual indicator or badge (e.g., ⚡ Static Mode (Public Repos Only)) in the header or sidebar with a tooltip/modal that lists feature availability (e.g., Public PR Review: Available | Merge-Tree / Rebase Projection: Requires Local/Server Deployment). Awesome project, and thanks for sharing the case study and GitHub Action! |
Uh oh!
There was an error while loading. Please reload this page.
I built Codebase Argus, a Next.js 16 review desk for three related maintainer workflows: pull request review, failing-CI diagnosis, and downstream fork sync checks.
The public GitHub Pages demo is a static export that can inspect public GitHub data in the browser. Local or server deployments unlock the API-backed pieces: private repositories, agent providers, webhook handling, and local git simulations such as
merge-tree, rebase projection,cherry, andrange-diff.The latest pass simplified the screen around the three workflows, moved the useful report lanes ahead of advanced setup, and tightened the small-screen layout. It also fixed two hydration mismatches caused by reading
window.location.originand generating a timestamp during the initial render; both values now initialize after hydration, with server/browser markup regression tests.For anyone interested in the full flow, there is a real public-PR case study and a separate GitHub Action.
I would welcome feedback on the static-demo boundary in particular: is it clear which capabilities work on GitHub Pages and which require a server or local checkout?
All reactions