Test-infra: Make fejta-bot admit that it is a bot

Created on 26 Jan 2018 · 17Comments · Source: kubernetes/test-infra

I would be good to make @feta-bot a bit more user-friendly. It could admit that it is an automated computer program, and is a bot. To newer users not familiar with Google bots, it may not be evident what a @feta-bot is.

See https://github.com/kubernetes/kops/issues/3566#issuecomment-359313231 for the reason that I am mentioning this.

Source

chrislovecnm

Most helpful comment

I admit nothing

fejta-bot on 28 Jan 2018

😄26

All 17 comments

Oh no :(

stevekuznetsov on 26 Jan 2018

/kind enhancement
/assign @fejta

stevekuznetsov on 26 Jan 2018

I admit nothing

fejta-bot on 28 Jan 2018

😄26

@fejta-bot it's hard to figure out what humans want these days

ghost on 28 Jan 2018

😄9

@fejta-bot @kargakis-robot shhhh don't ever let human know our secret mission besides pretending to be bots

/bark

k8s-ci-robot on 28 Jan 2018

😄10

@k8s-ci-robot:

In response to this:

@fejta-bot @kargakis-robot shhhh don't ever let human know our secret mission besides pretending to be bots

/bark

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 28 Jan 2018

❤1 👍1

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 29 Apr 2018

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
/remove-lifecycle stale

fejta-bot on 29 May 2018

lol. fejta-bot does not want to change

/remove-lifecycle rotten

craigbox on 17 Jun 2018

😄3

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 15 Sep 2018

/remove-lifecycle stale

ixdy on 17 Sep 2018

/meow

ixdy on 17 Sep 2018

@ixdy:

In response to this:

/meow

k8s-ci-robot on 17 Sep 2018

@BenTheElder this might be a good argument for k8s-cherrypick-robot :)

stevekuznetsov on 1 Oct 2018

bot, robot ... fejta-bot even _looks_ like a robot and the bio suggests it... as do the form comments it posts... if anything using it as a robot in more high profile places might make that more obvious /shrug

I'd rather not create new accounts right now, the k8s-infra-team discussions are still figuring out how we can create & manage new creds under the CNCF. I don't want another email + github account to migrate for a use case that could just as easily use one of the existing accounts for now.

BenTheElder on 1 Oct 2018

😄1

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 30 Dec 2018

Can we just change the message to explicitly say that this is an automated message by a bot?

Something as simple as:

This message is posted by an automated bot. Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).

/remove-lifecycle stale