Dataset: Commits from pull requests
Entity: Commit
Field ID: author_type
Type: Select list
Description: The type of the author of the commit. Possible values are:
PERSONa person.BOTa 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.TEAMa 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 commits written by people and teams, without naming each bot. A commit 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,_botor.botis a bot as well.
A commit not linked to an account is typed from Keypup's list only. GitLab always identifies a commit's author by their git email, and GitHub and Azure DevOps do so when the commit cannot be matched to an account. The application then gives no account type, so the commit is a PERSON unless its author's name matches Keypup's list.
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 (Commits) | The account type GitHub gives: a user is |
GitLab (Commits) | The account's bot flag: project and group access token users and service accounts are |
Bitbucket (Commits) | The account type: app users (Cloud) and service accounts (Data Center) are |
Azure DevOps (Commits) | The identity type: service principals and service identities (such as the build service) are |
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.
Code volume written by people: filter on
author_type != "BOT"to keep commits pushed by dependency updaters, formatters or coding agents out of lines added and deleted.Commits from coding agents: filter on
author_type == "BOT"and group byauthor_usernameto see which agents and automations push code, and how much.
