Skip to main content

Activity Events > Author type

Written by Arnaud Lachaume

Dataset: Activity Events

Entity: Activity Events

Field ID: author_type

Type: Select list

Description: The type of the author of the event. Possible values are:

  • PERSON a person.

  • BOT a bot or an app: a known review, CI or automation bot (e.g. CodeRabbit, Dependabot, GitHub Actions), or an account the application itself flags as a bot.

  • TEAM a team or group, such as a team requested as reviewer. Rare as an author.

Leave bots out with one filter. author_type != "BOT" keeps the events written by people and teams, without naming each bot. A event whose author is unknown has an empty author type, and this filter leaves it out too.

Source: Calculated

Transformation logic: Keypup types every account from two sources, and an account is a BOT when either says so:

  • The application's own account type, where the application gives one: see the App Mapping below. Otherwise the account is a PERSON.

  • A list of known bots maintained by Keypup, kept per application so that a name that is a bot on one application can be a person on another. It covers AI code reviewers and coding agents, code quality and security scanners, dependency updaters, CI and deployment services, and the automation apps of work trackers: CodeRabbit and Sonarcloud on Azure DevOps, or Automation for Jira, for example. On every application, an account whose name ends in [bot], -bot, _bot or .bot is a bot as well.

A bot of your own counts as a person unless its name says otherwise. The list holds products used across many teams, not a team's own release, CI or sync accounts. Name such an account with a bot suffix, e.g. release-bot or PR [bot], and it is typed BOT. If a product bot is shown as a PERSON, contact support and we will add it to the list for everyone.

App Mapping

GitHub (Timeline Items)

The account type GitHub gives: a user is PERSON, an app (such as dependabot or github-actions) is BOT, a team is TEAM.

GitLab (Discussions, State Events)

The account's bot flag: project and group access token users and service accounts are BOT.

Bitbucket (Activity)

The account type: app users (Cloud) and service accounts (Data Center) are BOT, team accounts are TEAM.

Azure DevOps (PR Threads, Issue Updates)

The identity type: service principals and service identities (such as the build service) are BOT, groups are TEAM. Review and analysis tools that sign in as ordinary accounts, such as CodeRabbit and Sonarcloud, are BOT through Keypup's list.

Jira (Changelog, Worklog)

The account type: apps (such as Automation for Jira, or a sync app) are BOT, Atlassian accounts and service desk customers are PERSON.

ClickUp (Issue timestamps)

Calculated: Keypup's list only, ClickUp gives no account type.

Trello (Actions)

Calculated: Keypup's list only, Trello gives no account type.

Reporting Use Cases

The author_type field separates the work of people from the work of automation. As a select list, it is mostly used as a filter, and sometimes as a dimension.

  • Activity by people only: automation apps move issues between statuses, assign reviewers and add labels. Filter on author_type != "BOT" to keep those events out of an activity feed or a contributor report.

  • What automation does: filter on author_type == "BOT" with action as the dimension to see which transitions your bots and workflow automations perform.

Did this answer your question?