kubevirt-bot

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/user-guide/pull/827#issuecomment-2679608536): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

/remove-label needs-approver-review

Hi @brandboat. 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...

@brandboat: Cannot trigger testing until a trusted user reviews the PR and leaves an `/ok-to-test` message. In response to [this](https://github.com/kubevirt/kubevirt/pull/13898#issuecomment-2650883188): >/retest Instructions for interacting with me using PR comments are...

Pull requests that are marked with `lgtm` should receive a review from an approver within 1 week. After that period the bot marks them with the label `needs-approver-review`. /label needs-approver-review

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

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