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.

Since both the new and the old pagination parameterswill be supporteduntil the next version of theAPI, 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).

Since both the new and the old pagination parametersare still supportedinAPI 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).