kubernetes
Fixed the cri api pkg link in sig-node/Readme.md
@vaibhav2107 please feel free to reopen this PR after you follow the guidance provided by @SergeyKanzhelev for now I'm going to go ahead and close this out.
Thanks!
/close
@mrbobbytables: Closed this PR.
In response to this:
@vaibhav2107 please feel free to reopen this PR after you follow the guidance provided by @SergeyKanzhelev for now I'm going to go ahead and close this out.
Thanks!
/close
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.
@vaibhav2107: Reopened this PR.
In response to this:
/reopen
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vaibhav2107 Once this PR has been reviewed and has the lgtm label, please assign nikhita for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@mrbobbytables I have reopened the PR and done the changes that were suggested, You can have a look
@vaibhav2107: 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 |
|---|---|---|---|---|
| pull-community-verify | 803f56a921d360440df91c6b27d6431f9d737e66 | link | true | /test pull-community-verify |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
please squash commits and rerun
make
/close
reopen if you plan to continue with this.
@SergeyKanzhelev: Closed this PR.
In response to this:
please squash commits and rerun
make/close
reopen if you plan to continue with this.
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.