We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can see on the GitHub API that the Events API (https://developer.github.com/v3/activity/events/) can be based on pagination (only page property, no per_page property).
Currently, the octokit framework let us get events with a simply collection (no paging system).
Could you fix it ?
The text was updated successfully, but these errors were encountered:
@ryangribble, @shiftkey could this one be closed as solved because Octokit.NET in one little step from release with pagination support?
Sorry, something went wrong.
Fixed in #1240 and will be available in the next Octokit release...
No branches or pull requests
I can see on the GitHub API that the Events API (https://developer.github.com/v3/activity/events/) can be based on pagination (only page property, no per_page property).
Currently, the octokit framework let us get events with a simply collection (no paging system).
Could you fix it ?
The text was updated successfully, but these errors were encountered: