Walkthrough

Adds explicit permissions and an ID to the clang-format check in the CI workflow and adds a follow-up step that uses parkerbxyz/suggest-changes to comment/request changes on PRs when formatting fails. Also applies a whitespace-only change in a C++ source file with no functional impact.

Changes

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant PR as Pull Request
  participant GH as GitHub Actions
  participant Job as check-code-formatting
  rect #E8F8F5
    Dev->>PR: Open or update PR
    PR->>GH: Trigger workflow
    GH->>Job: Run formatting job (permissions set)
    Job->>Job: Run clang-format step (id: clang-format)
  end
  alt Formatting passes
    Job-->>PR: Report success
  else Formatting fails
    rect #FFF4E6
      Job->>PR: Run suggest-changes action (post comment, REQUEST_CHANGES)
      Job-->>PR: Report failure / changes requested
    end
  end

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I nibbled the YAML, neat and bright,
A comment hops when checks aren’t right.
With whiskered care I tap my paw—
“Please fix the formats, mind the law.”
One space here, one hop there—🐇✨

Pre-merge checks and finishing touches

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

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 @coderabbitai help to get the list of available commands and usage tips.}