Is your feature request related to a problem? Please describe.
There is no clean, idiomatic way to grab all the milestones from a repo. First is always applied, and it needs to be overwritten; however, it cannot go over a value of 100 without erroring.
Is this limit due to GitHub CLI? Is it still a real limit? Is there any way to paginate and append all the results together? I know the GitHub API has a paginate flag. Currently, I have abandoned using this extension due to this limit.
Describe the solution you'd like
gh milestone list --all - This is very idiomatic and describes what is wanted clearly.
gh milestone list - This is very idiomatic and describes what is wanted clearly. I don't specify a limit, so it isn't limited.
Describe alternatives you've considered
gh milesone list --first 99999 - Set First to some arbitrarily large number.
gh milesone list --first 0 - Set First to zero. Instead of returning no milestones, this would default to Int.max
gh milesone list --first -1 - Set First to negative one. I think the codebase requires a positive int, though. However, it's the same idea as setting it to zero.
However, setting values above 100 results in an error...
Requesting 99999 records on the `milestones` connection exceeds the `first` limit of 100 records.
Is your feature request related to a problem? Please describe. There is no clean, idiomatic way to grab all the milestones from a repo. First is always applied, and it needs to be overwritten; however, it cannot go over a value of
100
without erroring.Is this limit due to GitHub CLI? Is it still a real limit? Is there any way to paginate and append all the results together? I know the GitHub API has a paginate flag. Currently, I have abandoned using this extension due to this limit.
Describe the solution you'd like
gh milestone list --all
- This is very idiomatic and describes what is wanted clearly.gh milestone list
- This is very idiomatic and describes what is wanted clearly. I don't specify a limit, so it isn't limited.Describe alternatives you've considered
gh milesone list --first 99999
- Set First to some arbitrarily large number.gh milesone list --first 0
- Set First to zero. Instead of returning no milestones, this would default to Int.maxgh milesone list --first -1
- Set First to negative one. I think the codebase requires a positive int, though. However, it's the same idea as setting it to zero.However, setting values above
100
results in an error...Requesting 99999 records on the `milestones` connection exceeds the `first` limit of 100 records.