kubevirt-bot

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

/remove-label needs-approver-review

Hi @kpol-lgx. 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...

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

@kpol-lgx: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests: Test name | Commit | Details | Required | Rerun...

PR needs rebase. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the...

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