You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.
I'm trying to list all of the issues closed in a milestone:
gh is --list --state closed --milestone '1.1.0'
I know from GitHub web that there are 50 issues closed but I only get 30 on the command line from gh.
I can see that the repo command has the per_page setting as per the github api docs. Seems that hasn't been implemented here (or I've missed a command line switch, in which case, apologies).
What I'd really like for my automation purposes is to be able to retrieve the exhaustive issue list from GitHub via gh.
PS - great work, gh is brilliant.
The text was updated successfully, but these errors were encountered:
Same problem for gh re -l. There are several pages in the response. If you don't want to get one long page, you can use the Link header with rel next to follow the subsequent pages.
If someone can send a pull request I would really appreciate it and as long as it doesn't have any issues I am going to merge and release a new version right away, otherwise there isn't much I can't do for now. Sorry about that.
Can you explain how this is related to rate limiting? It's just standard pagination. GitHub expects you to use the metadata supplied by the API to get all the pages using consecutive calls. You'll have to make a ton of calls before you hit the rate limit, and in that case, you can still implement a backoff mechanism as a fallback.
I'm trying to list all of the issues closed in a milestone:
I know from GitHub web that there are 50 issues closed but I only get 30 on the command line from gh.
I can see that the repo command has the per_page setting as per the github api docs. Seems that hasn't been implemented here (or I've missed a command line switch, in which case, apologies).
What I'd really like for my automation purposes is to be able to retrieve the exhaustive issue list from GitHub via gh.
PS - great work, gh is brilliant.
The text was updated successfully, but these errors were encountered: