-
Notifications
You must be signed in to change notification settings - Fork 966
Expand file tree
/
Copy path.pr_agent.toml
More file actions
50 lines (43 loc) · 2.12 KB
/
Copy path.pr_agent.toml
File metadata and controls
50 lines (43 loc) · 2.12 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
46
47
48
49
50
[github_app]
# Commands run automatically when a PR is opened.
pr_commands = [
"/agentic_describe",
"/agentic_review",
]
# Re-run commands when new commits are pushed to the PR.
handle_push_trigger = true
# Commands run automatically on push (requires handle_push_trigger = true).
push_commands = [
"/agentic_review",
]
[config]
# Skip automated reviews on bot-authored PRs (e.g. dependency bumps or CI bots).
# Qodo auto-detects most bots; these are listed explicitly to be safe.
ignore_pr_authors = [
"dependabot[bot]",
"renovate[bot]",
"teambit-ci",
]
# Optional: also skip reviews on chore/ci PRs by title (regex list).
# Left commented so maintainers can opt in. Note that bot dependency bumps
# are already covered by ignore_pr_authors above.
# ignore_pr_title = ["^chore", "^ci"]
[review_agent]
# A re-review triggered by a push looks only at what changed since the previous review, instead of
# going over the whole PR again. This is the documented default; it is stated here so the repo owns
# the setting rather than inheriting it, and so it is not left to a portal-level default.
enable_incremental_review = true
# Extra instructions for the Issues Agent (bug, security, performance detection).
# There is no setting that stops a finding from being raised again after it was answered, so the two
# rules below are asked for in the prompt instead.
issues_user_guidelines = """
- Do not raise a finding that has already been raised on this PR and answered, unless a later commit
changed the code it is about. Where a maintainer has replied explaining that the behavior is
deliberate, treat the matter as settled rather than reopening it in a new round.
- Judge a finding that asks for a test to move from the e2e suite to a unit test by the CI cost the
move would actually remove - the number of processes the case spawns, not the number of assertions
it makes. A case that reuses a workspace an adjacent case already builds spawns nothing of its own,
so moving it saves no CI time and the finding is not worth raising.
"""
# Extra instructions for the Compliance Agent (rule checking).
# compliance_user_guidelines = ""