Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat(review): file triage follow-ups — ranking call, categories and consumers

Aperta
  • Qualcosa non va?
#1,271 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
ai, backend, testing

Direzione di ricerca

Read the existing deterministic triage from #666, then inspect ReviewDimensionRouter, ReviewDiffFormatter.isTestFile, and RepoSettingsResolver for the existing file classifications and settings pattern. Map the proposed ranking call, shared taxonomy, consumers, and repository tier globs to those entry points and their tests. Done means each acceptance criterion has a test, triage-off behavior is unchanged, and ranking failures or spend limits preserve deterministic ordering.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement java
Problem Statement

#666 added deterministic file triage: with REVIEW_TRIAGE_ENABLED on, batches are packed by tier (build manifest, high-risk path, normal, low-risk path) from the model-routing globs. That first step leaves out four parts of the original proposal.

Proposed Solution
  1. Optional ranking call. A small call on the concise binding ranks the files the globs leave in the normal tier. It reads file paths and hunk headers, not diffs. It is ledger-gated, counted against REVIEW_MAX_AI_CALLS, off by default, and fails open to the deterministic order.
  2. Category taxonomy. Source, test, config, IaC, docs, generated and lockfile categories from path and content signals, plus risk signals such as public API surface. Several of these already exist in separate places (ReviewDimensionRouter's file kinds, the default ignore list, ReviewDiffFormatter.isTestFile). The taxonomy would share them.
  3. Consumers.
    • Pack config and IaC files together, so per-batch dimension routing (#665) carries IaC rules only where they apply.
    • Give docs and generated files a lighter prompt.
  4. Per-repository tier globs in .github/thrillhousebot.yml, like review.ignored-files (a RepoSettingsResolver change).
Acceptance criteria
  • The ranking call is optional and fails open: an error, a refusal or the spend ceiling leaves the deterministic order.
  • Each consumer has a test showing its effect, and no change when triage is off.
Note on the spend ceiling

Batches run in parallel, so they all start before the ceiling can refuse one. The packing order decides what the call cap leaves out, not which batch the ceiling skips. Ordering against the ceiling would need the first batch run on its own first.

Follows #666.

Lingua principale
Java
Stelle
35
Fork
7
Merge medio
7h 7m
PR unite (30g)
225

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di devops-thiago/ThrillhouseBot

Tutte le issue di devops-thiago/ThrillhouseBot

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.