Commits Per Active Day
The Commits per Active Day Dashboard provides insights into code commit frequency on active development days. It measures the average number of code commits contributors to make on active development days.
Analyze the chart
To calculate the Commits Per Active Day metric:
Identify Active Days: Count the number of days within a specified period where at least one commit was made.
Count Total Commits: Sum the total number of commits made within that period.
Calculate Average: Divide the total number of commits by the number of active days.
For example, if in a month there are 300 commits made over 20 active days, the Commits Per Active Day would be:
Commits Per Active Day = 300/15 = 20 days
This means, on average, there were 15 commits made on each day that had at least one commit.
Why is this important?
Early Issue Detection: A higher number of commits per active day increases the likelihood of early issue detection. Regular code commits to provide more opportunities for contributors to identify potential issues or bugs during the development process.
Code Quality and Stability: A consistent number of commits indicates ongoing code enhancements and maintenance, leading to improved code quality over time.
Productivity Assessment: A higher number of commits per active day suggests that contributors are actively working on code changes, implementing new features, fixing bugs, and making improvements.
Last updated
