Flight Log / repository
dotnet/aspire — agent flight log
169 pull requests opened by AI coding agents in dotnet/aspire (★ 6,406, C#): GitHub Copilot (GitHub) 169 (70% merged).
Flights by agent
| Agent | Flights | Merge rate | Median to merge | Burn rate |
|---|---|---|---|---|
| GitHub Copilot (GitHub) | 169 | 70% | 13.2 h | 19% |
By month
| Month | Flights | Merged | Burns |
|---|---|---|---|
| 2025-05 | 39 | 23 | 7 |
| 2025-06 | 76 | 47 | 19 |
| 2025-07 | 54 | 35 | 3 |
Where agents burned here
- GitHub Copilot (GitHub) burn #10498
@copilot https://github.com/dotnet/aspire/blob/ef7b5b268776076185357a654a503211abff0195/src/Aspire.Hosting/Publishing/PublishingActivityReporter.cs#L268 Any unsupported interactions should fail instead instead of return. See https://github.com/dotnet/aspire/blob/ef7b5b268776076185357a654a503211abff0195/src/Aspire.Hosting/Publishing/PublishingActivityReporter.cs#L275-L284 for an example on how failures should look.
- GitHub Copilot (GitHub) burn #10258
@copilot there are now merge conflicts rebase on main and factor in the new changes to this rename.
- GitHub Copilot (GitHub) burn #10205
Doesn’t it normally link to the issue it was assigned? Maybe Im missing it
- GitHub Copilot (GitHub) burn #10027
@copilot Let's update this implementation further. - Add a property to `PublishingStep` so that it can maintain a list of `PublishingTasks` that are parented to
- GitHub Copilot (GitHub) burn #10001
Closing in favor of a refined model.
- GitHub Copilot (GitHub) burn #9884
Been thinking about this over the weekend. For the `aspire run` scenario we probably don't need this because the UX is going to stream back
Last 50 flights
No rider has claimed a flight in this repository yet. Flew one of these? Open your flight page and claim it.
Read next
Data from public GitHub activity; this page is not affiliated with GitHub or the repository. Repository owner? Request exclusion — handled within 48 hours.