brand our bots consistently

[beckermr]

Our bots call themselves a few different things

• conda-forge-admin
• conda-forge-webservices[bot]
• "conda-forge-linting service"
• "conda-forge rerendering service"
• conda-forge-currator[bot]
• "friendly automated conda-forge-webservice"
• others I am forgetting...

It would be nice to decide on a consistent name and try to ensure that is used as much as possible in our tools. Some of this is unavoidable due to github account / app names, but I think we can get pretty close. I am excluding the regro-cf-autotick-bot from this discussion for now.

My vote for the name is conda-forge-admin since folks bump this account for the webservices commands.

To-do Items:

• [ ] decide on a name (likely conda-forge-admin)
• [ ] use the conda-forge-admin token as much as possible to make comments on PRs / issues / etc.
• [ ] set the git committer to conda-forge-admin in various spots (e.g., docker images, scripts, git CLI, github API calls, etc.)
• [ ] use the conda-forge-admin token as much as possible to make commits to feedstocks
• [ ] change text of comments made by bots to refer to themselves as the conda-forge-admin

cc @conda-forge/core

[jaimergp]

This is great and makes me happy. I think if we were to start from scratch, the obvious name would be conda-forge-bot, but that ship has sailed I guess because conda-forge-admin is way too popular now.

[beckermr]

Yeah I agree. I also think in many cases it makes sense to ask an admin to do something (eg update a team), so it's not so bad.

[jaimergp]

Works for me, then. Also, we can probably add the [bot] suffix to the name which gives a nice UI.

[beckermr]

Right. That bot suffix is actually added by github onto github apps, not machine accounts. Idk if we add it ourselves or if we'll need another app.

[h-vetinari]

I think if we were to start from scratch, the obvious name would be conda-forge-bot, but that ship has sailed I guess because conda-forge-admin is way too popular now.

I would actually like to move to conda-forge-bot. We could even help people transition very easily: if they address @conda-forge-admin, we can still do the task, but tell them (in a comment, as we already do anyway in most cases) to please use the new™ unified™ bot-interface @conda-forge-bot, and by the way, here are the docs for that if you're interested.

[beckermr]

We need to figure out the status of the conda-forge-bot github account if we really think it's worth the cost of switching. It seems like a pain for very little gain IMHO.

[beckermr]

One point possibly in favor of -admin is that it always seems to come up first when github autocompletes users when typing @ in an issue or PR and you get through conda-forge-. IDK how universal this is, but for me it is quite convenient.