Feedback on Copilot Coding Agent branch management #168610
Replies: 1 comment
-
💬 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
Copilot Coding Agent
Body
After using the GitHub Copilot coding agent to successfully close 30 issues, I noticed that the branches created by Copilot (e.g., those starting with
copilot/fix-****
) are not deleted after the related pull requests are closed. Now my repository has over 100 old Copilot branches cluttering the branch list.Thanks to Copilot, I was able to generate the following commands to clean them up both locally and remotely:
Remote:
Local:
GitHub Copilot coding agent should automatically delete its branches when the related PR has been closed to keep repositories clean and manageable.
Beta Was this translation helpful? Give feedback.
All reactions