kubevirt-bot

Results 5738 comments of kubevirt-bot

[APPROVALNOTIFIER] This PR is **NOT APPROVED** This pull-request has been approved by: **Once this PR has been reviewed and has the lgtm label**, please assign [sradco](https://github.com/sradco) for approval. For more...

@dasionov: The specified target(s) for `/test` were not found. The following commands are available to trigger required jobs: * `/test build-hco-test-utils-image` * `/test pull-hyperconverged-cluster-operator-e2e-k8s-1.30` * `/test pull-hyperconverged-cluster-operator-e2e-k8s-1.31` Use `/test all`...

@dasionov: The specified target(s) for `/test` were not found. The following commands are available to trigger required jobs: * `/test build-hco-test-utils-image` * `/test pull-hyperconverged-cluster-operator-e2e-k8s-1.30` * `/test pull-hyperconverged-cluster-operator-e2e-k8s-1.31` Use `/test all`...

@dasionov: Closed this PR. In response to [this](https://github.com/kubevirt/hyperconverged-cluster-operator/pull/3106#issuecomment-2470750927): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior,...

Hi @dependabot[bot]. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with `/ok-to-test` in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators...

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *awels* The full list of commands accepted by this bot can be found [here](https://prow.ci.kubevirt.io/command-help?repo=kubevirt%2Fhostpath-provisioner-operator). The pull request process is...

@dependabot[bot]: 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...

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

@dhiller: This request has been marked as needing help from a contributor. ### Guidelines - **No Barrier to Entry** - **Clear Task** - **Solution Explained** - **Provides Context** - **Identifies...