Overrides
Hosted review settings are project defaults. A few of them can be overridden per repository or per GitHub author. Owners and admins save changes. Members can view them. Nothing on this page selects the model provider or API key. Those stay with a platform administrator.
Changes apply to new hosted reviews. Comments already on GitHub stay as posted. Withheld findings already saved on a review are not reposted or removed by a later settings change.
These pages appear in the sidebar only when hosted inference is enabled: Repos, PR comment voice, Review tracks, Deprecations, Stampy Stamp, and Service maps.
Project and repository
| Setting | Page | Project | Repository | Author |
|---|---|---|---|---|
| Which repositories are reviewed | Repos | Installation default for new repositories | On or off | — |
| Posting threshold | Repos | Default, initially All feedback | Inherit, or only blockers, blockers and recommended fixes, or all feedback | — |
| Summary comment | Repos | Default on | Inherit, on, or off | — |
| Comment voice | PR comment voice | Tone, length, politeness, formality | — | — |
| Review tracks | Review tracks | Standard and adversarial, standard only, or adversarial only | — | — |
| Deprecation warnings | Deprecations | Impending, all, or none | Snooze or ignore one warning | — |
| Approval and merge | Stampy Stamp | Defaults, initially off | Inherit or override, on enabled repositories | Project rules, then repository rules |
There is no per-repository voice, review track, or deprecation mode. Deprecation exceptions are per warning on one repository, not a second mode.
Stampy author rules resolve in order: repository author rule, project author rule, repository default, project default. Unmatched authors use the defaults. Use default on an author field keeps the next level.
PR comment voice
PR comment voice sets how findings are worded. The finding and its confidence stay the same. Defaults are Direct, Terse, Medium politeness, and High formality. The examples on the page are previews, not live comments. Save voice is required; an unsaved preview is not used.
| Control | Values |
|---|---|
| Tone | Direct — concise and precise. Neutral — professional. Coaching — warm and collegial. |
| Length | Terse — essentials only. Standard — enough context to act. Explanatory — reasoning and impact. |
| Politeness | High — considerate. Medium — straightforward. Low — blunt, never personal. Very low — sharp on the pull request, never the author. |
| Formality | High — polished. Medium — conversational. Low — raw, and can include occasional mild swearing. |
Posted comments also carry the action label for their level: Don’t merge until this is fixed, Should fix before merging, or If you have the time. Voice does not choose that level. The posting threshold does. See Repos.
Review tracks
Review tracks chooses which passes run on a new hosted pull request. The default is Standard and adversarial.
- Standard and adversarial — merge readiness, then specialists for risk domains the changed code supports.
- Standard only — the general code review, without those specialists.
- Adversarial only — applicable specialists. A pull request with no supported risk domain is reported as incomplete coverage, not as a clean review.
The worker reads the saved value when it claims the job. Existing GitHub comments stay as posted.
Deprecations
Deprecation reviews chooses which deprecation findings are posted. The default is Impending.
- Impending — only warnings with evidence of an approaching removal or upgrade.
- All — every identified deprecation warning.
- None — hide deprecation warnings. Current breakages can still be reviewed as defects.
Recent deprecation warnings lists warnings seen in hosted reviews. Owners and admins can Snooze 30 days, Snooze 90 days, Ignore, or Reset a warning for its repository. Snooze and ignore apply to that warning, not to every deprecation in the repository. The list is empty until a hosted review has seen one.
Service maps
Service maps is experimental and read-only. There is no per-repository switch. Enabling a repository for hosted reviews is what causes a map to be built. The review Impact section uses it as evidence of a possible match. It does not override tracks, voice, or Stampy. See Intent and provenance.
What is not an override
- Model provider, model name, and API key. Platform admin only. They are not on these pages and are not returned to the browser.
- Issue tracker credentials and repository filters. Those live under Issue sources, and they can be edited before hosted reviews are enabled.
- Review feedback status (Active, Disabled, Overturned). That is per feedback event, not a repository default. See Review feedback.
- Private adversaries and CI OIDC. Those configure the CLI path, not the hosted
review/coderun.