Background: @fejta-bot automatically marks issues as stale/rotten and closes them if they don't have any activity for certain number of days. It is an unprivileged user and is not a member of any of the Kubernetes GitHub orgs.
While enabling fejta-bot automation across all Kubernetes GitHub orgs, it was suggested to rename it to something "official": https://groups.google.com/d/topic/kubernetes-dev/9ps8uNXJ10k/discussion
This issue is to track discussing renaming fejta-bot - what to rename it as or if we should use another account entirely - and making sure that this is rolled out across orgs.
/sig contributor-experience
/sig testing
/cc @cblecker @fejta @spiffxp
nikhita
All 29 comments
serious-fejta-bot with a grumpy cat partially converted into a robot for it's profile pic
fejta
on 21 Apr 2019
/assign
Assigning it to myself to try to move this along in contribex
nikhita
on 18 Jul 2019
Any reason not to use one of the existing robots?
stevekuznetsov
on 18 Jul 2019
We need prow to react to the comments posted by these jobs, so it can't be @k8s-ci-robot. We could maybe use @k8s-github-robot, but I would prefer using a bot that has no privileges.
spiffxp
on 24 Jul 2019
You'll want to rename more than the account:
- https://testgrid.k8s.io/sig-testing-fejtabot
- https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/test-infra/fejta-bot-periodics.yaml
Things @fejta-bot does:
- /lifecycle stale | /lifecycle rotten | /close
- /retest
- /check-cla
- comment that API review may be needed
- create github issues
Naming is hard, WDYT of either of these?
- @k8s-triage-robot
- @k8s-commenter-robot
spiffxp
on 24 Jul 2019
/milestone v1.16
/assign
spiffxp
on 24 Jul 2019
k8s-cuddle-bot
k8s-repo-sanity-bot
k8s-triage-bot
chris-short
on 24 Jul 2019
+1 to k8s-triage-[ro]bot!
Can probably dovetail with some of the stuff mentioned here: https://github.com/kubernetes/community/issues/3456
justaugustus
on 24 Jul 2019
+1 to k8s-triage-bot
dims
on 24 Jul 2019
fajita-bot
InAnimaTe
on 24 Jul 2019
+1 to k8s-triage-robot. Since we have -robot suffixes for our other bot accounts, using -robot feels consistent.
To be clear, this would be creating a new account instead of renaming the original one, right? I'm assuming @fejta would like to keep @fejta-bot around for testing, etc... @fejta can you confirm? :)
nikhita
on 24 Jul 2019
/area github-management
To be clear, this would be creating a new account instead of renaming the original one, right? I'm assuming @fejta would like to keep @fejta-bot around for testing, etc... @fejta can you confirm? :)
I spoke offline with fejta last week and am confirming by proxy, as he's out this week
spiffxp
on 30 Jul 2019
I've squatted on http://github.com/k8s-triage-robot, what needs to happen now is:
- an avatar
- making a token
- getting test-infra oncall to add the new secret to the cluster
- swapping the jobs to use the new token
- renaming the jobs / dashboards referenced above
note that fejta-bot is not a member of the org, doesn't have any privileges, doesn't need to have 2fa enabled; if we want that to change, I'd rather consider that out of scope here, and ask that those so motivated create a followup issue to
spiffxp
on 30 Jul 2019
swapping the jobs to use the new token
renaming the jobs / dashboards referenced above
Created https://github.com/kubernetes/test-infra/pull/13683 to get the ball rolling
an avatar
Do we know who created the avatar for @k8s-github-robot? It's pretty dope!
nikhita
on 30 Jul 2019
Do we know who created the avatar for @k8s-github-robot? It's pretty dope!
👋 😄
spiffxp
on 31 Jul 2019
/priority important-soon
spiffxp
on 31 Jul 2019
Some avatar ideas from @alexcontini
dankohn
on 1 Aug 2019
/reopen
reverted in https://github.com/kubernetes/test-infra/pull/14548
nikhita
on 2 Oct 2019
@nikhita: Reopened this issue.
In response to this:
/reopen
reverted in https://github.com/kubernetes/test-infra/pull/14548
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.
k8s-ci-robot
on 2 Oct 2019
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
fejta-bot
on 3 Jan 2020
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
fejta-bot
on 2 Feb 2020
/remove-lifecycle rotten
cblecker
on 11 Feb 2020
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
fejta-bot
on 14 Jul 2020
/remove-lifecycle stale
On Tue, Jul 14, 2020 at 8:05 PM fejta-bot notifications@github.com wrote:
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
https://github.com/fejta.
/lifecycle stale—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/12296#issuecomment-658217260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24BUEGR6CXJ6ZJWTD3ICDR3RUM3ANCNFSM4HHLK64A
.
nikhita
on 14 Jul 2020
@spiffxp @nikhita Is there anything I can do to help push this forward?
chris-short
on 13 Aug 2020
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
fejta-bot
on 11 Nov 2020
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
fejta-bot
on 11 Dec 2020
I don't have a strong opinion on this but the errors in https://github.com/kubernetes/test-infra/pull/14548#issuecomment-755628839 seem dubious. This issue should be pretty straightforward if someone wants to do it, otherwise we should probably close it out.
BenTheElder
on 6 Jan 2021
/remove-lifecycle rotten
/milestone v1.21
Agree this should be straightforward
spiffxp
on 8 Jan 2021
Related issues
Aisuko
·
3Comments
chaosaffe
·
3Comments
BenTheElder
·
3Comments
sjenning
·
4Comments
fejta
·
4Comments
Most helpful comment
serious-fejta-botwith a grumpy cat partially converted into a robot for it's profile pic