.pr_agent.toml

# Use this page: 'https://qodo-merge-docs.qodo.ai/ai_search/' to ask questions about the configuration options.

[config]
duplicate_prompt_examples = false
# seed
seed=-1 # set positive value to fix the seed (and ensure temperature=0)
temperature=0.2



[pr_reviewer] # /review #
# enable/disable features
require_score_review=false
require_tests_review=false
require_estimate_effort_to_review=true
require_security_review=false
require_todo_scan=true
require_ticket_analysis_review=false

# general options
publish_output_no_suggestions=false # Set to "false" if you only need the reviewer's remarks (not labels, not "security audit", etc.) and want to avoid noisy "No major issues detected" comments.
# extra_instructions = "Prefix each AI-generated comment with the text 'The following is generated by an AI tool. It may be useful, or can be ignored if it is not useful.'"
num_max_findings = 3
final_update_message = true




[pr_description] # /describe #
add_original_user_description=true
generate_ai_title=false
use_bullet_points=true
extra_instructions = """
Prefix the description with 'This description is generated by an AI tool. It may have inaccuracies'
Add only the following labels, if they apply: 'Bugfix', 'New Target', 'New Feature'
"""
enable_pr_type=true


[pr_code_suggestions] # /improve #
max_context_tokens=24000

commitable_code_suggestions = true
focus_only_on_problems=true
extra_instructions = "Do not suggest that only 1 of each hardware type should be defined. It is okay to have multiple IMU types, multiple types of flash chips, etc. Do not suggest that two different flash chip, two different IMUs, or two different baros shouldn't use the same pins. It is okay for them to use the same pins IF they are the same type of component. DO warn of conflicts created by DIFFERENT types of components using the same pin, such as a PWM defined to use the same pin as the baro. Immediately after the heading 'PR Reviewer Guide', add the following text: 'The following suggestions are generated by an AI tool. They may be useful, or can be ignored if not useful.' Do not say 'The suggestion correctly ...'. Your suggestions could be incorrect, so do not assert that they are correct. Rather, phrase it as a question such as 'should line 6 be ... ?' After generating suggestions, review the generated suggestions, attempting to determine if some of the suggestions may actually not be a good suggestion. That is, self-reflect on whether it's actually a good suggestion. Do NOT suggest that DEF_TIM lines in target.c files should have unique indices in the last two arguments. Those numbers indicate whether an alternate DMA should be used and it is common that all of them may be 0,0."
persistent_comment=true
publish_output_no_suggestions=false

# enable to apply suggestion 💎
apply_suggestions_checkbox=true
# suggestions scoring
suggestions_score_threshold=6 # [0-10]| recommend not to set this value above 8, since above it may clip highly relevant suggestions


# Suggestion impact 💎
publish_post_process_suggestion_impact=true
wiki_page_accepted_suggestions=true
allow_thumbs_up_down=true

[pr_compliance]
enable_security_section = false
enable_ticket_section = false
enable_codebase_duplication_section = false
enable_custom_compliance_section = false
extra_instructions = "Do not mentioned secure error handling. This is not intended to be a secure application. Do not mention audit trials or logging of changes. Do not say audit. Do not say logging"

# [pr_custom_prompt] # /custom_prompt #
# prompt = """\
# The code suggestions should focus only on the following:
# - ...
# - ...
# ...
# """
# suggestions_score_threshold=0
# num_code_suggestions_per_chunk=3
# self_reflect_on_custom_suggestions=true
# enable_help_text=false


[pr_add_docs] # /add_docs #
extra_instructions = ""
docs_style = "Sphinx" # "Google Style with Args, Returns, Attributes...etc", "Numpy Style", "Sphinx Style", "PEP257", "reStructuredText"
file = ""              # in case there are several components with the same name, you can specify the relevant file
class_name = ""        # in case there are several methods with the same name in the same file, you can specify the relevant class name

[pr_update_changelog] # /update_changelog #
push_changelog_changes=false
extra_instructions = "Be concise with the changelog descriptions"
add_pr_link=true
skip_ci_on_push=true

[auto_best_practices]
extra_instructions = "Only show auto best practices for which there is high confidence that they are likely to be helpful"