kubevirt-bot

Results 6143 comments of kubevirt-bot

[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 [mhenriks](https://github.com/mhenriks) for approval. For more...

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

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

[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 [aglitke](https://github.com/aglitke) for approval. For more...

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits. :memo: **Please follow instructions in the [contributing guide](https://github.com/kubevirt/containerized-data-importer/blob/master/CONTRIBUTING.md) 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: Closed this PR. In response to [this](https://github.com/kubevirt/containerized-data-importer/pull/3695#issuecomment-3338311855): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

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