7.5: Create README Documentation

[justin808]

Overview

Document the demo application.

Parent Epic: #70
Priority: P2

Prerequisites

• All previous issues complete

Next Issues (after this is complete)

• None - this is the final issue

Acceptance Criteria

• README.md with project overview
• Setup instructions (prerequisites, installation, running locally)
• Architecture explanation (RSC patterns used)
• File structure documentation
• Key RSC patterns documented with code examples
• Comparison with Next.js version (what's similar, what's different)
• Links to React on Rails Pro documentation
• Contributing guidelines (if accepting contributions)

Implementation Notes

README sections to include:

1. Overview - What this demo shows
2. Live Demo - Link to deployed version
3. Quick Start - Get running in 5 minutes
4. Architecture - How RSC works with Rails
5. Key Patterns - Server vs Client components
6. Comparison - Next.js vs React on Rails Pro
7. Learn More - Links to RoR Pro docs

Reference the original Vercel demo:
https://github.com/vercel/next-react-server-components

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar & Duplicate Issues

Related Issues

• shakacode/react_on_rails-demos#71
• shakacode/react_on_rails-demos#70
• shakacode/react_on_rails-demos#72
• shakacode/react_on_rails-demos#73
• shakacode/react_on_rails#1842

🔗 Related PRs

shakacode/react_on_rails#1744 - Update RSC docs [merged] | docs/react-on-rails-pro/react-server-components.md:
"""

AI-generated summary of changes

The React Server Components (RSC) section was expanded with more detailed, linked case studies and specific performance metrics from multiple sources including productonboarding.com, GeekyAnts.com, Airbnb, and Meta. The original brief bullet points were replaced by richer descriptions with direct links and additional statistics such as total blocking time reduction, improvements in core web vitals, time to first byte, time to interactive, first contentful paint, server response time, and maintenance complexity. A clarifying note was added that only the first case study compares equivalent applications with and without RSC, while others may include additional changes like dependency upgrades.

The SSR Streaming section was similarly enhanced by replacing terse bullet points with detailed references to an academic experiment at Nordnet, Hulu’s case study, and styled-components v3.1.0 streaming SSR support. The Nordnet experiment includes both positive results (faster time to first byte and total blocking time) and a negative result (2% increase in server load). The previous separate "Core Web Vitals & TTI Improvements" section was removed, and its content was integrated into the SSR Streaming section with updated references.

The references section at the end was removed, with all links now embedded inline in the text. Overall, the update provides a more comprehensive, evidence-backed presentation of the performance benefits of React Server Components and SSR Streaming in React on Rails Pro.

Alterations to the declarations of exported or public entities

None. The changes are limited to documentation content and formatting without modifications to exported or public code entities.
"""
shakacode/react_on_rails#1813 - 📚 Comprehensive documentation improvements for enhanced developer experience [merged] | AI_AGENT_INSTRUCTIONS.md:
"""

AI-generated summary of changes

Adds a new documentation file named AI_AGENT_INSTRUCTIONS.md containing concise, copy-paste instructions for AI agents to set up React on Rails in common scenarios. The content includes: a pre-check for current versions, Scenario 1 for creating a new Rails app with React on Rails (app creation, adding react_on_rails with strict options, install generator, accepting bin/dev changes, starting bin/dev, and a success check at /hello_world), Scenario 2 for integrating into an existing Rails app (adding the gem with strict option, install generator, accepting bin/dev changes, starting bin/dev), and a list of common troubleshooting commands (test with bin/dev, kill conflicting processes, doctor command). The file emphasizes starting the development server with bin/dev and a success verification URL.

Alterations to the declarations of exported or public entities

• No exported or public API declarations were modified or added. No signatures changed.
  """

---

