GitHub Copilot Pull Request Title Generation Returning 400 – Unknown Copilot-Integration-Id

[Asin-Junior-Honore]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hello GitHub Support,

I’m experiencing a persistent issue with GitHub Copilot on GitHub.com that has been occurring for over a week.

When I use the GitHub UI feature with the tooltip:

“Generate pull request title with Copilot”

the request consistently fails with a 400 Bad Request.

I inspected the browser Network tab and the request is being sent to:

https://api.individual.githubcopilot.com/agents/github-pull-request-title-generation

The response indicates:

“Bad Request: unknown Copilot-Integration-Id”

The request is being sent with:

copilot-integration-id: pull-title-gen

I’ve reproduced this multiple times over the past week, so it does not appear to be an intermittent failure.

The request is initiated directly by GitHub.com, and I have not modified the request or integration ID manually. The failure occurs when using the normal GitHub UI action for generating a pull request title.

I can provide the following if useful:

• Full redacted Network request/response details
• Browser console logs
• Screenshot/video of the issue
• Browser and OS information
• Timestamp of recent failed requests

I have intentionally redacted the authorization/session credentials from the information above.

Could you please investigate.

Thanks,
Asin Honore

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