kubevirt-bot

Results 6443 comments of kubevirt-bot

@kubevirt-bot: Closing this issue. In response to [this](https://github.com/kubevirt/kubevirt/issues/12157#issuecomment-2479058800): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with...

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

@alaypatel07: #14365 failed to apply on top of branch "release-1.6": ``` Applying: API: Support for Dynamic Resource Allocation (DRA) Applying: add feature gates, render virt-launcher based on vmi spec Using...

@alaypatel07: GitHub didn't allow me to assign the following users: Sreeja1725. Note that only [kubevirt members](https://github.com/orgs/kubevirt/people) with read permissions, repo collaborators and people who have commented on this issue/PR can...

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: Closing this issue. In response to [this](https://github.com/kubevirt/project-infra/issues/3534#issuecomment-2543176665): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

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