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
When a (force-)push is issued, the PR Verifier action tries to update the related check runs to the new commit. github.UpdateCheckRunOptions does provide a HeadSHA field but it is not updating the HeadSHA (potential GitHub actions bug). Therefore, we need to create a new CheckRun for the new commit instead of trying to rebind it.
#18 didn't solve the issue completely,
If the check runs weren't finished on synchornize, we are finishing and returning without making the duplicate for the new commit. We need to skip the return if finishing didn't yield any error.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Description
When a (force-)push is issued, the PR Verifier action tries to update the related check runs to the new commit.
github.UpdateCheckRunOptions
does provide aHeadSHA
field but it is not updating theHeadSHA
(potential GitHub actions bug). Therefore, we need to create a new CheckRun for the new commit instead of trying to rebind it.Related: google/go-github#1652
The text was updated successfully, but these errors were encountered: