xiaxinhang/pr-agent
1
0
Fork 0
mirror of https://github.com/qodo-ai/pr-agent.git synced 2025-07-20 20:40:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

extra_labels

Browse Source
This commit is contained in:
mrT23
2023-11-15 14:02:13 +02:00
parent e878bbbe36
commit 9478447141
4 changed files with 32 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pr_agent/settings/configuration.toml
View File

@ -21,6 +21,7 @@ require_score_review=false
require_tests_review=true
require_security_review=true
require_estimate_effort_to_review=true
#
num_code_suggestions=4
inline_code_comments = false
ask_and_reflect=false
@ -28,6 +29,9 @@ automatic_review=true
remove_previous_review_comment=false
persistent_comment=true
extra_instructions = ""
# review labels
enable_review_labels_security=true
enable_review_labels_effort=false
# specific configurations for incremental review (/review -i)
require_all_thresholds_for_incremental_review=false
minimal_commits_for_incremental_review=0

5
pr_agent/settings/pr_reviewer_prompts.toml
View File

@ -93,7 +93,7 @@ PR Analysis:
description: >-
Estimate, on a scale of 1-5 (inclusive), the time and effort required to review this PR by an experienced and knowledgeable developer. 1 means short and easy review , 5 means long and hard review.
Take into account the size, complexity, quality, and the needed changes of the PR code diff.
Explain your answer shortly (1-2 sentences).
Explain your answer shortly (1-2 sentences). Use the format: '1, because ...'
{%- endif %}
PR Feedback:
General suggestions:
@ -130,7 +130,8 @@ PR Feedback:
Security concerns:
type: string
description: >-
yes\\no question: does this PR code introduce possible vulnerabilities such as exposure of sensitive information (e.g., API keys, secrets, passwords), or security concerns like SQL injection, XSS, CSRF, and others ? If answered 'yes', explain your answer briefly.
does this PR code introduce possible vulnerabilities such as exposure of sensitive information (e.g., API keys, secrets, passwords), or security concerns like SQL injection, XSS, CSRF, and others ? Answer 'No' if there are no possible issues.
Answer 'Yes, because ...' if there are security concerns or issues. Explain your answer shortly.
{%- endif %}
```