jenkins: paginate PR commits to find the latest commit #153
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
When pushing Jenkins status to a PR, we need to reference the commit SHA the inline GitHub PR status relates to. These changes fixes a bug when handling enormous PRs with more than 100 commits, where we have to paginate to commits results for that PR to find the last commit SHA. Fixes nodejs#97
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
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.
When pushing Jenkins status to a PR, we need to reference the commit SHA the inline GitHub PR status relates to.
These changes fixes a bug when handling enormous PRs with more than 100 commits (e.g. nodejs/node#9745), where we have to paginate commits results for that PR to find the last commit SHA.
Fixes #97
/cc @nodejs/github-bot