AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with GitHub Copilot Feb 26, 2026
Ask a coding agent to fix an existing PR
A developer asked @copilot to fix an existing PR; it opened a new PR instead of pushing in place, later partly fixed except for fork branches. · Feb 26, 2026
- What They Did
- The developer opened a PR on a repo and saw Copilot's prompt to mention @copilot in a comment to make changes. He mentioned it and asked for a fix to his own PR. He expected a push to that branch. Copilot opened a separate new PR, so he would have had to merge its changes back himself.
- How It Went
- On March 24, 2026 GitHub shipped a changelog entry letting Copilot change any PR. Stephen Toub noted it still fails when the source branch is in a fork, which covers nearly all of dotnet/runtime's human-authored PRs.
- Worth Knowing
- Check whether your PRs come from fork branches. Copilot still can't edit those, and GitHub's announcement was later edited to say fork PRs aren't supported.
Try it yourself with GitHub Copilot
@copilot please fix pull request [PR number] in [owner/repo]: [describe the problem, e.g. the failing lint check and the review comment about the null case]. Push your fix to the existing PR branch if you can, rather than opening a new PR. If you can't push to this branch, because it's a fork for example, tell me why and say what you would change instead. Stop once the fix is pushed or you've explained the blocker.
Do this with a skill.
These AI Services Market playbooks do this exact job.