Support for pagination for commit and pull details #28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TT-S3-D1
approved these changes
Aug 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #21
Support for pagination of relevant API endpoints.
Not required for GitHub commits, as they only return one commit object with all changed files.
Note: Head SHA for GitLab pull requests is determined by pullData.diff_refs.head_sha instead of pullData.sha (more readable). Shall be the same as of https://docs.gitlab.com/api/merge_requests/#response.
Manually tested against both platforms by a commit/pull request touching 46 files. "perPage" was manuelly set to 10 to force pagination.