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

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

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

@fossedihelm: The specified target(s) for `/test` were not found. The following commands are available to trigger required jobs: * `/test pull-kubevirt-apidocs` * `/test pull-kubevirt-build` * `/test pull-kubevirt-build-arm64` * `/test pull-kubevirt-build-s390x`...

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: *alicefr* The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=kubevirt%2Fkubevirt). The pull request process is...

/remove-label needs-approver-review

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *akalenyu* The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=kubevirt%2Fcontainerized-data-importer). The pull request process is...

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