OpenShift Bot
OpenShift Bot
Rotten issues close after 30d of inactivity. Reopen the issue by commenting `/reopen`. Mark the issue as fresh by commenting `/remove-lifecycle rotten`. Exclude this issue from closing again by commenting...
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this...
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing...
Rotten issues close after 30d of inactivity. Reopen the issue by commenting `/reopen`. Mark the issue as fresh by commenting `/remove-lifecycle rotten`. Exclude this issue from closing again by commenting...
/jira refresh The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this...
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing...
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this...
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing...
/jira refresh The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.