[GitHub] Generate GraphQL types from a checked-in schema

[TyceHerrman]

Description

This PR makes GraphQL type generation for the GitHub extension deterministic, credential-free, and offline during normal development.

What changed

• Check in GitHub's public GraphQL schema at schema/github.graphql, sourced from the official GitHub Docs repository.
• Point both GraphQL Code Generator and GraphQL Config at the checked-in schema.
• Add npm run update-schema as an explicit, unauthenticated maintenance command that downloads the public schema and rejects it unless the GitHub Issue Types fields used by this extension are present.
• Remove the development-only token setup, .env.example, and dotenv dependency.
• Generate full schema types in src/generated/schema.ts, then generate operation types and the GraphQL Request SDK in src/generated/graphql.ts.
• Re-export schema.ts from graphql.ts so existing imports such as Issue, PullRequest, and Discussion continue to work without handwritten application changes.
• Update the extension's contribution instructions to document the offline generation and explicit refresh workflows.

Normal npm run generate now requires no GitHub token, .env file, Keychain access, gh subprocess, temporary schema file, or network connection. Every contributor and CI job generates from the schema version recorded in the repository.

The tradeoff is that the checked-in schema can briefly trail GitHub's live API. A contributor must run npm run update-schema before using a newly released GraphQL field.

Why the Octokit schema package is not used

I evaluated @octokit/graphql-schema@15.26.1, but its packaged schema is not currently usable for this extension and seems to not be maintained:

• EnterpriseOwnerInfo.repositoryDeployKeySetting is declared twice, so buildSchema rejects the IDL.
• The packaged schema is missing the GitHub Issue Types fields and types already used here.

Related upstream reports and work:

• octokit/graphql-schema#1030
• octokit/graphql-schema#806
• octokit/graphql-schema#1007

Using GitHub's official Docs schema avoids those package-specific blockers while retaining a reviewable, pinned input.

GraphQL Code Generator compatibility

Updating GraphQL Code Generator alone does not remove the compatibility issue. The extension already uses the current Codegen majors (@graphql-codegen/cli 7 and the TypeScript plugins 6/7), and they do not restore the older supported single-file composition of typescript plus typescript-operations.

onlyOperationTypes is not suitable because it omits the complete Issue, PullRequest, and Discussion object types that the extension imports directly. The supported split-output layout preserves those imports without patching Codegen:

1. schema.ts is generated with the typescript plugin.
2. graphql.ts is generated with typescript-operations and typescript-graphql-request, importing schema types from schema.ts.
3. graphql.ts re-exports schema.ts, preserving the existing src/generated/graphql import surface.

Longer term, replacing raw schema-object casts with operation-specific result types would allow full schema generation to be removed, which is the preferred model for newer Codegen versions.

Query contract correction

dataForRepository now explicitly requests owner.__typename because the application already reads that field. GraphQL only returns selected fields, so this is an independent query-contract fix rather than a workaround for the generated-file layout. It requires no handwritten TypeScript change.

Schema refresh automation

The live GitHub GraphQL API remains the authoritative, immediately current schema source, but introspection requires authentication. It should not be part of routine contributor generation.

A repository-owned follow-up GitHub Action could run on a schedule and through workflow_dispatch to:

1. Install the GitHub extension's dependencies.
2. Run npm run update-schema.
3. Run npm run generate.
4. Run the extension's type, lint, and distribution-build checks.
5. Open an update PR when the schema or generated files change.

The current refresh script itself needs no authentication; the Action token would only be needed to create the update branch and PR. If maintainers prefer live API introspection instead of the Docs schema, that repository-owned Action is also the appropriate authenticated boundary.

An example of this scheduled/manual update-PR pattern is andykenward/github-actions-cloudflare-pages#753. The repository-wide workflow is intentionally omitted here because its schedule, permissions, and PR-creation policy should be reviewed separately from this extension-scoped tooling change.

Verification

• npm ci
• npm run update-schema (the schema hash was unchanged after refreshing from GitHub Docs)
• npm run generate with GitHub token variables unset and network proxies pointed at a closed local port
• A second npm run generate with identical hashes for both generated files
• GraphQL Config load: 1,819 schema types and 8 documents
• TypeScript type check
• npm run lint: 0 errors; 7 pre-existing title-case warnings
• npm run build: ready - built extension successfully

Screencast

Not applicable. This changes development tooling, the schema input, and generated types; it does not add or change a user-facing command or UI.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
  • The current branch was rebuilt for Raycast Beta and Search Repositories opened and rendered 50 repository results. A subsequent background refresh returned a transient GitHub GraphQL 502, which the existing error handling surfaced without preventing the rendered results from remaining usable.
• I checked that files in the assets folder are used by the extension itself — not applicable to this PR because no asset files changed.
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool — not applicable to this PR because no README media or metadata assets changed.

[raycastbot]

Thank you for your contribution! 🎉

🔔 @thomaslombart @unnamedd @tonka3000 @khasbilegt @pernielsentikaer @loxygenK @oilbeater @LunaticMuch @aeorge @daquinoaldo @aeither @marcotf @qeude @nesl247 @xilopaint @antonengelhardt @bangerang @wottpal @LitoMore @d-mitrofanov-v @j3lte @jfkisafk @vlasischar @JavaLangRuntimeException @shyakadavis @sushichan044 @luarmr @nicolas-marien @ionTea @ridemountainpig @kud @MartinGonzalez @brandonnly @oscmarb @emergerrrd @ryo246912 @gfazioli @wonbywondev @SandeepBaskaran you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="github-vendored-graphql-schema"
FORK_URL="https://github.com/TyceHerrman/extensions.git"
EXTENSION_NAME="github"
REPO_NAME="extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Greptile Summary

This PR makes GitHub GraphQL generation deterministic and credential-free by replacing live authenticated introspection with a checked-in schema.

• Adds a script and package command for explicitly refreshing the schema from GitHub Docs.
• Splits generated schema types from operation and GraphQL Request SDK types while preserving the existing export surface.
• Updates the repository query contract and contributor documentation for offline generation.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
extensions/github/codegen.ts	Configures separate schema and operation outputs using the checked-in schema and formats both generated files.
extensions/github/scripts/update-graphql-schema.mjs	Adds the explicit unauthenticated schema-refresh workflow and validates required Issue Types fields before replacement.
extensions/github/schema/github.graphql	Checks in the GitHub Docs GraphQL schema used as the deterministic generation input.
extensions/github/src/api/repository.graphql	Selects the repository owner's typename to match the application's existing data access.
extensions/github/package.json	Adds the schema-refresh command, updates Codegen tooling, and removes dotenv.
extensions/github/CONTRIBUTING.md	Documents credential-free offline generation and the explicit online schema-refresh procedure.

_{Reviews (3): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/raycast/github

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@TyceHerrman).

Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.