.coderabbit.yaml

# SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: Apache-2.0
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
# https://docs.coderabbit.ai/getting-started/configure-coderabbit/
# In PR, comment "@coderabbitai configuration" to get the full config including defaults
language: "en-US"
reviews:
  profile: chill
  auto_title_placeholder: '@coderabbitai title'
  auto_title_instructions: 'Format: "[<category>] <title>". Category must be one of: fix, feat, doc, infra, style, refactor, perf, test, chore, revert. Enclose the category in square brackets. Title should be concise (<= 60 chars). Example: "[feat] Add logit_bias support".'
  commit_status: false
  high_level_summary_instructions: |
    Always produce two review sections in the summary:

    **Dev Engineer Review**
    Review all changes for correctness and consistency, including:
    - Code changes: correctness, performance, API consistency (CODING_GUIDELINES.md), error handling, regressions.
    - Config files: valid values, no typos, consistency with related configs, no unintended scope changes.
    - Test list files (test-db/, qa/, waives.txt): correct format, valid test paths, appropriate bug references, no duplicates.

    **QA Engineer Review**
    Always include this section when any files under tests/ are touched.
    For test-list-only changes (only tests/integration/test_lists/ files):
      - List which test-db/ or qa/ files were modified and what entries were added or removed.
      - Verdict: "needs follow-up" if CBTS coverage data is unavailable, otherwise "sufficient" or "insufficient".
    For test-code changes (files outside tests/integration/test_lists/):
      - List test functions added, modified, or removed.
      - State whether each is covered in tests/integration/test_lists/ (test-db/ for CI, qa/ for manual QA).
      - Verdict: sufficient, insufficient, or needs follow-up.
    If no test files are touched, write "No test changes."
  collapse_walkthrough: false
  assess_linked_issues: true
  related_issues: true
  related_prs: true
  suggested_labels: true
  suggested_reviewers: true
  poem: false
  review_status: false
  auto_review:
    auto_incremental_review: true
    drafts: false
    base_branches: ["main", "release/.+"]
  path_instructions:
    - path: "tests/**"
      instructions: |
        Act as a QA engineer reviewing test changes and coverage for TensorRT-LLM.
        Always produce a test coverage summary, even if no issues are found.

        If the change touches ONLY files under tests/integration/test_lists/ (no test-code changes):
        - Report which test-db/ or qa/ list files were modified and what entries were added or removed.
        - Do NOT require changed test functions for this path.
        - Use verdict "needs follow-up" when cbts_touchmap.sqlite or a CBTS coverage report is unavailable
          to confirm the impacted test scope; otherwise use "sufficient" or "insufficient".

        If the change includes test-code files (outside tests/integration/test_lists/), the summary must include:
        1. Which test functions were added, modified, or removed.
        2. Whether each changed test is listed in the appropriate test list files under
           tests/integration/test_lists/ (test-db/ for CI, qa/ for manual QA).
        3. A coverage verdict: sufficient, insufficient, or needs follow-up.
        Keep feedback actionable: reference concrete list file names when suggesting additions.
    - path: "tests/integration/test_lists/qa/**"
      instructions: |
        Files here are manually-triggered QA perf/regression lists, maintained
        by the QA team. They are NOT derived from, and do NOT need to mirror,
        the auto-run CI test-db under tests/integration/test_lists/test-db/.
        Do NOT suggest cross-syncing entries between qa/ and test-db/; coverage
        in one does not imply coverage in the other and is decided independently.
    - path: "tests/integration/test_lists/test-db/**"
      instructions: |
        Files here drive the auto-run CI test-db (per-GPU l0_*.yml tiers).
        Adding or removing entries here changes what CI runs either in every PR (pre-merge) or three times a day (post-merge).
        Do NOT suggest cross-syncing with the QA lists under
        tests/integration/test_lists/qa/.
    - path: "tests/integration/test_lists/**"
      instructions: |
        Files here (waives.txt and the *.txt/*.yml list files) are plain-text
        test-list data files, not source code. By repo convention they carry no
        NVIDIA copyright/license header. Do NOT require or suggest adding a
        copyright header to these files.
knowledge_base:
  code_guidelines:
    enabled: true
    filePatterns: ["**/CODING_GUIDELINES.md"]