.coderabbit.yaml

# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

language: "en" # English
early_access: false
inheritance: true
reviews:
  profile: chill
  request_changes_workflow: false
  high_level_summary: true
  commit_status: true
  poem: false
  review_status: false
  collapse_walkthrough: true
  estimate_code_review_effort: false
  sequence_diagrams: false
  changed_files_summary: false
  auto_review:
    enabled: true
    drafts: false
  finishing_touches:
    docstrings:
      enabled: false
    unit_tests:
      enabled: false
  suggested_labels: true
  high_level_summary_instructions: |
    - Never use emoticons or emojis in the summary.
    - Use bullet points or numbered lists for clarity.
    - Keep it short and each section should be no more than 200 words.
    - The Changes Summary table should be concise with only essential file paths (relative to repo root).
    - Divide the summary into five sections:

    1. **Description**: Describe the main change in the pull request in 60 words max. Explain what was changed, why it was needed, and the approach taken.
    2. **References**: A list of links to discussions, issues and pull requests related to the changes. You can look up for documentation, issues, or other pull requests that provide context or background for the changes.
    3. **Dependencies & Requirements**: List any new dependencies added or updated. Mention environment variable changes, configuration updates, or version requirements.
    4. **Contributor Summary**: A table showing contributions (lines of code added, removed, files changed) made by the contributor in this pull request. Format: `| Contributor | Lines Added | Lines Removed | Files Changed |`
    5. **Changes Summary**: A table summarizing the changes made in the pull request, including file paths (relative to repo root) and a brief description of the change. Format: `| File Path | Change Description |`
chat:
  auto_reply: false
  art: false