kubevirt-bot

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

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *xpivarc* 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...

[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 [vladikr](https://github.com/vladikr) 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...

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

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

@iholder101: Closed this PR. In response to [this](https://github.com/kubevirt/community/pull/297#issuecomment-2548309483): >> @iholder101 Now that #362 is merged, can we close this? > >Yes, thank you > >/close Instructions for interacting with me...

/remove-label needs-approver-review

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