Add ability to fetch pr runs in reverse order #382
Merged
Conversation
This file contains 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
We have over 100 PR runs. Increasing `fetchMaxPrChecks` to anything above 100 results in this error: ``` - Requesting 200 records on the `contexts` connection exceeds the `first` limit of 100 records. ``` This adds the ability to specify fetching pr runs using `last` instead of `first` as the only pr runs we're interested in is the absolute last one.
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.
We have over 100 PR runs. Increasing
fetchMaxPrChecksto anything above 100 results in this error:This adds the ability to specify fetching pr runs using
lastinstead offirstas the only pr runs we're interested in is the absolute last one.