Skip to content

handle pagination in github adapter #85

Description

@zgeoff

GitHub REST API responses are capped at 100 items per page. All provider reader methods (listWorkItems, listRevisions, listSpecs) currently fetch a single page. This means the system
silently drops items beyond the 100th.

Implement cursor-based pagination in the GitHub provider readers. Octokit supports automatic pagination via octokit.paginate() — use it for list endpoints. Consider an upper bound (e.g., 500
items) to prevent unbounded API calls on large repos.

Affected methods: listWorkItems (issues), listRevisions (PRs), and potentially listSpecs (tree entries, though the Trees API returns all entries in one response so this may not need
pagination).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions