Closed wuhuizuo closed 4 months ago
Hi @wuhuizuo. 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.
Name | Link |
---|---|
Latest commit | e8cb08b8a1fed98aea484866b604c23a199c9288 |
Latest deploy log | https://app.netlify.com/sites/k8s-prow/deploys/666c2d830b05d00008e99b8c |
Deploy Preview | https://deploy-preview-188--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.
/ok-to-test
@wuhuizuo More details about this change would be much appreciated.
/ok-to-test
@wuhuizuo More details about this change would be much appreciated.
@droslean I added some details in description. PTAL
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: droslean, wuhuizuo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Keep same with DCO GitHub app
DCO app will ignore the merge type commits: https://github.com/dcoapp/app/blob/main/lib/dco.js#L15-L19
So the branch updating triggered by contributor will not make the DCO check failed.
But the prow's "dco" plugin will fail when the branch has new merge type commits introduced by branch updating.