When using --per-page option for list commands, the CLI doesn't show that pagination kicked in and it doesn't show how many results are in GitLab. ---- Note from @jamesliu-gitlab on https://gitlab.com/gitlab-org/cli/-/merge_requests/1112#note_1199111824: I noticed that a bunch of other commands support pagination too (basically any commands that retrieve data via the [go-gitlab List\* methods](https://github.com/xanzy/go-gitlab/blob/ac5896fb7752ddd0eacaf1f724acef4b1d121455/gitlab.go#L212-L220), however we don't expose enough of the API response to allow users to actually paginate through the results. This is a bit of a UX issue. For example, if I list the schedules on a project with 14 schedules but set `--per-page 5`, I don't get an indication of the total number of results or pages: ``` ❯ ~/code/gl/cli/bin/glab schedule list --per-page 5 Showing 5 Schedules on gitlab-org/security-products/analyzers/sast-analyzer-deps-bot (Page 1) ID Description Cron Owner Active 319781 Release Issue Creation 0 16 4 * * amarpatel true 277311 Security Code Scan 0 0 8 * * vbhat161 true 277310 Brakeman 0 0 8 * * vbhat161 true 277308 PMD Apex 0 0 8 * * vbhat161 true 277307 NodeJS Scan 0 0 8 * * vbhat161 true ``` Existing commands have the same behaviour too. Running `glab mr list --per-page 5` on a repo with more than 5 MRs won't display the total number of MRs or pages. I guess it's more problematic if the default `--per-page` isn't large enough and leaves a false impression that some results are missing. <!-- implementation plan added during 2026-09 backlog triage --> ## Implementation plan > **Note:** This plan was drafted during an AI-assisted triage of the backlog and has not been validated by a maintainer. Treat it as a starting point: file paths, line numbers, and the approach may need adjusting. 1. Teach the shared title helper about page counts. In `internal/utils/display.go`, add `TotalPages int` and `HasNextPage bool` to `ListTitleOptions`, and update `(*ListTitleOptions).Describe()` so the page suffix renders `(Page N of M)` when `TotalPages > 0` and stays `(Page N)` otherwise. When `Total` is 0 but `HasNextPage` is true (GitLab omits `X-Total` and `X-Total-Pages` on large result sets, see `internal/commands/ci/delete/delete.go:246-247`), append a hint that more results are available and that `--page` fetches them. Extend `Test_Describe` in `internal/utils/display_test.go` with cases for total pages, the next-page hint, and the unchanged no-total case. 2. Fix `glab issue list` and `glab incident list`. In `internal/commands/issuable/list/issuable_list.go`, the `*gitlab.Response` from `client.Issues.ListProjectIssues`, `client.Issues.ListGroupIssues`, and the epic branch is currently discarded with `_` (lines 292 to 322). Capture it, then next to `title.CurrentPageTotal` at lines 325 to 327 set `title.Total = int(resp.TotalItems)`, `title.TotalPages = int(resp.TotalPages)`, and `title.HasNextPage = resp.NextPage > 0`, guarding for a nil response. 3. Fix `glab schedule list`, the reporter's example. In `internal/commands/schedule/list/list.go`, change the `getSchedules` package var (line 17) to return `([]*gitlab.PipelineSchedule, *gitlab.Response, error)` instead of dropping the response, set the three new title fields at lines 88 to 91, and update the three stub overrides in `internal/commands/schedule/list/list_test.go` (lines 30, 75, 111) to match the new signature. 4. Fix `glab mr list`. In `internal/api/merge_request.go`, return the `*gitlab.Response` from `listMRsBase` and `listGroupMRsBase` and surface it from the exported `ListMRs` (line 122) and `ListGroupMRs` (line 37) vars. Return a nil response from `listMRsWithAssigneesOrReviewers` and `listGroupMRsWithAssigneesOrReviewers`, because those merge results from several requests and no single total applies. Then set the title fields in `internal/commands/mr/list/mr_list.go` at lines 355 to 357, only when the response is non-nil. 5. Update the callers and stubs that the step 4 signature change touches: `internal/commands/mr/mrutils/mrutils.go:333`, `internal/commands/ci/ciutils/utils.go:82`, `internal/commands/mr/list/mr_list.go:339` and `:349`, and the `api.ListMRs` overrides in `internal/commands/mr/update/mr_update_test.go:123`, `internal/commands/mr/delete/mr_delete_test.go:75`, `internal/commands/mr/mrutils/mrutils_test.go` (lines 398, 408, 418, 498, 514), and `internal/commands/ci/run/run_test.go:334`. These are mechanical, discard the response where the caller does not need it. 6. Add command-level tests. In `internal/commands/mr/list/mr_list_test.go` and `internal/commands/issuable/list/issuable_list_test.go`, the gitlabtesting mocks currently return a nil `*gitlab.Response`. Add one case per file that returns `&gitlab.Response{TotalItems: 42, TotalPages: 21, CurrentPage: 1, NextPage: 2}` and asserts a title of the form `Showing 2 of 42 open merge requests on OWNER/REPO. (Page 1 of 21)`. Existing assertions that pass a nil response keep their current `Showing 2 ... (Page 1)` output, so they need no edits. No `cobra.Command` help text changes, so `make gen-docs` is not required, run `make test` and `make lint`.