[prompt-analysis] Copilot PR Prompt Analysis - 2026-07-26 #48228
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Copilot PR Prompt Pattern Analysis. A newer discussion is available at Discussion #48449. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🤖 Copilot PR Prompt Pattern Analysis - 2026-07-26
Summary
Analysis Period: Last 30 days
Total PRs: 1000 | Merged: 764 (76.4%) | Closed: 230 (23.0%) | Open: 6 (0.6%)
Prompt Categories and Success Rates
Prompt Analysis
✅ Successful Prompt Patterns
Common characteristics in merged PRs:
workflow,run,actions,copilot,modelfix,add,implement,resolve,alignExample Merged PRs
models.providerspricing into AWFapiProxy(including threat-detection runs) #48107: Propagatemodels.providerspricing into AWFapiProxy(including threat-detection) → Mergedmax-patch-sizepre-check with push diff semantics #48106: Align repo-memorymax-patch-sizepre-check with push diff semantics → Merged❌ Unsuccessful Prompt Patterns
Common characteristics in closed PRs:
workflow,copilot,daily,agent,runsExample Closed PRs
engine.auth#48170: Add Gemini Vertex AI auth viaengine.auth→ ClosedKey Insights
[WIP]or with very broad feature additions (e.g., new auth provider integrations) show higher closure rates — Copilot may not have enough context to complete these fully.Recommendations
Based on today's analysis:
[WIP]in PR titles or submitting broad feature additions spanning multiple components — these have the highest closure rate (37% for "other/uncategorized").Historical Trends (Last 7 Days)
Trend: Success rates are stable at 76–77% over the past week with minimal variance. No significant improvement or degradation detected.
References:
All reactions