Community PRs Awaiting Review — dotnet/msbuild

Updated ~daily, last at 2026-03-24 11:47 PDT · 0 PRs · dotnet/msbuild

Community-contributed PRs whose next step is a maintainer review. These authors may need extra shepherding and their PRs may not align with current investment priorities.

How are the scores calculated?

Each PR has three scores on a 0–10 scale:

Ready — how close to merging?

PointsSignal
3.0No merge conflicts
2.5CI passing 1
2.5Has approval 1
2.5Feedback addressed 1
2.5Discussion healthy 1
2.0–3.0Small, easy to review (2.0) / trivial ≤2 files, ≤20 lines (3.0) 1
1.5Has maintainer review 1
1.0Recently active 1
0.5–1.0Team or known author (1.0) / community (0.5) 1
0.7Recently updated 1
0.5Well labeled 1
0.3Good review momentum 1

Need — benefits from maintainer attention?

PointsSignal
1.5No approval yet
1.5CI blocking merge (otherwise merge-ready)
1.0Community author
1.0Reviewed, not approved
1.0Has unresolved feedback
1.0High interest
0.5Large change (>200 lines)
0.5Trivial change (≤2 files, ≤20 lines, no unresolved threads)
0.5Old but active (>30d)
−1.5Author silent >14d (ball in their court)
−0.5Author slow 7–14d (ball in their court)

Action — best use of your time?

(ready + 1) × (need + 1)
normalized to 0–10

PRs that are both high-need and near-ready rank highest.

🎯 = action ≥ 5
⚡ = action 4–5

1 Weight from 980-PR statistical analysis. Click any column header to re-sort. Click [?] on any score to see the breakdown.

Showing PRs for ✕ Clear
No PRs currently match this filter.