chore: add merge-queue review digest for the open PR backlog - #599
Open
essentialbit wants to merge 2 commits into
Open
chore: add merge-queue review digest for the open PR backlog#599essentialbit wants to merge 2 commits into
essentialbit wants to merge 2 commits into
Conversation
pr_merge_planner.py already confirms the 33-PR backlog is mergeable/ conflict-free; the real bottleneck (fredai.md open item 2) is a human working through it one PR at a time with no sense of review order. Buckets by conventional-commit kind + diff size into a fast-to-clear queue, with a separate needs_attention bucket for large diffs or a title-level risk-keyword hit (word-boundary matched, title only -- verified a full-body substring scan false-positived on 10/33 PRs before shipping, e.g. "author"/"tokenizer"/"Claude Code session" matching auth/token/session). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scripts/merge_queue_digest.py(read-only, no git/GitHub writes) buckets the open, non-draft PR backlog into a review order: fast chore/fix merges first, small features next, then aneeds_attentionbucket for large diffs (250+ lines) or a title-level risk-keyword hit, with everything else inother.pr_merge_planner.pyalready shows the 33-PR backlog is mergeable and conflict-free, but there's been no merge tomainsince PR AI Universe tab: live prices, sentiment badges, nav-highlight fix, sector scope #549 (2026-08-03) because a live user session has to work through the whole backlog with no sense of which PRs are quick reviews vs which need real attention.risk_rules.classify_risk()'s full-body substring match — verified before shipping that a full-body scan false-positived on 10/33 real PRs in this backlog (e.g. "auth" matching "author", "token" matching "tokenizer", "session" matching "Claude Code session"). Title-only + word-boundary dropped that to 1/33 on the same data.touches_high_risk_fileper PR (main.py/memory_store.py/config.py/crypto_utils.py/CI workflows) as an informational flag, not a bucket driver — folding it into risk scoring would swamp every bucket since nearly everyfeat:PR wires a new route intomain.py.Test plan
PYTHONPATH=. venv/bin/python3 scripts/merge_queue_digest.pyruns clean against the live 33-PR backlog, produces valid JSON with sane bucket counts (17/4/2/10)venv/bin/python3 -c "from main import *"still imports cleanly🤖 Generated with Claude Code