Keypup

Dataset: Commits from pull requests

Field ID: <code>author_username</code>

Description: The username of the person who created the commits. Note that usernames are app-specific.

The <code>Author</code> field from the Commits dataset is the definitive attribute for identifying who wrote a specific piece of code. It is essential for analyzing individual contribution patterns, tracking workload at the code level, and filtering out automated activity.

Filtering and Scoping: You can create highly focused reports by including or excluding commits from specific authors.

- Individual Contribution Reports: To analyze the work of a single developer, you can apply a filter like <code>Author = "john.doe"</code>.
- Exclude Bot Commits: A crucial use case is to clean your data by removing automated commits (e.g., from dependency updates). You can do this with a filter like <code>Author !~ "bot"</code>.
- Personal Dashboards: Use the is me operator to create a widget that shows all the commits you have personally authored.

Reporting on Contribution Patterns: Using <code>Author</code> as a dimension is the primary way to visualize who is contributing code and where.

- Commits per Developer: A bar chart with <code>Author</code> as the dimension and <code>COUNT()</code> as the metric will show the total number of commits per person.
- Work Distribution: A heatmap with <code>Author</code> as one dimension and <code>Project</code> as the other can reveal which developers are the primary contributors to which repositories, helping you identify code ownership and knowledge silos.

Creating Advanced KPIs: You can use this field within aggregations to measure the breadth of your team's contributions.

- Active Contributor Count: A KPI with the custom formula <code>COUNT_DISTINCT(author_username)</code> will tell you the number of unique developers who have committed code in a given period, which is a great way to measure team engagement.

- Filtering and Scoping: You can create highly focused reports by including or excluding commits from specific authors.
 - Individual Contribution Reports: To analyze the work of a single developer, you can apply a filter like <code>Author = "john.doe"</code>.
 - Exclude Bot Commits: A crucial use case is to clean your data by removing automated commits (e.g., from dependency updates). You can do this with a filter like <code>Author !~ "bot"</code>.
 - Personal Dashboards: Use the is me operator to create a widget that shows all the commits you have personally authored.
- Reporting on Contribution Patterns: Using <code>Author</code> as a dimension is the primary way to visualize who is contributing code and where.
 - Commits per Developer: A bar chart with <code>Author</code> as the dimension and <code>COUNT()</code> as the metric will show the total number of commits per person.
 - Work Distribution: A heatmap with <code>Author</code> as one dimension and <code>Project</code> as the other can reveal which developers are the primary contributors to which repositories, helping you identify code ownership and knowledge silos.
- Creating Advanced KPIs: You can use this field within aggregations to measure the breadth of your team's contributions.
 - Active Contributor Count: A KPI with the custom formula <code>COUNT_DISTINCT(author_username)</code> will tell you the number of unique developers who have committed code in a given period, which is a great way to measure team engagement.

Commits > Author

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (Commits)	`author`
Gitlab (Commits)	`author`
Bitbucket (Commits)	`author`
Azure DevOps (Commits)	`author` ADO does not attach commits to ADO users. Only a name and email are available. A user lookup is performed to retrieve the user based on the author's email address, but this match only works if the commit author's email in git is the same as the ADO user's email. If no match is found, the commit user will be attached to a generic user built based on their name and email address.
Jira	N/A
ClickUp	N/A
Trello	N/A

Commits > Author

Reporting Use Cases