PR #8373
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8372
facts: approved=True conflicts=no days_since_last_activity=0
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85_wSps -> reviewer (The author has already replied with a detailed rationale for the behavior changes, so the thread is back in reviewer court for review/acknowledgment.)
route: maintainer
PR #8364
facts: approved=False conflicts=no days_since_last_activity=1
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: pr-conversation -> none (The reviewer asked to park the PR, and the author agreed; the thread has no immediate follow-up until the overlapping PR #8346 settles.)
route: approver
PR #8363
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8362
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8361
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86AMNrI -> reviewer (The reviewer asked for an explanation, and the author answered by clarifying the unrelated change was removed; the thread now needs reviewer follow-up/acknowledgment.)
route: approver
PR #8349
facts: approved=False conflicts=no days_since_last_activity=7
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author is asking the profiling maintainers for guidance on spec changes and whether the wire spec should match the trace spec, so the next move is reviewer/maintainer input.)
route: approver
PR #8346
facts: approved=True conflicts=no days_since_last_activity=1
threads: author=2 reviewer=0 external=3 none=3 unclear=0
llm: PRRT_kwDOCkv3g85_EBPg -> external (The author deferred the question until the linked OpenTelemetry spec issue is resolved, so the thread is blocked on an external spec decision.)
llm: PRRT_kwDOCkv3g85_EEnc -> external (The author deferred the change until the linked OpenTelemetry specification issue is resolved, so this thread is blocked on an external dependency.)
llm: PRRT_kwDOCkv3g85_EFiy -> external (The requested extra tests are explicitly deferred until the external specification issue is resolved, so the thread is waiting on work outside this repository.)
llm: PRRT_kwDOCkv3g85_yMUD -> author (The approver requested a code change: stop using exceptions as control flow, return null from sanitizeUnitName, and update the caller to guard on non-null.)
llm: PRRT_kwDOCkv3g85_yVSV -> author (The approver is requesting a code change for consistency (“Probably null”), so the PR author needs to update the implementation.)
llm: PRRT_kwDOCkv3g85_yXP2 -> none (The comment is a non-blocking nit suggesting an optional refactor, and the same approver later approved the PR, so no follow-up is needed for this thread.)
llm: PRRT_kwDOCkv3g85_ydQK -> none (This is a non-blocking nit from the approver (“don’t feel strongly”), and the PR was approved afterward, so no follow-up is needed for this thread.)
llm: PRRT_kwDOCkv3g85_ypRk -> none (The reviewer’s comment is a non-blocking readability suggestion rather than a required change, and the same approver later approved after the thread.)
route: author
PR #8335
facts: approved=False conflicts=no days_since_last_activity=None
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8326
facts: approved=False conflicts=yes days_since_last_activity=0
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author explicitly asked @open-telemetry/java-approvers to take a look, so the next action is on the reviewers/approvers.)
route: approver
PR #8318
facts: approved=False conflicts=no days_since_last_activity=12
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: pr-conversation -> none (The author only shared SIG discussion context and pointed to a separate PR that solved it; there’s no explicit request for action in this thread.)
route: approver
PR #8313
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g858njQs -> none (The author’s comment is explanatory and does not request any follow-up or change; it reads as informational rationale rather than an action item.)
llm: PRRT_kwDOCkv3g858nkV1 -> author (The author left a TODO to revert or make the test change configurable before merging, so the remaining action is on the author.)
route: author
PR #8294
facts: approved=False conflicts=no days_since_last_activity=13
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8270
facts: approved=False conflicts=yes days_since_last_activity=15
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g857PtCt -> none (The reviewer explained the current PR should stay as a follow-up, and the author acknowledged that plan; no further reply or decision is requested in this thread.)
route: approver
PR #8261
facts: approved=True conflicts=no days_since_last_activity=28
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g855XQ2Y -> none (The author asked an exploratory question about using Zulu, and the approver responded "Fine with me," making it non-blocking and leaving no follow-up action for either side.)
llm: PRRT_kwDOCkv3g855rwM4 -> author (A reviewer asked a direct question about the change (“What’s this?”), so the PR author needs to explain or adjust the code.)
route: author
PR #8259
facts: approved=False conflicts=no days_since_last_activity=28
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The approver says this must wait for Nullaway 0.13.2, which is tracked in an external upstream issue.)
route: external
PR #8256
facts: approved=False conflicts=yes days_since_last_activity=30
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked for the benefit, and the author responded with an explanation plus evidence about the terms of use behavior, so the thread is now waiting on reviewer response.)
route: approver
PR #8255
facts: approved=True conflicts=yes days_since_last_activity=8
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g857fR2F -> author (The author said to add a comment “here and elsewhere,” and the thread is still unresolved; the reviewer only pinged afterward, so the next step is for the author to make the requested edit.)
route: author
PR #8240
facts: approved=False conflicts=no days_since_last_activity=14
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer requested benchmark results, and the author replied that they need to investigate why the benchmark metrics are zero and will spend time figuring that out.)
route: author
PR #8232
facts: approved=False conflicts=no days_since_last_activity=15
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The remaining blocker is upstream GraalVM support for Java 26, not a repo-local change, so the PR is waiting on an external dependency.)
route: external
PR #8197
facts: approved=False conflicts=yes days_since_last_activity=21
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The author pointed to the upstream spec discussion issue, and the reviewer said the PR can stay as a reference implementation while that external spec process happens.)
route: external
PR #8164
facts: approved=False conflicts=no days_since_last_activity=55
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> reviewer (An approver is requesting feedback from the Java/configuration approvers on the proposed guardrail change, so the next action is on reviewers rather than the PR author.)
llm: pr-conversation -> reviewer (The author explicitly says they are waiting for approver feedback, so the next move is on a reviewer/maintainer to respond or approve.)
route: approver
PR #8077
facts: approved=True conflicts=no days_since_last_activity=15
threads: author=2 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g85uUzlV -> author (The only comment is from the PR author noting a TODO to update Javadocs before merging, so the author still has the next action.)
llm: PRRT_kwDOCkv3g85uUzwM -> author (The only comment is the author’s own TODO to remove a leftover annotation, so the code change still needs to be made by the PR author.)
llm: PRRT_kwDOCkv3g85ufcGk -> none (The outsider asked a question, and the author answered it with no request for further action or change, so the thread is informational and closed.)
llm: pr-conversation -> none (The author only shared an informational update about opening an alternative PR; no follow-up or decision is requested in this thread.)
route: author
PR #8076
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85-kTBF -> reviewer (The author replied with “added,” indicating they addressed the reviewer’s optimization suggestion; the thread is now back with the reviewer to confirm or continue review.)
llm: pr-conversation -> reviewer (The author’s latest comment asks how to call `setConfig` from an extension and requests guidance on the API shape, so the next action is with a reviewer/maintainer.)
route: approver
PR #7964
facts: approved=False conflicts=yes days_since_last_activity=21
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: pr-conversation -> none (The author made the requested fix and the latest reply from the outsider says it’s a better fix with no further change requested, so this thread doesn’t need follow-up.)
route: approver
PR #7924
facts: approved=True conflicts=no days_since_last_activity=51
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: maintainer
PR #7763
facts: approved=False conflicts=yes days_since_last_activity=189
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked why, and the author replied with an explanation, so the thread is now back in the reviewer’s court for follow-up review or approval.)
route: approver
PR #7741
facts: approved=False conflicts=no days_since_last_activity=34
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (Reviewer suggested implementation paths and the thread is waiting for the PR author to choose and make the build/module change.)
route: author
PR #6791
facts: approved=False conflicts=yes days_since_last_activity=237
threads: author=2 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85aSnGV -> author (A reviewer asked whether the change is based on a specification, so the author needs to जवाब/justify the implementation or update it.)
llm: PRRT_kwDOCkv3g85aSnh9 -> author (The approver asked the PR author to add a test covering the change, so the next action is on the author.)
route: author
Note
Open PRs are grouped by deterministic routing over per-thread LLM classifications. CI, conflicts, and activity age are computed deterministically and are shown as facts, not used as standalone routing reasons.
Waiting on maintainer (approved)
Waiting on approvers
Waiting on authors
Waiting on external
Diagnostics
Generated 2026-05-07 13:43 UTC