### Summary in the [List repository tree document](https://docs.gitlab.com/ee/api/repositories.html#list-repository-tree), it indicates the api uses keyset pagination. However, in my testing with the api, it returns page number. ### Steps to reproduce ```http curl --request GET \ --url 'https://gitlab.com/api/v4/projects/{project}/repository/tree?order_by=id&pagination=keyset&per_page=100&recursive=true&ref={ref}&sort=asc' \ --header "Private-Token: {token}" ``` it returns headers with: `x-next-page: 2 x-page: 1 x-per-page: 100 x-prev-page:` ### Example Project ### What is the current _bug_ behavior? no page_token is returned, page number is returned instead ### What is the expected _correct_ behavior? page_token returned ### Relevant logs and/or screenshots ### Output of checks #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`) </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes