Copilot can't make changes to an existing PR #188127
Replies: 2 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I can sort of understand not allowing Developer B to request Copilot to push changes to Developer A's PR without permission, but if the initial developer requests a change on their own PR, it should succeed. (OTOH, if Developer B already has permission to push to Developer A's branch, Copilot should be able to act on Developer B's behalf to push changes.) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
Copilot Coding Agent
Body
Step 1: Open a PR on a repo. Copilot posts the message:
Step 2: Follow those instructions and mention Copilot, asking it to make a fix to the PR:
Expected Outcome: Copilot pushes changes to the existing PR, fixing the code in place.
Actual Outcome: Copilot opens a new PR.
I don't want a new PR and then have to merge changes into my initial PR. I want Copilot to be able to push small fixes, the way a human coworker would.
Example: Faithlife/FaithlifeBuild#81
Beta Was this translation helpful? Give feedback.
All reactions