Copilot's PR "Suggested changeset" not accessible via any API

[HaleTom]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

This issue is about Copilot's "Suggested changeset" feature — the multi-file grouped suggestion that Copilot generates during its code review.

This data appears in the GitHub WebUI (labeled "Suggested changeset 1", "Suggested changeset 2") but is not exposed via any API.

---

Proof: No API Returns the Changeset

Fetched every available data source for PR #29208 review #4356610345 (a Copilot review with suggested changesets):

Source	Data Available	Suggested Changeset?
WebUI	✅ Shows changeset label + grouped diffs	✅ Yes
REST GET /pulls/{pr}/comments	26 fields per comment	❌ No
REST GET /pulls/{pr}/reviews/{id}	body, user, state, submitted_at	❌ No
GraphQL reviewThreads	comments, diffHunk, replyTo	❌ No
GraphQL __type(name: "SuggestedChangeset")	—	❌ Type doesn't exist
gh api repos/.../commits/{sha} → files[].patch	committed diff only	❌ No
gh pr view --json comments,reviews,files	comments, reviews, files	❌ No
gh pr diff	raw committed diff	❌ No
Page HTML (34KB fetched)	nav, PR metadata, comment text	❌ No
REST GET /pulls/{pr}/files	file patches	❌ No

Specific example: Copilot review comment r3298114511 shows a "Suggested changeset" in the WebUI proposing:

expect((config as Record<string, unknown>).invalid_field).toBeUndefined()
expect("invalid_field" in (config as Record<string, unknown>)).toBe(false)

This code does not exist in any commit, any API response, or any comment body. Searching 117KB of API data across 9 endpoints for Record<string, unknown> or toBeUndefined returns zero matches. The actual committed code is the weaker expect("invalid_field" in config).toBe(false) — the changeset's stronger suggestion was never persisted anywhere accessible outside the browser.

Proof: Changeset Is JS-Injected, Not in Static HTML

I fetched the full page HTML of the review page (34KB). It contains comment bodies and review metadata, but zero matches for "Suggested changeset" or "changeset":

$ grep -c "Suggested changeset" page.html
0
$ grep -c "changeset" page.html
0

The "Suggested changeset" label and its grouped diffs are rendered entirely by client-side JavaScript after page load. They are not present in the initial HTML payload, confirming they are not server-rendered content — they are dynamically injected by Copilot's frontend code.

Reproduction

1. Open a PR reviewed by Copilot that includes a "Suggested changeset" section in the WebUI (e.g., the one above)
2. Fetch the same data via any API combination (REST, GraphQL, gh CLI)
3. The changeset data is absent — only individual comments + diff_hunk fields are returned
4. Fetch the page HTML with curl or wget — "Suggested changeset" text is absent from static HTML too

Request

Expose Copilot's "Suggested changeset" data via the API — either as a new field on PullRequestReviewComment or as a new endpoint on the review itself. The minimal viable output would be the suggested file diffs that Copilot generates as part of its changeset, allowing CLI tools to display and act on them without resorting to browser-only access.

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

[HaleTom]

I previously incorrectly raised this issue at: cli/cli#13517