Skip to main content
When a review summary comment exceeds your Git provider’s size limit, Qodo trims its content to fit. It removes less important content first, preserving findings for as long as possible. Warnings identify what was removed, and the full findings remain available in the Qodo portal.

Why Qodo trims review comments

A Git provider does not accept a comment above its maximum size. Cutting the end off such a comment to make it fit can remove important content and break the comment’s formatting. Instead, Qodo fits the comment within the limit by choosing what to leave out. A comment within the limit is posted unchanged. Trimming applies only to the review summary comment, not to inline comments on code lines.

Comment size limits by Git provider

The table lists the limit Qodo applies on each provider. On a number of providers, this limit is lower than the largest comment the provider accepts. Qodo counts characters on every provider except Gerrit, where it counts bytes. As a result, on Gerrit, emoji and non-Latin characters use more of the limit than plain ASCII text.

What Qodo trims first

When the review summary comment is over the limit, Qodo removes content in the order below, least important first, and skips any content the comment does not include. After each step, Qodo measures the comment again and stops as soon as it fits. As a result, a comment loses only as much content as it needs to. In steps 5 to 10, Qodo starts from the last finding in the comment and works upward, removing content from lower-priority findings first. A finding is removed only after its code snippet, Relevance, Evidence, and Agent prompt sections have all been removed. If a single finding is larger than the entire limit, Qodo shows that finding in part and adds this notice:
This finding exceeds the comment size limit and was truncated. View the full findings in the Qodo portal.

Warnings for content removed from a comment

Qodo adds one warning for each kind of content it removed, just above the footer, with the most important first. A trimmed comment shows up to three warnings:
Each warning ends with a link:
  • View findings: Opens the pull request’s findings in the Qodo portal.
  • Learn more: Opens this page. If the pull request’s findings are not available in the Qodo portal, every warning shows this link instead of View findings.
GitHub, GitLab, and Azure DevOps show each warning in its own box. Bitbucket and Gerrit support standard Markdown only. As a result, each warning appears as a quoted line on those providers.