Repository navigation
feat(landing): GitHub, CI and code review page and homepage section - #1534
Conversation
Seed the demo org with PR reviews (`bun run seed:demo:code-review`, refuses any database but maple_screenshots) and add four shots to the landing capture list: Code Review analytics, a PR review sheet, the CI tab and a failed CI run's trace. CI runs come from scripts/seed-ci-runs.ts against acme/web.
…ection /features/github in en, ja and ko: Code Review analytics with its facts panel, Maple's review comment from #1531 redrawn in the site's type, CI runs as traces, and the post-merge comment from #1524. The homepage gets a three-step section (before merge, in CI, after it ships) after the agent section.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 9 minutes. View limit details
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 |
Maple review🟢 Confidence 9/10 · safe to merge Adds the
Before merge
Production impactProduction traffic of the changed files (last 7 days)
What was checked
|
|
Merged with 1 step from "Before merge" still open. If it is done, tick it on the review comment; if not, now is the time.
|
Maple: after this shipped✅ Shipped clean. Nothing this change touches got worse in the hour after it deployed. Deployed to
Maple looks once, an hour after the first deploy that carries the merge. |
What
A new feature page,
/features/github(en, ja, ko), and a homepage section for the GitHub integration: PR reviews, CI observability and the post-merge check.Feature page
/code-reviewanalytics capture.components/github/PrReviewComment.astro). Content is literal, like docs snippets.PostMergeComment.astro) with commit context, deploy markers and PR-closes-issue.error-trackingandai-mcp-integrationnow link here.Homepage
GitHubSectionafter the agent section: before merge, in CI, after it ships. Compact versions of both comment cards and a CSS crop of the CI tab capture (the full frame is unreadable at a third of the shell).Screenshots, through the existing
bun run screenshotsworkflow:surface-code-review,gallery-code-review-pr,surface-ci,gallery-ci-traceadded toshots.tsand checked in.scripts/seed-demo/code-review.ts(bun run seed:demo:code-review) fills the demo org with PR reviews and findings. It refuses any database butmaple_screenshots. CI runs come from the existingscripts/seed-ci-runs.ts.Notes
illustrationis unset, so the hero uses the plain dot-grid treatment. A Roman engraving should follow like the other feature pages.POST /mcpandGET /mcptwice each; the card keeps one row of each. Looks like a duplicate-row bug in the post-merge table, worth a separate look.bun.lockpicks up a few unrelated workspace version bumps because the lockfile on main was out of date.Checks
bun run testin apps/landing: 85 passed.astro build: 233 pages, no new warnings./features/github,/ja/features/githuband the homepage section in a browser at 1440 wide.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.