kubernetes
kubernetes-admins group to help fight spam
volunteering ✋🏾 to help cleanup spam. Deleting issues needs admin privs.
context some recent pokes to github admins for cleanup:
- https://kubernetes.slack.com/archives/C01672LSZL0/p1717176398639109
- https://kubernetes.slack.com/archives/C01672LSZL0/p1716209389720009
- https://kubernetes.slack.com/archives/C01672LSZL0/p1713264674072169
- https://kubernetes.slack.com/archives/C01672LSZL0/p1709499192141139
- https://kubernetes.slack.com/archives/C01672LSZL0/p1706446526481819
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dims, jasonbraganza
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~config/kubernetes/OWNERS~~ [jasonbraganza]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/hold
will also wait for the other, more experienced folk, to weigh in
I am okay with this only if we can absolutely not come up with an alternative. I would prefer not adding admin privileges beyond the set of GH admins and required bots.
One solution that I am currently tinkering with is since the k8s-ci-robot has admin access already, a prow plugin that can recognise comments like /delete-issue and we can add in @dims as someone authorised to comment that and the k8s-ci-robot can handle the deletion for us.
One solution that I am currently tinkering with is since the k8s-ci-robot has admin access already, a prow plugin that can recognise comments like /delete-issue and we can add in @dims as someone authorised to comment that and the k8s-ci-robot can handle the deletion for us.
works for me!