Describe the feature or problem you’d like to solve
A number of options have a -L or --limit option with defaults (20 or 30) and can be supplied with a --limit n where n is a positive integer option, e.g.:
gh issue list --state=open --limit=2000 --json=number
However, if the user needs to get a list of all of the open issue numbers they need to either guess how many there might be or supply a very high number.
Proposed solution
Either have a --nolimit flag or allow either --limit=0 or --limit=-1 to mean no limit. This would allow things like pre-populating a list of all open tickets for pre-commit, etc. hooks to use to validate commit messages include only open ticket numbers without possibly doing multiple calls during the commit message processing.
Alternatively, a documented mechanism to get more items when piping output could be added - to me this seems more complex to both implement and use.
Additional context
Describe the feature or problem you’d like to solve
A number of options have a
-Lor--limitoption with defaults (20 or 30) and can be supplied with a--limit nwhere n is a positive integer option, e.g.:However, if the user needs to get a list of all of the open issue numbers they need to either guess how many there might be or supply a very high number.
Proposed solution
Either have a
--nolimitflag or allow either--limit=0or--limit=-1to mean no limit. This would allow things like pre-populating a list of all open tickets for pre-commit, etc. hooks to use to validate commit messages include only open ticket numbers without possibly doing multiple calls during the commit message processing.Alternatively, a documented mechanism to get more items when piping output could be added - to me this seems more complex to both implement and use.
Additional context