-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.coderabbit.yaml
More file actions
45 lines (41 loc) · 2.14 KB
/
.coderabbit.yaml
File metadata and controls
45 lines (41 loc) · 2.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
tone_instructions: >
Provide exact, committable GitHub `suggestion` blocks when possible. Keep fixes minimal and compile-safe; explain when exact code isn’t feasible. Consolidate feedback per file into one pass.
reviews:
# optional: tends to be more direct/more “do this” than “consider…”
profile: assertive
request_changes_workflow: true
collapse_walkthrough: true
estimate_code_review_effort: false
suggested_labels: false
in_progress_fortune: false
high_level_summary_in_walkthrough: true
poem: false
auto_review:
ignore_title_keywords:
- '[WIP]'
- '[DO NOT MERGE]'
- '[RELEASE]'
base_branches:
- .*
path_instructions:
- path: "**/*.{js,ts,tsx,jsx,php}"
instructions: |
In addition to default instructions, perform a detailed review of the provided code with following key aspects in mind:
- Verify compliance with WordPress and WordPress VIP coding standards and best practices.
- Check for proper escaping and sanitization of data to prevent security vulnerabilities.
- Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features.
For any `register_post_meta` calls, ensure the following:
- 'show_in_rest' is set to true for REST API visibility and support for the real-time collaboration functionality.
- 'type' is correctly defined (e.g., 'string', 'integer', 'boolean') according to the expected data type.
**Output requirements for fixes**
- If you identify an issue that can be fixed locally, include a GitHub Suggested Change block using:
```suggestion
<exact replacement code>
```
- Make the suggestion directly committable: exact syntax, correct indentation, and valid PHP/JS.
- Prefer one suggestion per comment (small, focused diffs). Avoid “pseudo-code” or hand-wavy guidance.
- Only fall back to plain instructions when multiple files or larger refactors are required.
chat:
art: false
auto_reply: false