You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With nodejs/node#9745 which has 100+ commits, we just found that the bot pushes Jenkins build status to the wrong commit SHA.
Probably because the list of commits fetched in findLatestCommitInPr() is paginated by GitHub, and therefore we'll have to do some pagination tricks to ensure we actually fetch the latest commit of that specific PR, even if it consists of hundreds of commits.
The text was updated successfully, but these errors were encountered:
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.
Fixesnodejs#97
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#97
With nodejs/node#9745 which has 100+ commits, we just found that the bot pushes Jenkins build status to the wrong commit SHA.
Probably because the list of commits fetched in findLatestCommitInPr() is paginated by GitHub, and therefore we'll have to do some pagination tricks to ensure we actually fetch the latest commit of that specific PR, even if it consists of hundreds of commits.
The text was updated successfully, but these errors were encountered: