Real example · Build apps (vibe coding)
Assign bug fixes and cleanups to GitHub Copilot coding agent
What they did
Microsoft's .NET team let maintainers assign work to Copilot coding agent in the dotnet/runtime repo for ten months, then published the numbers.
How it went
Of 878 agent pull requests, 535 were merged (67.9% of those decided, versus 87.1% for Microsoft staff PRs) and 3 were later reverted. Cleanup and removal work did best (84.7%); performance work did worst (54.5%). A shared instructions file lifted success from 38.1% to 69%.
Worth knowing
Self-reported by the team that ships the product. Every PR was requested by a maintainer, 52% of merged ones needed human commits, and the author says review capacity became the bottleneck.
Try it yourself with GitHub Copilot
Replace anything in [brackets] with your details.
Issue for the coding agent: [clear description of the bug with steps to reproduce]. Expected result: [what should happen]. Add a test that fails before your fix and passes after. Follow the conventions in [instructions file, e.g. AGENTS.md]. Keep the change small and explain it in the PR description. Read the original
Ten Months with Copilot Coding Agent in dotnet/runtime (.NET Blog) ↗
devblogs.microsoft.com · · Company blog
Attributed to the source linked below; not our own test.
Share Share on X Share on WhatsApp


