/assign @spiffxp @fejta @timothysc
Shouldn't we close this one to help?
馃 馃
s/200/300? 馃槀
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 is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/remove-lifecycle stale
we have 279 open issues currently.
250!
/assign @AishSundar
@mithrav: GitHub didn't allow me to assign the following users: AishSundar.
Note that only kubernetes members and repo collaborators can be assigned.
In response to this:
/assign @AishSundar
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.
Also adding Aish =)
/assign
@AishSundar: GitHub didn't allow me to assign the following users: AishSundar.
Note that only kubernetes members and repo collaborators can be assigned.
In response to this:
/assign
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.
@AishSundar sent you a collaborator link :-)
@krzyzacy Thanks :)
/assign @AishSundar
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 is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/remove-lifecycle stale
/milestone 1.12
Let's see what happens after some grooming...
/milestone v1.13
We are now at 303 open issues
/milestone v2.0 :)
probably easier to rename the issue 馃槀 (s/200/300)
s/200 open //
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 is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/remove-lifecycle stale
72 to go!
we could get it down to 71 if we close this issue. :)
/milestone v1.14
@ixdy: You must be a member of the kubernetes/kubernetes-milestone-maintainers github team to set the milestone.
In response to this:
/milestone v1.14
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.
:( nobody likes you, @k8s-ci-robot
@k8s-ci-robot hold my 馃嵑
/pony new year
In response to this:
/pony new year
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.
/milestone 2019-goals
Not even going to try this quarter lol
isn't this more like
/milestone someday ? :wink:
/milestone ${CurrentMilestone}+1
@krzyzacy: You must be a member of the kubernetes/kubernetes-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.
In response to this:
/milestone ${CurrentMilestone}+1
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.
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 is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
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.
/lifecycle rotten
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.
/close
@fejta-bot: Closing this issue.
In response to this:
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.
/close
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.
Good bot :-)
/woof
given now we only have 288 open issues, good bot :-)
In response to this:
/woof
given now we only have 288 open issues, good bot :-)
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.
We're now legitimately below both 294 and 200 issues!
Most helpful comment
Shouldn't we close this one to help?
馃 馃