kcp CI Bot

Results 572 comments of kcp CI Bot

Rotten issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle rotten`. /close

@embik: once the present PR merges, I will cherry-pick it on top of release-0.24 in a new PR and assign it to you. In response to [this](https://github.com/kcp-dev/kcp/pull/3126#issuecomment-2098540377): >/cherry-pick release-0.24 Instructions...

@kcp-ci-bot: Closing this issue. In response to [this](https://github.com/kcp-dev/kcp/issues/1818#issuecomment-2169209114): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

LGTM label has been added. Git tree hash: c16bc1a9657b14c0541319f3b66fe6d4ecd7e1d8

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

@embik: new pull request created: #3127 In response to [this](https://github.com/kcp-dev/kcp/pull/3126#issuecomment-2098540377): >/cherry-pick release-0.24 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...

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with `/remove-lifecycle stale`. If this issue is safe to...

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

@kcp-ci-bot: Closing this issue. In response to [this](https://github.com/kcp-dev/kcp/issues/2818#issuecomment-2195621101): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...