You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 1, 2017. It is now read-only.
Copy file name to clipboardExpand all lines: content/changes/2014-05-08-improved-pagination-for-the-repository-commits-api.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,4 +15,4 @@ This new approach improves the reliability of this endpoint, which on rare occas
15
15
16
16
The old way of paginating, using`top`,`last_sha`, and`per_page` parameters, is still supported in API v3, but it will be removed in the[next major version of the API](https://developer.github.com/v3/versions/#v3-deprecations). API clients that are manually constructing URLs for pages should be modified to use the new parameters. Even better, API clients shouldn't construct URLs for pages manually, but should use[page links provided by the`Link` header](/guides/traversing-with-pagination/) in API responses.
17
17
18
-
Since both the new and the old pagination parameters are still supported in API v3, API clients shouldn't notice any changes today. Still, if you notice any problems with this endpoint, please[let us know](https://github.com/contact?form%5Bsubject%5D=API:+Commits+pagination+changes).
18
+
Since both the new and the old pagination parameters are still supported in API v3, API clients shouldn't notice any changes today. Still, if you notice any problems with this endpoint, please[let us know](https://github.com/contact?form%5Bsubject%5D=API:+Commits+pagination+improvements).