-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't suggest a reviewer I've already assigned. #4272
Comments
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten
…On Thu, Feb 8, 2018 at 11:59 AM, fejta-bot ***@***.***> wrote:
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 close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
<https://github.com/fejta>.
/lifecycle rotten
/remove-lifecycle stale
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4272 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMK-Rb56dy-DzyB5oD1k7oouQ8ZDzMks5tS1IrgaJpZM4PIFHH>
.
|
@kubernetes/sig-testing-bugs is this perhaps already fixed? |
It could be. This process is no longer managed by mungegithub, it is now handled by Prow and I made a bunch of fixes while migrating, so this might not be an issue anymore. Please reopen if this is still an issue. |
This is not fixed in prow. @tnozicka came across this in openshift/origin#18513 (comment) and I would like to track it somewhere so we can potentially fix it. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/sig contributor-experience |
/remove-lifecycle frozen |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
roberthbailey was already assigned when the bot said that
The text was updated successfully, but these errors were encountered: