Skip to main content
Use Code Review settings to control when reviews run, what they post, and which context they use. Start with a conservative repository pilot, then change one control at a time and verify it on a test pull request. Open Settings → Code Review for workspace controls. Open Code Review → Codebases → Repositories → Show details for repository controls.
PR reviewer configuration controls for priority, style, confidence, approvals, and comment limits

​
Trigger and conversation controls

Keep automatic review limited to one pilot repository until the output and provider permissions are verified.

​
Finding volume and placement

A useful pilot starts with medium-and-above findings, inline comments, and a conservative comment limit. Raise or lower the bar after reviewing acceptance and false-positive patterns.

​
Generated review content

Enable only the artifacts your team uses:
  • High Level Summary
  • Walkthrough
  • Changed Files Summary
  • Auto Generate Title
  • Auto Link Ticket
  • LGTM comments
  • Sequence diagrams
Ticket linking requires the appropriate Jira or Linear connection and scope.

​
Analysis and analytics

Workspace controls can include:
  • Static security analysis through the configured SonarQube-based integration
  • Pull-request metrics collection
  • Pull-request quality scoring and tagging
  • Cross-repository Learnings
  • Cross-organization Learnings
  • Global leaderboard visibility
Cross-organization learning and global visibility can broaden where derived signals appear. Confirm the approved data boundary and opt-out policy before enabling them.

​
Guidelines and Learnings

  • Assign guidelines to the repositories where the rule applies.
  • Review generated guidelines before enabling them.
  • Keep a revision owner for every guideline.
  • Audit Learnings for correct repository scope and continued relevance.
  • Remove Learnings that hide a real issue or outlive the code pattern.
See Context & Learnings for rule-writing and verification guidance.

​
Repository context

Codebase Context controls which repository Markdown files inform the review. Linked codebases add related repository context. File exclusions remove matched paths from review coverage. Use the narrowest possible scope for every context source and exclusion.

​
Roll out a setting safely

1

Change one control

Record the repository, previous value, new value, owner, and expected effect.
2

Run a purpose-built test pull request

Include the condition the setting should change—for example, a new commit, an excluded file, or more findings than the comment cap.
3

Compare the output

Confirm the trigger, priority, placement, and context changed exactly as intended.
4

Keep or roll back

Expand only after the pilot is useful. Otherwise restore the recorded previous value.

​
Verification ideas

  • Push a new commit to test automatic re-review.
  • Include more findings than the limit to test comment capping.
  • Include an excluded and included path.
  • Add a valid ticket key to test ticket linking.
  • Reply to a thread to test auto-resolution.
  • Ask @entelligence config to confirm the repository settings visible to the bot.

​
Next step

Configure guidelines and context or troubleshoot review behavior.