GeezerVison

Problem

github.paginate handles REST pagination, but scripts that page GraphQL results still have to hand-roll cursor loops. #309 asks to include @octokit/plugin-paginate-graphql by default so github.graphql.paginate works like the REST helper does.

Fix

• Add @octokit/plugin-paginate-graphql ^6.0.0 (peer @octokit/core >=6, compatible with the v7 core already in use) as a dependency.
• src/main.ts adds paginateGraphQL to the plugin list of both the pre-built github client and createConfiguredGetOctokit, so secondary clients from the injected getOctokit also get graphql.paginate / graphql.paginate.iterator.
• README: new "Paginate GraphQL queries" example next to the existing GraphQL example; .licenses/ cache entry for the new package (as done for plugin-request-log); dist/ rebuilt with npm run build.

How tested

• New __test__/main.test.ts loads src/main.ts with inputs set through INPUT_* env vars and stand-ins for the ESM-only @actions/github / Octokit plugin packages (the CommonJS Jest runtime cannot load them, which is why the existing tests avoid them too). It asserts the primary client and a secondary getOctokit client are both built with retry, requestLog, paginateGraphQL.
  • Before (upstream main.ts): both assertions fail, getOctokit received only retry, requestLog.
  • After: 5 suites, 37 tests pass; npm run style:check clean.
• New integration.yml job test-graphql-paginate walks two pages of issues with github.graphql.paginate.iterator against the real API and checks both github and a getOctokit secondary client expose graphql.paginate.
• Ran the rebuilt dist/index.js locally with a dummy token: typeof github.graphql.paginate and typeof getOctokit('t').graphql.paginate both return function; the previous build fails with Cannot read properties of undefined (reading 'iterator').

Links

• Add support for graphql pagination #309
• https://github.com/octokit/plugin-paginate-graphql.js

This change was prepared with an AI agent operated by KR-Ravindra, who reviewed and tested it.