kubevirt-bot

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/3805#issuecomment-2849317682): >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...

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: *dhiller* The full list of commands accepted by this bot can be found [here](https://prow.ci.kubevirt.io/command-help?repo=kubevirt%2Fproject-infra). The pull request process is...

@dhiller: Updated the `job-config` configmap in namespace `kubevirt-prow` at cluster `default` using the following files: - key `community-periodics.yaml` using file `github/ci/prow-deploy/files/jobs/kubevirt/community/community-periodics.yaml` In response to [this](https://github.com/kubevirt/project-infra/pull/3832): > > >**What this PR...

/remove-label needs-approver-review

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