Commit Frequency

Measures development activity over the last 30 days.

Methodology

What We Look For

Active development indicated by regular commits to the codebase.

Evaluation Criteria:

• Total commits across all repositories in last 30 days
• Excludes bot commits (dependabot, renovate, etc.)
• Excludes merge commits with minimal changes
• Counts only substantive code commits

Data Sources:

• GitHub API - Commits
• GitHub commit history

Scoring Approach

Higher commit frequency indicates:

• Active development
• Team is shipping regularly
• Product is being improved
• Technical health

Guide

Finding Information

Step 1: Access Your GitHub Organization

Navigate to your GitHub organization page and identify all active repositories.

Step 2: Calculate Total Commits

Sum commits across all repositories in the last 30 days. You can:

• Use GitHub API
• Check each repository's commit history
• Use GitHub Insights (if available)

Step 3: Apply Filters

Exclude:

• Bot commits (dependabot, renovate, etc.)
• Merge commits with no code changes
• Commits that only update documentation without code
• Automated dependency updates

Include:

• Feature commits
• Bug fix commits
• Refactoring commits
• Test commits
• Documentation commits with code changes

Submitting Evidence

When submitting commit frequency:

1. Repository URLs: Links to all active repositories

2. Commit Count: Total commits in last 30 days

3. Calculation: How you arrived at the number (if not obvious)

4. Special Circumstances: Any factors affecting commit count (e.g., private repos, monorepo structure)