Repos
Repos (/team/<namespace>/repos) is where owners and admins choose which GitHub repositories receive hosted reviews, and the project defaults for summary comments and which findings are posted.
The page is visible only when hosted inference is enabled for the project. Members can view it. Owners and admins save it.
Enablement
GitHub installation access and Doomer enablement are different:
- The App installation lists repositories Doomer is allowed to see.
- A repository receives hosted reviews only when it is turned on here, or when Automatically turn on new repositories is on for that installation and the repository is added later.
Automatically turn on new repositories does not change repositories you already set. Select all selects every repository in that installation, including ones hidden by the search box.
Use Manage installation to change GitHub access, then Refresh access so the list matches GitHub. Install on a new organization connects another account. If GitHub cannot load an installation, fix access there and refresh. Doomer will not guess the repository list.
Turning a repository off stops new hosted reviews. Saved per-repository summary, posting, and Stampy rules are kept and apply again if you turn it back on. Stampy Stamp only lists repositories that are currently enabled.
Saves recheck that the App can still see the repositories you enable.
Automatic reviews
Automatic reviews is on by default for each repository. To request reviews only when needed, keep the repository enabled, uncheck Automatic reviews in its row, and save repository settings.
Use All on or All off under Automatic reviews for enabled repositories to change every enabled repository in that installation, including repositories hidden by search or filters. Disabled repositories keep their saved choices. Click Save repository settings to apply the changes.
With automatic reviews off, pull request events and periodic reconciliation do not start reviews. An owner, organization member, or collaborator can still comment /doomer run on any open pull request to review its current head. Draft runs are review-only and cannot approve or merge. GitHub Re-run and manual reruns in Doomer also remain available. New commits need another review request. Reviews already queued or running continue.
What should Doomer post on PRs?
The project default is All feedback. Each repository can inherit that default or override it. The threshold is cumulative:
| Setting | Label in the list | What is posted |
|---|---|---|
| Only blockers | Don’t merge until this is fixed | must_fix |
| Blockers and recommended fixes | Should fix before merging, plus blockers | must_fix and should_fix |
| All feedback | If you have the time, plus both stronger levels | must_fix, should_fix, and optional |
Findings are categorized before they are posted. If categorization is unavailable, Doomer falls back to severity: high and critical become blockers, medium becomes a recommended fix, and low or info becomes optional. That fallback is a compatibility rule, not a second review.
Hidden findings are not inline comments, replies, or summary text. They remain on the Doomer review page, marked as not posted because they are below the repository feedback level. They still count when Doomer decides whether an older thread was addressed, so lowering the threshold does not resolve an unfixed issue. A review whose only findings are withheld does not post a clean “no issues” comment.
The default applies to new review attempts, including reruns. It does not delete comments already on GitHub and does not reclassify a finished review.
Summary comments are a separate switch.
Include summary comments by default
The project default is on. Each repository row can stay on the project default or set summary on or off.
The summary is the aggregate assessment. Inline findings and off-diff findings in the review body are still posted when the summary is off, subject to the posting threshold above.
Save the project default with Save default or Save feedback default. Save repository checkboxes, automatic review choices, summary overrides, feedback overrides, and the new-repository switch with Save repository settings. They are separate forms.
Who does not use this page
Self-managed CI ignores these switches and uses the workflow’s own arguments. See CLI and packages. Hosted approval behavior is Stampy Stamp, not a Repos switch.