vm
Report information
Repositories: 0Activity
| Commits | Issues | Reviews | |
|---|---|---|---|
| Total | |||
| Total (Last year) | |||
| Year-over-year | % | % | % |
Number of commits
Number of commits is the most common measure of activity in a git repository. To compute it, we're considering all commits in all branches of all repositories in the report, excluding empty commits. Each commit represents a change to the source code, maybe touching several files. However, commits may be very different in size, complexity and usefulness to the report, so this number should only be considered as an indicator, among others.
Read moreCommunity
| Commit authors | Issue submitters | Review submitters | |
|---|---|---|---|
| Total | |||
| Total (Last year) | |||
| Year-over-year | % | % | % |
Number of authors
Number of authors gives an idea of the size of the active community for a report. In this case, we're measuring, for each week in the chart, the number of different identities that authored at least one commit, or that submitted issues or reviews (pull or merge requests) to any repository of the report during that week. Although this is usually a good indicator of people who are active in the project, it is important to notice that, during any given week, active developers may be busy with some other stuff, thus not appearing in this chart. Also, casual contributors (such as somebody submitting a bug report but not really engaged with the project) appear in the chart. People taking care of important tasks, such as writing documentation, may also be reflected in this chart, or not, depending on the repositories included in the report, and how the project deals with those tasks.
Read morePerformance
| Issues | Reviews | |
|---|---|---|
| Median time to close | days | days |
| Median time to close (Last year) | days | days |
| Year-over-year | % | % |
The following table shows all the commits, issues, reviews and its corresponding number of authors/submitters for all the history of each repository.
Mean and median duration (days) of all closed reviews
This heat map compares the responsiveness of a repository to reviews (pull requests and merge requests). The light blue indicates review response times that are fastest; the red indicates the time slots with slowest response times. White boxes indicate time slots in which no reviews were closed. The minimum and maximum are determined by the pool of repositories within the report. For GitHub repositories, both accepted and declined pull requests are taking into account. For GitLab repositories, only the declined are being shown.
Metric inspired by the 
report, and 
# Issues created/closed
Number of issues shows activity in the issue tracking system, usually including bug reports, feature requests, and other tasks that are tracked with issues (tickets). We measure, for each week, the number of issues that were opened (created) or closed during it. Not only the absolute numbers, but also the relationship between open and closed issues is important in this chart: if many more issues are consistently being opened than closed, the report is not dealing with all the new stuff that is entering the issue tracking system.
Read moreDrive-through and repeat contributor counts
This graph shows the number of new contributors in the specified time period and indicates how may were drive-through or repeat contributors. Drive-through contributors are contributors who make less than the required 5 contributions in the specified time period. Repeat contributors are contributors who made 5 or more contributions in the specified time period and their first contribution is in the specified time period.
Metric inspired by the report, and
# Commits by hour and weekday
The heatmap shows what times of day contributors in their local time zone contribute. Activity that clusters between regular office hours on workdays can indicate activity by contributors who do this as part of their job. Activity during evenings and weekends can indicate volunteer activity.
Read more