Do not compare dates to detect new commits #911
Merged
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.
NCU was relying on
timelineItems
to get date for the last push event, but turns out that gives us the commit date (not very relevant for what we're testing as the commit and push can be done at different moment), not the date when the push was received by GH servers. What we can do instead is to use the SHA of the commit, and compare it with the last approving review.I also take the opportunity to update
ncu-ci
to pass the now required commit SHA (I reused the--certify-safe
flag for that), I didn't mark it as semver-major given that the breaking change was made upstream, so the PR is fixing, rather than breaking, but happy to reconsider.This will have the effect of making
request-ci
work only on approved PRs, but currently it is not working at all, so I'd take as an improvement.Commits should land separately, and it probably makes sense to review them separately as well.