fix(deploy): Increase page limit and add pagination to releases #299
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.
This pull request updates several functions in
tools/config.sh
to improve their handling of paginated API responses from GitHub. The changes increase the maximum number of pages processed in some functions and add pagination logic to others, ensuring more comprehensive data retrieval.Enhancements to pagination logic:
github_get_libs_idf
function to allow for deeper searches through commit history.github_commit_exists
function to improve the likelihood of finding a specific commit.Added support for paginated responses:
github_release_id
function to include pagination logic, enabling it to search through multiple pages of releases to find a specific release ID.github_release_asset_id
function to include pagination logic, allowing it to search through multiple pages of release assets to locate a specific asset ID.