fejta-bot
fejta-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...
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`. Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). /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...
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`. Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). /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...
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...