Programmatically and continuously trigger Copilot to generate PR text (Continuous AI)

[MariusStorhaug]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot in GitHub

Body

When opening a Pull Request (PR), whether programmatically or through the UI, I’d love the ability to add a “placeholder” to the PR template that allows Copilot to generate the PR content. Ideally, I’d like to use this both while initially creating the PR and when updating it later. To make this possible, it would be helpful if the placeholders were "hidden" or comment-based, so they’re easy to identify and automate against.

The current solution works well and inserts a [Copilot is generating a summary...] in the summary section, but it’s not easy to keep updating the PR description automatically after the initial creation.

It would also be great if Copilot (Codex) could continue updating the PR and leverage the PR template for these updates.

A suggested way to implement this in the PR template might look like:

<!-- COPILOT SUMMARY START -->

<!-- COPILOT SUMMARY END -->

---

Summary of asks:

1. Placeholder support in PR templates:
   Allow the use of hidden/comment-based placeholders in PR templates that Copilot can recognize and use to generate PR content.

2. Ongoing Copilot updates:
   Enable Copilot to continue updating the PR description after creation, not just during the initial PR creation.

3. Template-based generation:
   Ensure Copilot uses the PR template (including custom placeholders) when generating and updating content.

4. Support both UI and programmatic workflows:
   Make sure this feature works whether PRs are created/updated via the GitHub UI or automation/scripts.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