<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=537234) </details> <!--IssueSummary end--> Original discussion: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/188177#note_2464613037 Since there was an API support (well, partial since as you noted we use the oktokit) — I wanted to explore that path. I see this docs section in the [oktokit repo](https://github.com/octokit/octokit.rb?tab=readme-ov-file#pagination): > Many GitHub API resources are paginated. While you may be tempted to start adding :page parameters to your calls, the API returns links to the next, previous, and last pages for you in the Link response header as Hypermedia link relations. > > ```rb > issues = client.issues 'rails/rails' > issues.concat client.get(client.last_response.rels[:next].href) > ``` And I think we even use it in a github import wrapper: [lib/gitlab/github_import/client.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/b019c6f28b1333437131f060c432e131d41e3776/lib/gitlab/github_import/client.rb#L130-158)