Commit Delivery Reporting

Helm ADE provides roll-up commit visibility summaries so you can monitor engineering throughput by Project, Component, PRD, and Task hierarchy. This helps org admins understand delivery patterns and identify areas needing attention.

Overview

Commit delivery reporting gives you insights into:

• Commit volume trends over configurable time periods
• Contributor activity and top contributors
• Linkage rates showing how many commits are connected to work items
• Stale projects that haven't received commits recently
• Code churn via additions/deletions metrics

Accessing Delivery Reports

From the Project Commits Page

Navigate to a project's Commits page

Click the Reports tab

View project-specific delivery metrics

Organization-Wide Reports

For org-level insights:

Navigate to Organization Settings

Select Engineering Insights or access via API

View aggregate metrics across all projects

Required Permissions

Action	Required Role
View delivery reports	viewer or higher
Configure report parameters	admin or higher

Understanding the Dashboard

Summary Statistics

The top of the report shows key metrics:

Metric	Description
Total Commits	Number of commits in the selected period
Contributors	Unique authors who committed
Linkage Rate	Percentage of commits linked to artifacts
Stale Projects	Projects with no recent commits

Date Range Selection

Filter the report by date range:

Select the start date

Select the end date

The report updates to reflect the selected period

Default view shows the last 30 days.

Stale Threshold

Configure what counts as "stale":

• 7 days - Aggressive monitoring
• 14 days - Standard threshold (default)
• 30 days - Relaxed monitoring

Projects without commits for longer than this threshold appear in the stale list.

Code Changes Section

This section shows aggregate code metrics:

• Files Changed - Total files modified
• Additions - Total lines added
• Deletions - Total lines removed

These metrics help understand code churn and development velocity.

Top Contributors

See who's been most active:

Rank - Position by commit count

Name - Contributor's name

Commit Count - Number of commits

Use this to:

• Recognize active contributors
• Identify workload distribution
• Spot potential knowledge silos

Stale Projects

Projects appearing in this section haven't had commits recently.

What Makes a Project Stale?

A project is stale when:

• No commits exist for the project, OR
• The most recent commit is older than the stale threshold

Interpreting Stale Projects

Stale projects might indicate:

• Completed projects that are in maintenance mode
• Blocked work that needs attention
• Projects that should be archived
• Resource allocation issues

Taking Action

For each stale project, consider:

Is this project still active?

Are there blockers preventing commits?

Should resources be reallocated?

Should the project be archived?

Volume Trends Chart

The trend chart visualizes commit activity over time.

Reading the Chart

• X-axis - Date (day by day)
• Y-axis - Number of commits
• Blue bars - Linked commits
• Gray bars - Unlinked commits

Interpreting Trends

Pattern	Possible Meaning
Consistent activity	Healthy, steady development
Spikes	Release preparation or feature completion
Valleys	Holidays, blockers, or planning phases
Declining	Possible issues or project completion
Increasing	Growing momentum or team expansion

Linked vs Unlinked

The chart distinguishes between:

• Linked commits - Associated with PRDs, Tasks, or Components
• Unlinked commits - No artifact association

A high ratio of unlinked commits may indicate:

• Inconsistent commit message patterns
• Need for triage of existing commits
• Commits for non-tracked work (infra, tooling, etc.)

Commit Hierarchy Breakdown

Reports show commit distribution by:

By Project

How commits are distributed across projects in your organization.

By Component

Which system components receive the most development attention.

By PRD

Which product requirements are actively being implemented.

By Task

Which specific tasks are generating commits.

Using Reports for Planning

Sprint Planning

Review reports before sprint planning to:

• Identify velocity trends
• Spot bottlenecks
• Allocate resources effectively

Retrospectives

Use reports during retrospectives to:

• Discuss delivery patterns
• Celebrate contributions
• Identify process improvements

Stakeholder Updates

Generate reports for stakeholders to:

• Show development progress
• Demonstrate work linked to requirements
• Highlight active projects

AI Tool Integration

Reports are also accessible via AI tools for automated insights.

get_commit_delivery_summary

This AI tool provides:

• Summary statistics
• Top projects by commits
• Top contributors
• Stale project list

Use this in automation or chatbot contexts for quick insights.

Exporting Data

While the UI provides visualization, underlying data is available via API:

GET /api/orgs/{orgId}/commits/report

Parameters:

• startDate - YYYY-MM-DD
• endDate - YYYY-MM-DD
• projectId - Optional, filter to specific project
• periodType - daily, weekly, or monthly
• staleThresholdDays - Number of days for stale detection

Best Practices

Regular Reviews

• Check delivery reports weekly or bi-weekly
• Review stale projects monthly
• Track linkage rate trends over time

Improving Linkage Rates

• Train teams on commit message conventions
• Use auto-linking patterns in commit messages
• Schedule regular triage sessions

Acting on Stale Projects

• Create a review process for stale alerts
• Don't ignore stale projects indefinitely
• Archive completed projects to clean up lists

Troubleshooting

Report shows zero commits

Check that:

• GitHub sync is enabled and working
• Date range includes expected activity
• Project has been set up correctly

Stale projects seem incorrect

Verify:

• Sync is up to date
• Commits are going to the tracked branch
• Project ID mapping is correct

Contributors not showing correctly

This can happen when:

• Different email addresses are used
• Git config varies between machines
• GitHub user isn't linked to Helm account

Related Topics

• Project Commit Timeline - View individual commits
• Organization and Project Switching - Navigate between projects