[Bug]: Pull Requests list is empty on GitHub Enterprise Server (GHES) because GraphQL documents include github.com-only stack/stackEntry fields #20436

Activity

1. Ossiam

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Oct 17, 2026
2. juliusmarminge commented on Oct 17, 2026

   

   juliusmarminge

   on Oct 17, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   Confirmed on main: this is a regression from #19224, which moved the PR queries into fixed .graphql documents. Before that, stack membership was a separate query that only ran on github.com.

   The code is meant to handle Enterprise Server here: $stacks is set to false off github.com, and the documents say "Enterprise Server has no pull request stacks". But @include(if: $stacks) only skips a field when the query runs. GHES checks the whole document against its schema first, so stack/stackEntry fail that check in:

   • pullRequestListings.graphql: the PullRequestRow fragment (L13-20), used by both search and list
   • pullRequestBatches.graphql: PullRequestSummary (L47-54)

   PullRequestStackMembership (L68-79) has the same fields, so it should also only be sent to github.com.

   Some of this overlaps with #17232 (other fields GHES doesn't support, in PR details), and #14458 covers the REST stacks endpoint. But this is a separate regression with a separate fix: stack fields need to stay out of Enterprise requests entirely. So we're keeping it open as its own bug and linking it to #17232. Thanks for tracking down the exact cause.
3. juliusmarminge

   added

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   needs more infoInitial triage showed no bug. Awaiting more infoInitial triage showed no bug. Awaiting more info

   and removed

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   needs more infoInitial triage showed no bug. Awaiting more infoInitial triage showed no bug. Awaiting more info

   on Oct 17, 2026
4. Ossiam commented on Oct 22, 2026

   

   Ossiam

   on Oct 22, 2026

   Author

   More actions

   I can't give outside access to our GHES instance (it's a corporate server), but I verified the fix against it directly.

   Environment: GitHub Enterprise Server 3.21.4, authenticated with gh auth login --hostname <ghes-host>.

   I took the per-operation GraphQL documents (each operation plus only the fragments it uses, as the generated client sends them) from current main and from #20531 at 4bdb33d3e1. I sent them to a real repository with gh api graphql --hostname <ghes-host>:

   Operation	main	#20531
   PullRequestSearch (stats false and true)	❌ Field 'stack' doesn't exist on type 'PullRequest', Field 'stackEntry' doesn't exist…, no data	✅ rows returned, no errors
   PullRequestList	❌ same errors, no data	✅ rows returned, no errors
   PullRequestSummary	❌ same errors, no data	✅ PR loaded, no errors
   PullRequestStackMembership	❌	❌ (expected: github.com only)

   This confirms the cause on a live GHES: @include(if: false) doesn't help because the server validates the whole document first. With #20531, the Enterprise list, repository-list fallback and summary queries all validate and return data. PullRequestStackMembership and the *WithStacks variants still fail on GHES, so they must stay github.com-only, as the PR intends.

   If it would help, I can also test a build of #20531 in the desktop app. I'm happy to run any other queries or builds you'd like checked.
5. EmanuelMedinaEme commented on Oct 28, 2026

   

   EmanuelMedinaEme

   on Oct 28, 2026

   More actions

   Another confirmation, on a stable desktop build this time.

   Environment

   • T3 Code (Beta) desktop, 0.1.3 stable, Windows 11 (x64), local server
   • GitHub Enterprise Server 3.21.7, gh 2.95.0 logged in with gh auth login --hostname <ghes-host> (scopes: repo, read:org)

   What happens
   The Pull Requests list is empty for repositories on the GHES host. listPullRequestsByHead succeeds, but getPullRequestSummary fails every time:

   GitHubPullRequestReadError: GitHub returned an unreadable getPullRequestSummary response.
     [cause]: GraphQLClientError: PullRequestSummary: ResponseError:
       Field 'stack' doesn't exist on type 'PullRequest';
       Field 'stackEntry' doesn't exist on type 'PullRequest';
       Variable $_0_stacks is declared by PullRequestSummary but not used
   

   This matches the diagnosis above. #20531 would fix it for us too.

   Something that may trip up other GHES users: at first this bug was hidden behind a TLS failure. Our GHES certificate is issued by a private corporate root CA. gh trusts it through the Windows certificate store, but the T3 server (Node) doesn't use that store. Every request failed with self signed certificate in certificate chain, and the error T3 showed was just Could not reach GitHub at <ghes-host>. Pointing NODE_EXTRA_CA_CERTS at an exported copy of the root CA and fully restarting the app fixed the TLS part. Only then did the stack/stackEntry error above appear. If the error said the certificate wasn't trusted, instead of "Could not reach GitHub", this would have taken much less time to figure out. (Probably related: #16703.)

   Diagnosed via t3 triage with Claude Code (Claude Opus 5.5).