Log more information about why commits_in_range isn't working. #1811
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 is a followup to #1801 to further investigate why it is not working correctly. From what I can tell, the
/commits
endpoint seems to be returning results out of order. I'm expecting them to be in commit order, but that doesn't seem to be the case (but I still can't reproduce locally). This adds a log message to help me confirm that theory. If that is the case, I will likely need to add something that traverses the parent commits to get the correct set of commits, or perhaps consider using the GraphQL endpoint which might be more reliable.