Add option for blunderbuss to wait for tide status

[dobesv]

As a code reviewer, I don't want to review code which has not passed the test suites yet.

If I am asked to review something and then the tests fail after my review, it feels like I wasted my time as the person submitting it has to address the feedback from the tools anyway. However, if I do not review it immediately then I have to manually check back later to see whether the tests have passed - there is no way currently to set up a notification for tests passing under the current system.

This change allows configuring blunderbuss to request reviews when a matching commit status is reported instead of immediately when the pull request is opened or marked as ready for review. By setting the condition to one which matches the status that tide posts when all tests have passed but it is waiting for a label or for GitHub reviews to be posted, I can defer the automated review requests until the tests have passed.

This way someone can open a pull request, and when they eventually get all the tests passing, I can be prompted to review the pull request. I won't waste time reviewing a pull request that has failing tests or lint errors, and I also will not have to manually "check back" on all the pull requests to see which ones have the tests passing.

For example in this project, you could in theory set up blunderbuss to wait with requesting reviews until tide shows this status:

[k8s-ci-robot]

Hi @dobesv. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for k8s-prow ready!

Name	Link
🔨 Latest commit	71eb2c7
🔍 Latest deploy log	https://app.netlify.com/sites/k8s-prow/deploys/67786206cb661200080ea9a9
😎 Deploy Preview	https://deploy-preview-349--k8s-prow.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[matthyx]

/ok-to-test

[dobesv]

/retest

[dobesv]

I probably would need some guidance how to resolve that failure in pull-prow-integration, I'm having trouble relating that failure to my change here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dobesv
Once this PR has been reviewed and has the lgtm label, please assign cjwagner, michelle192837 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cmd/deck/OWNERS
• pkg/plugins/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment