Unable to generate PR summary

[gimlichael]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I am unable to use on my favorite features at GitHub.com; PR summary using GitHub Copilot.

Anything changed?

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

[sharyaropensource]

A couple of things worth checking, since "Something went wrong. Please try again." on its own doesn't tell you much.

First, and most likely: PR summary generation is explicitly documented as not available on GitHub Copilot Free, it requires a paid Copilot seat (Pro, Pro+, Business, or Enterprise). If your account or org is on the Free tier, clicking the summary option can fail with a generic error like this instead of a clear "not available on your plan" message. Worth checking your Copilot plan under Settings, or your org's Copilot settings if this is a repo under an organization.

Second, if you do have a paid seat: GitHub declared and resolved an incident the day before your post, "Disruption with Copilot for access to some models," investigated and mitigated on August 10, 2026. The timing is close enough that it's worth a quick retry now in case you were hitting trailing effects, though since it was marked fully resolved before your report, this is a secondary possibility rather than the likely cause.

If you've confirmed you have a paid Copilot seat and a fresh retry still fails the same way, it'd help to add:

• Whether this is a personal repo or one under an organization (org-level Copilot policies can also block the summary feature even with an individual paid seat)
• Whether the error happens on every PR or just specific ones (e.g. very large diffs sometimes fail where small ones succeed)
• The exact time (with timezone) you hit the error, so it's easier to cross-reference against status history

Between the plan check and those details, that should narrow it down.

[gimlichael]

I have Pro+ (legacy) .. but I also experience this at work .. Business. So o see it as temporary regression from the Copilot service.

[sharyaropensource]

That rules out the plan-tier explanation, good to know, and it actually points pretty clearly at what you suspected.

Seeing this on both a personal Pro+ account and a separate work Business org is a useful signal on its own: those are two independent billing/plan tiers, so if it were account- or plan-specific the failure pattern wouldn't line up across both. That points to something above the account layer, i.e. the shared service itself, which lines up with your "temporary regression" read.

There's also a matching data point: GitHub declared a service degradation the same day as your original post, on August 11, 2026 between 14:00-16:00 UTC, the GraphQL API service saw elevated timeouts (peaking around 0.14% of requests) due to resource contention at one site, mitigated by adding capacity. PR summary generation runs through that API, so this is a plausible match for what you hit, and the timing (Aug 11) lines up with your report.

That incident was marked mitigated same day, so if you're still seeing this now, it's likely either a separate, currently-undeclared issue or a longer tail than the status page reflects. Worth checking https://www.githubstatus.com directly for anything currently listed under Copilot or the API component. If nothing's showing there and it's still failing for you, that's worth flagging to GitHub Support directly with both the personal and work occurrences noted, since cross-account reproduction like this is exactly the kind of detail that helps them distinguish a real regression from an isolated account issue.