Hi @naorpeled,
I've been onboarding pr-agent across a few repos and ended up doing a full pass over the open PRs. There are a lot of them, and from experience a single maintainer carrying that kind of volume gets noisy fast, so I thought I'd offer a hand rather than add to the pile.
Below is a deliberately conservative first cut: only the extra-small and small PRs, split into "looks safe to close" and "small and basically ready". Everything here is a suggestion, your call entirely.
(I've obviously left my own open PRs out of all of this, triaging those would just be me reviewing my own work :D, so the list below is everyone else's.)
Candidates to close (stale or already steered elsewhere)
Closing these, or nudging the authors first, drops the count with effectively no risk.
Quick wins (small, low-risk, near-ready)
Just needs a review:
One small fix from ready:
Correct micro-fixes needing a test or rebase:
If this is useful, I'm glad to keep going. I've triaged the whole backlog (the larger features, the two duplicate MCP PRs, a couple of security ones) and can write that up too, or help review and close in whatever order is most useful. Only if it's welcome, I don't want to add noise.
I hope this helps, and do let me know if it needs any changes.
Hi @naorpeled,
I've been onboarding pr-agent across a few repos and ended up doing a full pass over the open PRs. There are a lot of them, and from experience a single maintainer carrying that kind of volume gets noisy fast, so I thought I'd offer a hand rather than add to the pile.
Below is a deliberately conservative first cut: only the extra-small and small PRs, split into "looks safe to close" and "small and basically ready". Everything here is a suggestion, your call entirely.
(I've obviously left my own open PRs out of all of this, triaging those would just be me reviewing my own work :D, so the list below is everyone else's.)
Candidates to close (stale or already steered elsewhere)
Closing these, or nudging the authors first, drops the count with effectively no risk.
Quick wins (small, low-risk, near-ready)
Just needs a review:
openai/andazure/prefixes (well tested, green).One small fix from ready:
target_file, and sanitise one log line.isinstanceguard./improve, plus an edge-case test.Correct micro-fixes needing a test or rebase:
If this is useful, I'm glad to keep going. I've triaged the whole backlog (the larger features, the two duplicate MCP PRs, a couple of security ones) and can write that up too, or help review and close in whatever order is most useful. Only if it's welcome, I don't want to add noise.
I hope this helps, and do let me know if it needs any changes.