Conversation
Add docs/ folder with MDX documentation pages: - Getting Started (install, quick start, project structure) - CLI Commands (init, dev, build, start, serve) - Configuration (full chronicle.yaml reference) - Frontmatter (title, description, order, icon) - Components (callouts, tabs, mermaid, code blocks, tables, images) - Themes (default and paper) - chronicle.yaml with paper theme and llms enabled Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds a Chronicle documentation site: one site config file and multiple new MDX docs covering getting started, CLI, configuration schema, frontmatter, built-in MDX components, themes, and Docker usage. No runtime code changes. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/components.mdx`:
- Around line 67-72: The docs table incorrectly states Callout's outline default
as false; update the Callout prop table in docs/components.mdx to reflect that
Chronicle's wrapper (CalloutContainer) sets outline to true by default before
spreading user props, so change the `outline` default to `true` (or add a note
that Chronicle forces outline: true unless explicitly overridden) and mention
CalloutContainer by name so readers know the source of the default behavior.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 59792453-af71-4082-9873-dcb50b375866
📒 Files selected for processing (7)
docs/chronicle.yamldocs/cli.mdxdocs/components.mdxdocs/configuration.mdxdocs/frontmatter.mdxdocs/index.mdxdocs/themes.mdx
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
docs/folder with Chronicle's own documentation as MDX pageschronicle.yamlconfigured for self-documenting siteTest plan
chronicle dev --content ./docsand verify all pages renderordervalues/llms.txtand/llms-full.txtroutes work (requires llms PR)🤖 Generated with Claude Code