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
Findings display
Resolved findings
Bitbucket and Gerrit do not support collapsible sections. As a result, resolved findings beyond the overflow breakpoint are not displayed. You can view them in the Qodo portal instead.
Expanded sections in findings
Show content section titles
Inline comment sections
Review workflow
Gerrit work-in-progress changes are treated as drafts. Qodo skips new patch sets while a change is work in progress, so
feedback_on_draft_pr cannot enable automatic feedback for them.
CI feedback
Ignore rules
Gerrit changes do not have a source branch separate from the change ref. Gerrit hashtags are used as labels for
ignore_pr_labels.
Comment commands
You can trigger these commands in Pull Request (PR) comments or Gerrit change comments.
On Gerrit,
/generate_labels applies hashtags to the change.