kubevirt-bot

Results 5933 comments of kubevirt-bot

@dhiller: The following commands are available to trigger required jobs: * `/test build-autoowners-image` * `/test build-bootstrap-image` * `/test build-fedora-coreos-kubevirt-image` * `/test build-kubekins-e2e-image` * `/test build-kubevirt-infra-bootstrap-image` * `/test build-kubevirt-kubevirt.github.io-image` * `/test...

@dhiller: 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...

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our [release note process](https://git.k8s.io/community/contributors/guide/release-notes.md) to remove it. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md)....

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 **NOT APPROVED** This pull-request has been approved by: **Once this PR has been reviewed and has the lgtm label**, please assign [mhenriks](https://github.com/mhenriks) for approval. For more...

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...

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Rotten issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle rotten`. /close

@kubevirt-bot: Closed this PR. In response to [this](https://github.com/kubevirt/containerized-data-importer/pull/3703#issuecomment-3322817484): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

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...