README.md:
"""

AI-generated summary of changes

• Documentation content updated with extensive rewording and restructuring:

  • Section header change: News to ⚡ What's New.
  • News content updated to highlight v16.0 release with modernizations.
  • About section renamed to 🎯 About React on Rails with expanded introductory blurb.
  • Then-new introductory tone: adds a quote and community/authorship line.
  • Upgraded “Documentation” area to “📚 Quick Start,” adding quick-start links and a more prominent onboarding path.
  • Replacing old Feature/Why React on Rails list with a structured feature table (✨ Why React on Rails?) containing features, benefits, and links.
  • Added emphasis on React on Rails Pro and its features (Server Components, streaming SSR, etc.).
  • Replaced previous online/demo references with updated quick-start and live-demo links.
  • Numerous minor wording and formatting changes (emojis, bulleting, section ordering) throughout to reflect a refreshed marketing/documentation stance.

• Overall effect: observable semantic shift from a general News/About/Documentation narrative to a modernized, feature-focused, quick-start oriented README with enhanced onboarding and Pro features emphasis.

Alterations to the declarations of exported or public entities

• None. There are no changes to declarations of exported or public code entities in this diff.

Estimated code review effort: Medium
"""

---

docs/README.md:
"""

AI-generated summary of changes

Adds a comprehensive documentation hub at docs/README.md for React on Rails, outlining a navigable structure with sections: Quick Start, Learning Paths (Beginner and Experienced), Migrating guides, Popular Use Cases with a guidance table, Complete Documentation (Core Guides, Features, Development, Deployment & Performance), Help (Troubleshooting, FAQ, Error Messages), Community and Professional Support, External Resources, and a detailed Table of Contents covering API References, Guides (Getting Started, Core Features, State Management, Routing, Advanced Topics, Development, Deployment, Migration Guides, Troubleshooting, Contributing), plus Migration Guides, Troubleshooting, and Contributing sections. No code or public API declarations are modified.

Alterations to the declarations of exported or public entities

• None
  """

---

docs/contributor-info/pull-requests.md:
"""

AI-generated summary of changes

The header text under Doc Changes changed from "### Links to other docs:" to "### Links to other docs" (colon removed). This is a formatting change to a markdown heading; the subsequent bullet and example remain unchanged.

Alterations to the declarations of exported or public entities

No changes to exported/public declarations detected.

Estimated code review effort: Low
"""

---

docs/getting-started.md:
"""

AI-generated summary of changes

• Replaced initial guidance with a multi-path starting-point structure, introducing a prominent quick-start link and clearly categorized starting options (New to React on Rails, Have an existing Rails app, Want comprehensive tutorial, Learn by example).
• Introduced a System Requirements block and reorganized content around starting points, updating compatibility details (Shakapacker, Rails, Ruby, Node).
• Reworked Basic Installation: shifted to a streamlined, install-first flow with a distinct “React on Rails Installation” section; removed earlier inline server-rendering toggles narrative; adjusted commands and steps, including explicit gem installation guidance.
• Removed the former step-by-step “Turning on server rendering” narrative; condensed server rendering guidance into a more general render-availability discussion.
• Updated “Including your React Component on your Rails Views” to emphasize using react_component after installation, with clarified server-side rendering guidance and terminology adjustments.
• Expanded and reorganized the Auto-Bundling/Auto-Registration concept, detailing both manual and auto-loading approaches and tying them to example usage and references.
• Reworked the Exposing/Registration workflow to address server-vs-client considerations, the interaction between component exposure, bundling, and registration, and expanded examples showing both manual and auto-bundling paths.
• Enhanced the Specifying Your React Components section to differentiate between direct registration and render-functions, including railsContext usage, required function signatures, and return-value guidance; added explicit notes on detecting render-functions and adjusted narrative around render-function behavior.
• Expanded render-function-related topics: clarified render-function returns (including server rendering results), and integrated react_component_hash usage with server-rendering scenarios and react-helmet considerations.
• Added a More Reading and Additional Resources section with a structured progression and links to API docs, tutorials, configuration, and migration guides; updated I18n references.
• Reorganized and renamed several subsections to reflect new terminology and workflows, including server/client rendering handling, bundling configurations, and exploration of server-specific vs client-specific code paths.
• Maintained and extended guidance on I18n and view-helper references, but reflowed the content to align with the new starting-point and workflow structure.
• Overall, a substantial restructuring and content expansion of the getting-started flow, with emphasis on practical starting points, updated installation steps, and richer guidance on component exposure, bundling, and server rendering scenarios.

Alterations to the declarations of exported or public entities

• None detected. No changes to exported/public code signatures or API declarations.

Estimated code review effort: High
"""

---

