-
Notifications
You must be signed in to change notification settings - Fork 7
Expand file tree
/
Copy path.coderabbit.yaml
More file actions
43 lines (43 loc) · 1.82 KB
/
Copy path.coderabbit.yaml
File metadata and controls
43 lines (43 loc) · 1.82 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
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
---
reviews:
commit_status: true
tone_instructions: |
Be concise and direct. Focus on:
- Bugs and correctness issues
- Probot API usage patterns
- Handler contract violations
- Test coverage gaps
Avoid commenting on:
- Formatting (handled by linters)
- Subjective style preferences
path_instructions:
- path: src/handlers/**/*.js
instructions: |
Review Probot handler implementation:
- Verify match() function returns boolean based on event/action
- Ensure run() creates check-run with 'in_progress' status
- Confirm run() updates check-run with 'completed' status and proper conclusion
- Check error handling for GitHub API failures
- Validate config parameter usage (handler receives only its own config)
- Ensure proper context.octokit usage patterns
- path: src/auto-me-bot.js
instructions: |
Review main bot orchestration:
- Verify CONFIG_SPEC registration matches handler exports
- Check ON_EVENTS includes all required GitHub webhook events
- Ensure proper handler matching and invocation logic
- path: tests/**/*.js
instructions: |
Review test quality:
- Verify both match() and run() functions are tested
- Check comprehensive mocking of GitHub API (context.octokit)
- Ensure edge cases are covered (missing config, API failures)
- Validate test descriptions are clear and specific
- Confirm full code coverage for critical paths
- path: "**/*.{yml,yaml}"
instructions: |
Review workflow and config files:
- Verify GitHub Actions use pinned versions
- Check proper secret handling
- Validate MkDocs configuration structure