fix(zsh): fetch 100 items in the ghi and ghpc pickers - #382
Merged
Conversation
Both pickers omitted --limit, so they took gh's default of 30 while every sibling helper (_gh_pr_pick, _gh_issue_pick, ghsq, ghrb, ghrp) already used --limit 100. For ghpc this is a plain cap. For ghi it also broke the ordering the picker exists to provide: the jq runs sort_by(.createdAt) client-side, but over a server-side newest-30 slice, so "oldest-first with the cursor on the oldest" was sorting the newest 30 and calling the result oldest. Measured in laurigates/claude-plugins (43 open issues): ghi showed as oldest #2174 2026-07-27 actually oldest #1017 2026-04-09 The 13 genuinely-oldest issues were unreachable from the picker. Verified by extracting the shipped pipeline with sed and running it rather than retyping it; #1017 now sorts to the top, matching a --limit 100 control. ghprls keeps no limit on purpose: it is a documented thin `gh pr list` passthrough (`ghprls -L 50 --state all`). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPT64ByhPz27jQDUUnvUFU
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
--limit 100to thegh issue list/gh pr listcalls behind theghiandghpcfzf pickers.Why
Both omitted
--limit, so they tookgh's default of 30 — while every sibling helper (_gh_pr_pick,_gh_issue_pick,ghsq,ghrb,ghrp) already used--limit 100. The inconsistency was the tell.For
ghpcthis is a plain cap. Forghiit also broke the ordering the picker exists to provide. The jq runssort_by(.createdAt)client-side, but over a server-side newest-30 slice — so the header promising oldest-first with the cursor on the oldest was sorting the newest 30 and presenting that as oldest.Measured against
laurigates/claude-plugins(43 open issues, so the cap bites today):3.5 months off, with the 13 genuinely-oldest issues unreachable from the picker.
How
Two-line change. Verified by extracting the shipped pipeline with
sedand running it against a live repo rather than retyping the logic —#1017now sorts to the top, matching a--limit 100control.zsh -npasses on the rendered~/.zshrc, andchezmoi applytouched exactly the two intended lines.ghprlsdeliberately keeps no limit: it is a documented thingh pr listpassthrough (ghprls -L 50 --state all).