docs/guides/auto-bundling-file-system-based-automated-bundle-generation.md:
"""

AI-generated summary of changes

• Updated the document title from "File-System-Based Automated Bundle Generation" to "Auto-Bundling: File-System-Based Automated Bundle Generation".
• Removed the entire subsection "8. Installation order issues", including the problem description and proposed solutions, effectively eliminating guidance on installation order and related steps.

Alterations to the declarations of exported or public entities

• No exported/public declarations modified.

Estimated code review effort: Low
"""

---

docs/guides/how-to-use-different-files-for-client-and-server-rendering.md:
"""

AI-generated summary of changes

Minimal formatting updates to headings in the Webpack-resolve guidance pages. All changes remove trailing colons from header lines; no changes to logic, control flow, or error handling. Code blocks and examples remain unchanged; no observable behavioral modifications.

Alterations to the declarations of exported or public entities

• No public exported API changes detected.

Estimated code review effort: Low
"""

---

docs/guides/tutorial.md:
"""

AI-generated summary of changes

• Renamed the "Table of Content" heading to "Table of Contents" (plural) and removed the trailing colon.
• Removed the trailing colon from the "Swap out sqlite for postgres" subsection header. No other content or logic is altered; no functional changes.

Alterations to the declarations of exported or public entities

• Public/exported declarations: none

Estimated code review effort: Medium
"""

---

docs/guides/upgrading-react-on-rails.md:
"""

AI-generated summary of changes

• Client Webpack config header punctuation changed: from "###### Client Webpack config:" to "###### Client Webpack config" (colon removed). No other changes.

Alterations to the declarations of exported or public entities

• No exported/public declarations were changed.

Estimated code review effort: Low
"""

---

docs/javascript/render-functions.md:
"""

AI-generated summary of changes

• Updated headings by removing trailing colons in multiple sections for react_component and react_component_hash, resulting in headers like "When to use" and "Not suitable for" instead of "When to use:" and "Not suitable for:".

• Minor content adjustment under react_component_hash: added an extra bullet line in the Requirements section stating that all other keys are optional and can be accessed in your Rails view.

• No changes to the core behavior or examples; the changes are stylistic (header formatting) plus a single additional bullet in the public API section.

• No changes to public/exported declarations.

Estimated code review effort: Low
"""

---

docs/outdated/rails-assets-relative-paths.md:
"""

AI-generated summary of changes

• Minor typographic tweak: the heading "Here's a full example of a webpack.config.js configured with file-loader to load images" had its trailing colon removed in the updated version. No functional changes.

• No changes to declarations of exported or public entities.

Estimated code review effort: Low
"""

---

docs/quick-start/README.md:
"""

AI-generated summary of changes

Introduces a new documentation file at docs/quick-start/README.md containing a comprehensive 15-minute quick start guide for integrating React with Rails via React on Rails. The guide covers prerequisites (React on Rails 16.0+, Shakapacker 7+, Rails 7+, Ruby 3.0+, Node.js 18+, Yarn), installation (adding the gem, running the installer), running a development server, viewing and editing a React component, embedding components in Rails views with auto-bundling, and a quick reference of commands, file locations, and next steps. It includes step-by-step commands, example code snippets (Ruby, JavaScript/JSX, and ERB), and notes on auto-bundling behavior, server startup, hot-reloading, and deployment considerations. The document ends with a “What you’ve accomplished” section, quick reference, and links to advanced topics and troubleshooting.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity declarations detected.
  """

---

docs/troubleshooting/README.md:
"""

AI-generated summary of changes

Adds a comprehensive Troubleshooting Guide to docs/troubleshooting/README.md. The new document introduces a structured, end-to-end reference for diagnosing and fixing common React on Rails issues across stages: Quick Diagnosis, Installation Issues, Build Issues, Runtime Issues, Server-Side Rendering Issues, Performance Issues, Advanced Debugging, and a still-stuck section for collecting details and seeking help. Each section contains concrete error messages, checklists, and reproducible commands or code snippets. The guide covers:

• Quick Diagnosis table linking problem areas to sections.
• Installation issues with commands for uncommitted changes and Node/Yarn not found scenarios.
• Build issues with module resolution, Webpack failures, and ExecJS runtime guidance.
• Runtime issues including component rendering failures, window usage on SSR, and prop-updating problems, with code samples.
• SSR-specific issues like prerendering, runtime availability, and hydration warnings.
• Performance guidance for slow builds and large bundles, including caching and bundle analysis.
• Advanced debugging steps for verbose logging and webpack config inspection.
• A “Still Stuck?” section listing information to gather and avenues for community or professional support.

No changes to public APIs or exported declarations are present; this is purely documentation content.

Alterations to the declarations of exported or public entities

• None (no changes to exported/public code entities).

Estimated code review effort: Low
"""

