PR #8422
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8418
facts: approved=False conflicts=no days_since_last_activity=None
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8417
facts: approved=False conflicts=no days_since_last_activity=1
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer pointed out a remaining OSGi issue, and the author replied that it is optional and said they will fix it and check similar cases.)
route: author
PR #8413
facts: approved=True conflicts=no days_since_last_activity=2
threads: author=0 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86C7dSe -> none (The author is only explaining why the test covers the change; there’s no question, request, or required follow-up in the thread.)
llm: PRRT_kwDOCkv3g86Dgb4W -> none (The author’s comment is informational (“FYI”) and does not request a concrete follow-up in this thread.)
route: maintainer
PR #8408
facts: approved=False conflicts=no days_since_last_activity=8
threads: author=3 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86CKKVv -> none (The author only clarifies what should be reviewed and doesn’t ask for a response or change, so no follow-up action is implied in this thread.)
llm: PRRT_kwDOCkv3g86CKMLE -> none (The author explains the flagged comparison is intentional and not a real problem, so there’s no follow-up action requested in the thread.)
llm: PRRT_kwDOCkv3g86CKN7v -> author (The only comment is from the PR author noting they want to investigate changing the Jackson constructor behavior; no reviewer response or request for reviewer action is present.)
llm: PRRT_kwDOCkv3g86CKPJM -> author (The author’s latest comment proposes investigating a rename to `set*`, so the next step is on the author to make or confirm that change.)
llm: PRRT_kwDOCkv3g86CKPwd -> author (The latest comment is from the PR author noting the `toString` needs changes and saying they should look into fixing it, so the next step is on the author to update the implementation.)
route: author
PR #8407
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86CMfQS -> reviewer (The reviewer asked for justification comments, and the author replied that they added them in a commit. The next step is for a reviewer to re-check and resolve the thread.)
llm: PRRT_kwDOCkv3g86CMnfF -> reviewer (The author answered the question about the `Object` change, so the thread is back in the reviewer’s court to accept the explanation or continue reviewing if needed.)
route: approver
PR #8377
facts: approved=False conflicts=yes days_since_last_activity=15
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: PRRT_kwDOCkv3g86Ab-gj -> external (The approver says to wait for the real 7.3.0 release before merging, so the thread is blocked on an external upstream release rather than an in-repo change.)
route: external
PR #8364
facts: approved=False conflicts=no days_since_last_activity=8
threads: author=3 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86BhQsA -> author (The approver requested a code change: add a clarifying comment and then revise the test strategy to avoid the extra allocation unless a collision occurs.)
llm: PRRT_kwDOCkv3g86BhVsZ -> author (The approver flagged a code change request: collisions should also account for normalization of resource, scope, and additionalAttributes, so the author needs to update the implementation.)
llm: pr-conversation -> author (The latest comment is from the author and explicitly says they will rebase and apply the requested changes once the blocking PR settles, so the next action is on the author.)
route: author
PR #8362
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=2 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86C-hHG -> author (The commenter suggested a test refactor (using `Named` arguments) and left the change as an optional improvement, so the next concrete action—if any—is for the PR author to decide whether to apply it.)
llm: PRRT_kwDOCkv3g86C-jIw -> author (A reviewer nitpicks a variable name change (`short` to `short_attr`), so the PR author would need to update the test if they choose to address it.)
route: author
PR #8349
facts: approved=False conflicts=no days_since_last_activity=3
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver
PR #8270
facts: approved=False conflicts=yes days_since_last_activity=31
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g857PtCt -> author (The reviewer pushed back on this PR’s approach and the author replied by acknowledging it would be a follow-up/recreated effort, so the next step is for the author to act on that feedback.)
route: author
PR #8261
facts: approved=True conflicts=no days_since_last_activity=44
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g855XQ2Y -> none (The author asked an informational question about using Zulu, and the approver replied "Fine with me," so no further action is needed in this thread.)
llm: PRRT_kwDOCkv3g855rwM4 -> author (The approver asked a direct clarification question ('What's this?'), so the author needed to explain or adjust the code; the later approval suggests it was handled, but the follow-up belonged to the author.)
route: author
PR #8256
facts: approved=False conflicts=yes days_since_last_activity=46
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author answered the benefit question and followed up with evidence supporting the change, so the next step is for the reviewer/approver to react or decide whether to proceed.)
route: approver
PR #8240
facts: approved=False conflicts=no days_since_last_activity=30
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer asked for before/after benchmark results, and the author’s last reply says they still need to investigate why the relevant benchmark metrics are zero. The thread is waiting on the author to continue with that work.)
route: author
PR #8232
facts: approved=False conflicts=no days_since_last_activity=31
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The blocker is upstream GraalVM support for Java 26, not a repo-local change, so progress depends on an external artifact becoming available.)
route: external
PR #8197
facts: approved=False conflicts=yes days_since_last_activity=37
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The reviewer asked to defer until the spec discussion, and the author’s last reply just links the external OpenTelemetry spec issue. The next step is outside this repository.)
route: external
PR #8164
facts: approved=False conflicts=no days_since_last_activity=3
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> author (A reviewer suggested changing the config key and another approver agreed, so the suggested guardrail change still needs the PR author to implement or respond.)
route: author
PR #8076
facts: approved=False conflicts=yes days_since_last_activity=16
threads: author=0 reviewer=1 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g85-kTBF -> none (The reviewer only suggested a possible later optimization/TODO, and the author replied "added," so the thread reads as informational rather than requiring further action.)
llm: pr-conversation -> reviewer (The latest comment is from the author asking how an extension can call `setConfig`, so the thread is waiting on reviewer/maintainer guidance rather than a new code change.)
route: approver
PR #7763
facts: approved=False conflicts=yes days_since_last_activity=205
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked for justification (“Why?”) and the author replied with an explanation, so the thread is back in the reviewer’s court to decide whether the answer is sufficient.)
route: approver
PR #7741
facts: approved=False conflicts=no days_since_last_activity=50
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer gave implementation options and the latest outsider comment was just a suggestion; the next concrete step is for the PR author to choose an approach and update the code.)
route: author
PR #6791
facts: approved=False conflicts=yes days_since_last_activity=13
threads: author=2 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g85aSnGV -> author (The approver is asking the author to justify the change against a specification, so the next step is for the PR author to პასუხ/point to the source.)
llm: PRRT_kwDOCkv3g85aSnh9 -> author (An approver asked the PR author to add a test covering this code path, so the next action is on the author.)
llm: pr-conversation -> none (The only comment is an informational FYI linking another PR addressing the same issue, with no requested change or response needed in this thread.)
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-23 09:39 UTC