Mesa can automatically review pull requests when they are opened or published from a draft. This is configurable in the “PR Defaults” -> “Review” section of your Mesa dashboard.
You can also customize review settings on a per-repository basis in the “Repositories” section of your Mesa dashboard.
Mesa’s code review process is designed to be flexible and customizable. To this end, you can customize the types of comments that Mesa should leave.
Logic: Comments that address potential logic issues in the code, usually related to business logic or the overall purpose of the code.
Style: Comments that address potential style issues in the code, usually related to formatting or code readability.
Security: Comments that address potential security issues in the code, usually related to vulnerabilities or potential security risks.
Performance: Comments that address potential performance issues in the code, usually related to inefficient patterns or bottlenecks.
Question: Comments that are questions about the code, usually related to the code’s purpose or functionality, or requests for clarification about the developer’s intent.
Other: Comments that do not fit into the other categories, such as comments about the purpose of the code or the system design.
After reviewing the code, Mesa will classify the comment based on the following criteria:
Low: The comment is a low priority issue, usually nitpicks or style issues. Mostly relevant for low-risk code like frontend, CSS, etc.
Medium: The comment is a medium priority issue, usually related to potential logic issues or missing edge cases / error handling.
High: The comment is a high priority issue, usually related to potential security issues or serious performance issues. Should be used rarely.
You can customize the severity of the comments that Mesa should leave by adjusting the “Minimum comment severity” slider in the “PR Defaults” -> “Review” section of your Mesa dashboard.
For example, if you set the minimum comment severity to “Medium”, Mesa will only leave comments that are either Medium or High severity.
Mesa provides three options for controlling when Mesa should review a pull request:
Automatic Review: This toggle controls whether Mesa should automatically review pull requests when they are opened or published from a draft.
Re-review on Commit: This toggle controls whether Mesa should re-review a pull request when new commits are pushed to the pull request.
Diff line count range: This range controls the PR size that Mesa should review. This is useful for large PRs that may take a long time or require large amounts of tokens to review.
Under the hood, Mesa’s code review process selects from the following review types:
Full Review: Mesa’s agent swarm will review the entire pull request, ignoring any previous reviews.
Incremental Review: Mesa’s agent swarm will review only the changes since the last review, making an effort to skip reviewing unchanged code and avoiding duplicate comments.
Custom Range Review: Mesa’s agent swarm will review a specific range of commits. This is never used automatically, but is available for manual triggering.
When a review is triggered automatically, Mesa will select the appropriate review type based on the following criteria:
If Mesa has never reviewed the pull request before, it will perform a full review.
If Mesa has reviewed the pull request before, it will perform an incremental review.