---

lib/tasks/generate_packs.rake:
"""

AI-generated summary of changes

• Updated two documentation file links in the React on Rails pack generation task to reference auto-bundling variants of the file-system based automated-bundle-generation guide. The changes replace references to file-system-based-automated-bundle-generation.md with auto-bundling-file-system-based-automated-bundle-generation.md in two places:
  • In the common error guidance about conflicting common/client/server component files.
  • In the documentation section listing guides for file-system based components.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity declarations.

Estimated code review effort: Low
"""

---

spec/dummy/client/README.md:
"""

AI-generated summary of changes

Removed the trailing colon from the instruction line under "Updating Node Dependencies" in spec/dummy/client/README.md. The line changes from “# Make sure you are in the client directory, then run:” to “# Make sure you are in the client directory, then run” (no functional impact).

Alterations to the declarations of exported or public entities

• No changes to exported or public declarations detected.

Estimated code review effort: Low
"""

---

docs/api/README.md:
"""

AI-generated summary of changes

Adds a new documentation file docs/api/README.md serving as the API Reference index. The file introduces a top-level header "API Reference" with a brief description "Complete API documentation for React on Rails." and lists three internal links to further API docs: View Helpers API, Redux Store API, and JavaScript API.

• File added: docs/api/README.md

Estimated code review effort: Low
"""

---

docs/guides/advanced/README.md:
"""

AI-generated summary of changes

Adds a new documentation page at docs/guides/advanced/README.md detailing advanced features. The content introduces an "Advanced Features" section for React on Rails, provides a brief description, and lists three linked subsections: Auto-Bundling, Server-Side Rendering, and Performance Optimization, with relative links to their respective documents. The new file serves as an index for advanced topics and patterns.

• No exported/public entity declarations were modified.

Estimated code review effort: Low
"""

---

docs/additional-details/recommended-project-structure.md:
"""

AI-generated summary of changes

• In the documentation, the code fence for the shell command was changed from sh to bash, while the mv command remains the same (mv app/javascript client). This is a formatting change only; no functional/path changes.

• No changes to exported/public declarations.

Estimated code review effort: Low
"""

---

docs/guides/rails-webpacker-react-integration-options.md:
"""

AI-generated summary of changes

• In the React Hot Loader (Deprecated) section, the code fence label was changed from sh to bash for the command block:
  • Before: ```sh
  • After: ```bash
  • The actual command remains the same: yarn add --dev react-hot-loader @hot-loader/react-dom
• This is a minor formatting adjustment of the code block language specifier; no behavioral or functional changes.

Alterations to the declarations of exported or public entities

• No exported or public entity signatures were added, removed, or modified.

Estimated code review effort: Medium
"""

---

docs/javascript/capistrano-deployment.md:
"""

AI-generated summary of changes

• Updated the code fence language specifier for the shell command from sh to bash in the docs, leaving the bundled command and surrounding text unchanged. No functional changes or control-flow alterations.

• Alterations to the declarations of exported or public entities

• No changes to public/exported declarations detected.

Estimated code review effort: Low
"""

---

