Closed knative-automation closed 3 years ago
Hi @knative-automation. Thanks for your PR.
I'm waiting for a google 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.
/ok-to-test /lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nlopezgi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold
holding off till https://github.com/google/knative-gcp/pull/2169 is in and 0.21 branch is cut
@knative-automation: The following test failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
pull-google-knative-gcp-wi-tests | cb8c0bd1dcbbbe2e77f4f44b5e3052bcacf68e83 | link | /test pull-google-knative-gcp-wi-tests |
Full PR test history. Your PR dashboard.
New changes are detected. LGTM label has been removed.
closing as the merge did not work properly, lets just wait for the bot to create a new PR.
Cron. -knative-prow-robot
/cc @nlopezgi @zhongduo /assign @nlopezgi @zhongduo
Produced via:
Details: