Skip to main content
Qodo configuration options and PR commands vary by Git provider. Use the tables below to check what is supported for your provider.
Qodo strives for feature parity across all providers, but a number of settings are limited by each provider’s capabilities. GitHub, GitLab, and Azure DevOps support extended markdown; Bitbucket Cloud and Bitbucket Data Center support standard markdown only, which is why they do not support all features.

Configuration options

Configuration is managed in the repository’s .pr_agent.toml file or in the Qodo portal. For a full description of each setting, see the Configuration and command reference.

Review output and visibility

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
comments_location_policy
inline_comments_severity_threshold

Findings display

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
finding_overflow_count
resolved_overflow_count

Expanded sections in findings

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
expand_description
expand_code
expand_relevance
expand_evidence
expand_prompt

Review workflow

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
pr_commands
handle_push_trigger
push_commands
demand_self_review
approve_pr_on_self_review
enable_chat_in_code_suggestions

CI feedback

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
enable_auto_checks_feedback
excluded_checks_list
persistent_comment
enable_help_text
final_update_message

Ignore rules

SettingGitHubGitLabBitbucketBitbucket DCAzure DevOps
ignore_pr_title
ignore_pr_source_branches
ignore_pr_target_branches
ignore_pr_labels
ignore_pr_authors
ignore_repositories
allow_only_specific_folders
ignore_languages_frameworks
ignore_ticket_labels

PR commands

These commands can be triggered in pull request comments.
CommandGitHubGitLabBitbucketBitbucket DCAzure DevOps
/agentic_review
/agentic_describe
/ask
⮑ Ask on code lines
/config
/generate_labels
/checks