Update bot users with Gitlab bot flag

Same with https://git.drupalcode.org/tugboat

Others known?

I don’t think GitLab has a “is bot” flag for accounts. I don’t see any checkbox or selection for this when editing an account as an admin or the user themselves. The only distinguishing characteristic about https://git.drupalcode.org/project_88996_bot I see is that the username ends in _bot and the display name makes it look related to a token.

https://git.drupalcode.org/users/project_88996_bot/ is automatically created by GitLab. I believe https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html is the documentation for that type of account.

https://git.drupalcode.org/Project-Update-Bot is actually a normal Drupal.org account which is automated.

There’s no restriction on usernames, anyone human or not, could name their account something_bot. We could establish a convention that bots should have specific usernames, but that would be hard to enforce as community-created automations show up.

Yeah I'm not exactly sure what triggers it, but you can see the `bot` flag in a user extract:

{
  "id": 24510,
  "username": "longwave",
  "name": "Dave Long",
  "state": "active",
  "locked": false,
  "avatar_url": "https://git.drupalcode.org/uploads/-/system/user/avatar/24510/picture-246492-1701276520.jpg",
  "web_url": "https://git.drupalcode.org/longwave",
  "created_at": "2018-12-11T21:35:54.623Z",
  "bio": "",
  "location": "UK",
  "public_email": "",
  "skype": "",
  "linkedin": "",
  "twitter": "",
  "discord": "",
  "website_url": "https://www.drupal.org/u/longwave",
  "organization": "",
  "job_title": "",
  "pronouns": "he/him",
  "bot": false,
  "work_information": null,
  "followers": 0,
  "following": 0,
  "is_followed": false,
  "local_time": null
}

This flag seems to also be tied to the inverse `humans` and `exclude_humans` filter on list endpoints https://docs.gitlab.com/ee/api/users.html#for-non-administrator-users

-

Surely the bot flag is not powered by a username suffix?

Just above https://docs.gitlab.com/ee/api/users.html#for-administrators explains a bit more about the “bot”-related conditions. These are 2 types of internal users that GitLab creates. I expect they are mostly maintained for GitLab’s per-seat pricing plans.

I don’t see any way to update this property in the user modification API https://docs.gitlab.com/ee/api/users.html#user-modification

The regular accounts created for bots can’t use GitLab internals to be anything else. So I think this is by design, unless GitLab introduces user-created bot labeling, or we want to establish some community norms we encourage people to follow.