PRs are stalled on repository-owner test approval rather than contributor changes.

Inspect or approve the gated run, then decide the linked PR and issues with the evidence thread open.

pending: gerrit_reviewowner gatepending checks: gerrit_review12 package receipts

The local packet found no failed-check blocker; the next step is maintainer review, merge, close, rebase request, or takeover.

Review changed files, linked issues, and latest comments, then choose merge, close, rebase request, or maintainer takeover.

no failed-check blockerreviewDecision=mergeStateStatus=UNSTABLEpending=code_review4 package receipts

The failing job names are known, so maintainers can ask for or apply a focused check fix before re-review.

Fix or request fixes for the named static/type checks, rerun, then return to review only after the branch is green.

pending: gerrit_reviewfailed static/type checksfailed checks: mypy-3.14pending owner gate: gerrit_review.3 package receipts

The blocker is merge state, so review should wait until the branch is updated against main.

Rebase or update the branch, rerun checks, then re-enter maintainer review.

merge-state blockedmergeStateStatus=DIRTYbranch=feature/GH-11122/table-withbranch=issue_29433 package receipts

Multiple active or referenced PR attempts are connected, so maintainers should choose the current path before separate reviews diverge.

Review the current PR, older attempts, superseding links, and review guidance together; close, park, or merge in one lineage decision.

pending: gerrit_reviewowner gatefailed static/type checksmerge-state blockedpending checks: gerrit_review9 package receipts

The next work is contributor-owned unless a maintainer chooses to take over or close the stale path.

Keep parked, close with context, or explicitly take over only when the evidence warrants maintainer work.

requested changesreviewDecision=CHANGES_REQUESTEDstale_days=4791 package receipt

Old low-urgency rows can be handled as a policy batch instead of reopened one at a time.

Close with rationale when no live reproducer exists, mark canonical duplicates, or promote still-reproducible failures into a local draft.

issue #12972: stale/low urgencylabels: use case, asynciotitle: Move asyncio out of ext into the library properissue #12710: stale/low urgency25 package receipts

Related reports can share one canonical answer, close path, or implementation direction.

Pick the canonical issue, preserve the strongest reproduction, and close or link duplicates in one pass.

issues #8326 and #10335 share title/component terms: or...1 package receipt

These rows are waiting for reporter information unless existing evidence is enough for maintainer reproduction.

Park or close unless a maintainer can reproduce from the evidence already collected.

issue #10531: waiting on contributorlabels: bug, documentation, awaiting info, orm - annota...title: Issue with relationship typing when using Declar...issue #11136: waiting on contributor3 package receipts

The local evidence is concrete enough to plan a patch or design branch without writing to GitHub.

Draft locally, add focused regression coverage, and only open a GitHub PR if maintainers approve the scope.

patch-plan readyit's #4384issue #13113: needs maintainer decisionlabels: sqlite, use case, dml11 package receipts

The grouped issues share low-risk scope, labels, or documentation/test expectations suitable for contributors.

Publish or keep a local contributor-ready bundle with scope, expected files, tests, and linked issue context.

patch-plan readyThanks for the great explanation mike. I've taken the l...eems like contains_eager() + join() is more appropriate...issue #7604: good volunteer slice12 package receipts