kubevirt-bot

Results 6447 comments of kubevirt-bot

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *brianmcarey* 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 following 2 configmaps: * `job-config` configmap in namespace `kubevirt-prow` at cluster `default` using the following files: - key `project-infra-postsubmits.yaml` using file `github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-postsubmits.yaml` - key `project-infra-presubmits.yaml` using file...

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

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: Closed this PR. In response to [this](https://github.com/kubevirt/user-guide/pull/835#issuecomment-2972989825): >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...

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