Closed vishnukarthikl closed 2 years ago
Hi @vishnukarthikl. Thanks for your PR.
I'm waiting for a kubevirt 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
@vishnukarthikl: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
kubevirt-io-presubmit-markdown-linter | 99029e9e1e151346ed772fd9e670a6a4647ab4a3 | link | true | /test kubevirt-io-presubmit-markdown-linter |
/retest
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mazzystr
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What this PR does / why we need it: Remove duplicate paragraph that is already mentioned a few lines above.