docs/planning/DOCS_PR_SUMMARY.md:
"""

AI-generated summary of changes

This diff adds a comprehensive documentation planning and improvement narrative for React on Rails. Observable changes include:

• Creation of new documentation structure and content plan:

  • Added new top-level landing and guidance pages:
    • docs/README.md
    • docs/quick-start/README.md
    • docs/troubleshooting/README.md
    • DOCUMENTATION_IMPROVEMENT_PLAN.md

• Enhancement of existing documentation:

  • README.md updated for improved visuals and organization
  • docs/getting-started.md streamlined with clearer user paths

• Introduction of visual and organizational improvements described throughout:

  • Consistent emoji usage, tables, checklists, callout boxes, and improved headings
  • Shorter, clearer language with more practical code examples
  • Added progress indicators and cross-references

• UX and navigation enhancements outlined:

  • Multiple entry points by user type
  • Clear next steps, cross-topic references, and dedicated reference materials

• Quality and outcomes focus:

  • Documentation validation, link checks, mobile responsiveness
  • Defined success metrics (time-to-first-success, reduced bounce, etc.)

• Implementation roadmap:

  • Phase 1: core structural and visual improvements plus essential new content
  • Phase 2/3: future interactive tutorials, video content, site redesign, analytics

• Review and success criteria included:

  • Checklist for content accuracy, links, formatting, structure safety, accessibility, and SEO
  • Success metrics related to reduced questions, faster onboarding, and improved engagement

• Public/exported declarations: No changes

Alterations to the declarations of exported or public entities

• No exported/public entity signatures modified or introduced in this diff.

Estimated code review effort: High
"""

---

docs/planning/DOCUMENTATION_IMPROVEMENT_PLAN.md:
"""

AI-generated summary of changes

A new documentation planning file docs/planning/DOCUMENTATION_IMPROVEMENT_PLAN.md was added. It outlines a comprehensive plan to restructure and improve React on Rails documentation, focusing on navigation, clarity, and visual design. The plan defines current issues (navigation complexity, content clarity, and visual presentation), proposed structural reorganization (landing README, quick-start, guides with fundamentals/advanced/deployment, API reference, examples), and content improvements (clear learning path, added visuals, more examples, simplified language, troubleshooting). It includes design system recommendations (consistent formatting, standardized code blocks, color-coded callouts) and interactive elements (expandable sections, copy-to-clipboard, progress indicators, improved search). Specific file-focused improvements are proposed for getting-started.md, tutorial.md, and configuration.md, with added supporting content like flow diagrams, screenshots, and decision trees. New content areas are suggested (troubleshooting, performance, migration guides, architecture decision records) plus enhanced examples (cookbook, real-world examples, video tutorials, interactive demos). Implementation phases (Phase 1–3) outline priorities, success metrics (time to first success, support volume, onboarding, SEO), and next steps for team alignment and ticket creation.

Alterations to the declarations of exported or public entities

• No exported or public declarations were added or modified.

Estimated code review effort: Low
"""

---

docs/javascript/angular-js-integration-migration.md:
"""

AI-generated summary of changes

Changed the StoryBook link presentation from "StoryBook" with an old Storybook URL to "Storybook" with the updated Storybook URL. Specifically:

• Text updated: "StoryBook" → "Storybook"
• URL updated: getstorybook.io → storybook.js.org
  No changes to logic, error handling, or control flow.

Alterations to the declarations of exported or public entities

• None. No exported/public entity declarations were modified.

Estimated code review effort: Medium
"""
shakacode/shakapacker#713 - Enhance Rspack migration documentation with real-world lessons [merged] | docs/rspack_migration_guide.md:
"""

AI-generated summary of changes

• Added a comprehensive Table of Contents with multiple anchors under the Rspack Migration Guide.
• Introduced an explicit Rspack overview blurb and a prominent SSR/relevant context in the Before You Migrate section.
• Expanded the Before You Migrate section to include Migration Timeline Expectations, Testing Strategy, and SSR Considerations.
• Renamed and expanded migration workflow from "Migration Checklist" to "Migration Steps," including a new Step 7: Review Migration Checklist and a detailed list of sub-tasks.
• Replaced and expanded several step headings to emphasize structured guidance (e.g., Step 1/2/3/4/5/6 to Step 1/2/3/4/5/6 with consistent formatting; added Step 7 in the revised flow).
• Added a detailed Configuration Best Practices section with guidance on organizing webpack/rspack configs, CSS Modules override placement, and handling breaking changes.
• Introduced comprehensive SSR/CSS issues guidance (CSS Modules export mode, SSR CSS extraction handling, SWC React runtime with SSR, ReScript module resolution, ReScript dependencies patches).
• Added a new Real-world Migration Example link and updated Migration-related links in the Resources section.
• Included performance guidance and an "Expected Performance Improvements" table, alongside general caching and SWC recommendations.
• Updated the Debugging Configuration section to reflect migration-oriented checks and comparisons between webpack and rspack configurations.
• Adjusted the migration flow examples and code blocks to reflect Rspack-specific commands, options, and file locations.
• Minor wording adjustments and reorganization to align with the new sectional structure while preserving core migration guidance.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""
shakacode/react_on_rails#1865 - Document content_for pattern to prevent FOUC with SSR and auto_load_bundle (#1864) [merged] | docs/core-concepts/auto-bundling-file-system-based-automated-bundle-generation.md:
"""

AI-generated summary of changes

• Replaces the prior CSS not loading Troubleshooting entry with a Root Cause explanation for SSR auto_load_bundle = true, clarifying that append_stylesheet_pack_tag runs too late for the head, causing FOUC; introduces a Solution using the content_for :body_content pattern to render body content first so auto-appends occur before head rendering, plus an explicit alternative to disable auto-loading and manually specify packs.
• Adds a detailed code example demonstrating the content_for pattern, including steps for reordering head and body rendering and ensuring CSS/JS appends occur before head rendering.
• Updates auxiliary notes to reflect Rails document order nuances when using content_for, and adds an Alternative configuration to disable auto_load_bundle.
• Reworks related guidance under “Additional Resources” and retains distinctions for Development with HMR, Development static, and Production modes; clarifies that HMR-related FOUC in development is separate from the SSR auto-loading issue.
• Extends Troubleshooting with a new subsection for “document is not defined” errors during SSR, outlining dynamic imports for browser-only libraries, skeleton fallbacks, and client-only rendering guidance.
• Expands Troubleshooting to include a comprehensive itemized list (7 items) covering issues like bundles not generated, manual pack tags after switching to auto-loading, bundle size, and dev vs prod differences, each with explicit remedies and debugging tips.
• Overall, increases SSR-focused guidance, introduces concrete code patterns for SSR FOUC prevention, and reorganizes Troubleshooting to address additional failure modes beyond SSR/HMR framing.

Alterations to the declarations of exported or public entities

• None
  """

---

docs/deployment/troubleshooting.md:
"""

AI-generated summary of changes

• Updated the Quick Diagnosis table by reordering columns and expanding the installation/section links. Renamed the “Styling (FOUC)” row to match the new label “Flash of Unstyled Content (FOUC)” and added a new FOuC article section with symptoms, root cause, solution, and a quick fix example. Introduced a detailed FOuC guidance block including a sample ERB snippet demonstrating a body-content pattern to render CSS before the head. Removed the old “Performance” alignment in the header of the table. Kept existing sections for Installation, Compilation, Runtime, SSR, and Performance, but adjusted their alignment to accommodate the new FOuC entry and updated anchor references.

[tag: ]

---

Alterations to the declarations of exported or public entities

---

Estimated code review effort: Medium
"""
shakacode/react_on_rails#1987 - Comprehensive rewrite of React on Rails Pro README [merged] | react_on_rails_pro/README.md:
"""

AI-generated summary of changes

• Substantially rewrote README.md to a marketing/documentation hub for React on Rails Pro, replacing technical onboarding with sections like What is Pro, License & Pricing, Why Use Pro, Key Features, Requirements, Getting Started, Documentation, Examples, and Support. The content shifts from technical, feature-driven descriptions to promotional and licensing-focused material, including a dedicated license setup flow, case study references, and centralized examples. Public-facing sections and the monorepo relationships are clarified, with updated links and new sections for licensing, pricing, and contributing. Minor structural separators and visual formatting were added to create a catalog-like documentation site within the README.
• Replaced old Getting Started, Features, and References subsections with condensed, marketing-oriented equivalents and moved detailed feature explanations into named feature sections (Fragment Caching, Prerender Caching, Node Renderer, RSC, Bundle Caching, Global State Management).
• Updated support, contact, and branding blocks to reflect licensing and commercial positioning, including new licensing FAQ and a sense of enterprise readiness.
• The overall content shift preserves the public-facing, non-functional essence of the README while removing or relocating prior technical onboarding content into documentation files and references.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Minor
"""

👤 Suggested Assignees

• justin808
• ihabadham
• alexeyr-ci2

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false