[Proposal] Add "bot account" as a type of user

[a1012112796]

• Gitea version (or commit ref):
• Git version:
• Operating system:
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

Hello, Sometimes we will want add a new accout which only used by bot apps to call api. So I think maybe we can add it as a new user type. It maybe follow this tips.

• Bot account willn't login on ui page
• Bot account maybe should not have ability create it's own repos
• Each boat account should belong to a user or an org, and this user or the owners of this org can change the setting of the bot account. (important)
• manager can limit the max number of the bot acounts that one user and org can have
• Bot account is not necessary to request email and the system will't send email notify and action notify to them also
• show bot label on frofile page
• ......

Maybe usefull to fix #12985.

Screenshots

[silverwind]

• Bot account should not have a password, or if git password auth is really desired, should have it optional with the ability to unset password.
• Bot account should have the ability to create app tokens and add ssh/gpg keys.

[basxto]

This would also be interesting for gpg key checks of mirrored repositories.
You could just add a bot for the original owner.

[mscherer]

I would say that multiple owners could also be useful, so more than 1 person can operate the bot (useful if one of the owner is away)

[lafriks]

My proposal would be:

• Bot can be server wide (managed by server admins) - owner_id = nil
• Bot can be organization owned (managed by organization admins) - owner_id = organization id
• Bot can be user owned (managed by single user) - owner_id = user id

[a1012112796]

now, I found it in gh, maybe we can add a similar mechanism.
https://docs.github.com/en/free-pro-team@latest/developers/apps/about-apps#about-github-apps

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[jpraet]

I have a bot account in my CI pipeline that adds commits to PR's (code formatting and cleanup, dependency upgrades, ..).
We trust this bot, so these commits don't require review. But these commits cause the earlier approvals of the PR to become stale.
Is that something that could be included in the requirements for the bot account implementation?

[dpschen]

Maybe this can also be used to change the sort order in the request review dropdown:
Because we have a bot that deploys a preview and creates a comment with a preview link the bot will always appear as the first suggestion in the list.

[rakshith-ravi]

Have there been any proposals to implement this? If one were to start implementing this, what would be a good starting point?

[a1012112796]

Have there been any proposals to implement this? If one were to start implementing this, what would be a good starting point?

looks github app is similar with this.

[techknowlogick]

So technically there is now a type of bot, but it doesn't have any logic for displaying a badge etc..

[rakshith-ravi]

So technically there is now a type of bot, but it doesn't have any logic for displaying a badge etc..

You mean with current Gitea? How would bot accounts work with the existing version?

[delvh]

Well… We recognize them since #24026.
Practically, however, the only effect this has at the moment is prohibiting login and reserving the username.
Have a look at the PR for more details.

[Frankkkkk]

Related somewhat: Support configuring permissions of automatic tokens of Actions jobs #24635