Replies: 2 comments 3 replies
-
|
The main question here is whether |
Beta Was this translation helpful? Give feedback.
-
|
For more information, see the following: Lines 133 to 155 in 9b9e654 |
Beta Was this translation helpful? Give feedback.
-
|
All of that said, I'm going to close out this discussion given #9749 👍 |
Beta Was this translation helpful? Give feedback.
-
|
So the cli will return all the results matching all the criteria except --limit and then apply --limit to exclude some results? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think
The CLI help frames it differently: the flags are used to construct a GitHub search query, and GitHub search then returns the matching results. So the practical mental model I'd use is:
So if your main concern is I may be missing an implementation detail, but I don't think there is a documented per-qualifier evaluation order beyond "build search query -> sort/order results -> fetch up to |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I assume the order in which options are passed to
gh searchon the command line doesn't matter, but the order in which they're actually applied does.Currently I'm using
gh search prs -R owner/repowith the following options:--limit--merged--merged-at--base--sort--orderSo we start with all the PRs in
owner/repoand then apply filters according to the options passed - what order are these filters applied in?Beta Was this translation helpful? Give feedback.
All reactions