Code Velocity tab provides various insights related to the code that has been submitted by various contributors to the various open source project.
Code Velocity tab provides insights on the following:
Commit Analysis
Pull Request Pipeline
Issue Request Pipeline
To access Code Velocity, perform the following steps:
1.Login to Insights.
2.On the vertical sidebar navigation menu, click Code Velocity.
Pull Request (PR) Pipeline provides various insights related to the PRs carried out for the open source project. Pull Request Pipeline provides various graphs that provides you information on PRs analysis. There are various graphs such as:
Pull Request History
Request Pipeline
Cycle Time
Pull Request Trends
Contributor Type
Active Submitters
Time to Merge
Time in Review
New Contributor Efficiency
Top 10 Contributors
Top 10 Organizations
You can filter the data related to PR as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter the PRs using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This line graph provides the count of the total number of PRs submitted and merged aggregated for all time over the selected time period.
Observations window provides various observations carried out on the Pull Request Pipeline. Some of the observations that are displayed are listed in the following list:
The total number of PRs submitted increased/decreased by X% during the ${selected time period}.
An average of X PRs were merged during the ${selected time period}.
The total number of PRs merged increased/decreased by X% during the ${selected time period}.
X% of total changes were merged without any approval during the last ${selected time period}.
This funnel chart provides you the total number of code change requests in the form of PRs or changesets submitted, reviewed, accepted and merged during the selected time period.
GitHub's accepted/approved state configured differently for every repository. This "Approved" metric is counted based on at least one review with "Accepted state".
Submitted - Number of PRs created/submitted during the given time range + the number of PRs still in open at the end of the time period.
Reviewed - Number of PRs with at least one Review (comment or approval or requested changes). The review must be done during the selected time period.
Accepted - Number of PRs with at least one approval. The approval must be done during the selected time period.
Merged - Number of PRs merged (not rejected).
For Gerrit:
Submitted - Number of Changesets created/submitted the given time range + number of changesets still in open
Reviewed - Number of chanegstes with at least one Review (comment or review value +1, +2, -1, -2)
Accepted - Number of changesets with at least one approval (review value +1, +2)
Merged - Number of changesets merged/closed (not -2)
This funnel chart provides you the sum of the average time it takes in each step of the PR/changeset cycle.
The annotation block shows the total Average PR Cycle time i.e. the sum of the averages for each stage. It also shows the percentage change compared to previous period.
Waiting for Review - Shows the average of the time between a PR is submitted/created and time to get the first review_comment or review_approval or review_requested_chages for all PRs merged or closed during the selected time period.
In Review - Shows the average of the time a PR received its first review to the time a PR received its first approval for all the PRs merged or closed during the selected time period.
In Approval - Shows the average of the time a PR received its first approval to the time a PR was merged or closed for all the PRs merged or closed during the selected time period.
This bar graph provides the count of the total number of PRs submitted and merged during the selected time period.
This donut chart provides the analysis of code change request contributors by reviewers and submitters.
Total PR contributors are unique identities who are PR submitters, PR reviewers (review_comment, review_requested_changes, review_approval) and PR mergers.
PR submitters are strictly those who have submitted at least 1 PR during the selected time period.
PR reviewers are strictly those (can be submitters as well) who have reviewed at least one PR during the selected time period.
This bar graph provides you the count of the total number of unique PR submitters analyzed by cohorts of existing and new submitters contributing during the selected time period.
New PR Submitters are also Active.
New submitters are strictly those identities or profiles who have submitted PR for the first time for the project.
This line chart provides you the average time, in days, it takes for a PR to be merged during the selected time period.
This line graph provides you the average time in days required for pull request to be reviewed during the selected time period.
This line graph provides the average time it takes for the first PR submitted by a new contributor to be accepted and merged.
The Lead time will either be higher or at least same as the time in Review
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the PRs submitted on the project.
This list provides various details such as:
Name
Identity
Organization
Last activity
PRs submitted
PRs reviewed
PRs merged
PR comments
You can order the list based on PRs submitted, reviewed, merged and comments.
On Click of All Technical Contributors, all the technical contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the PRs submitted on the project.
This list provides various details such as:
Organization name
Contributors
Last activity
PRs submitted
PRs reviewed
PRs merged
PR comments
You can order the list based on PRs submitted, reviewed, merged and comments.
You can download all the charts that are displayed in the PR Pipeline page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
Issue Request Pipeline provides various insights related to issues raised and resolved for the open source project. Issue Request Pipeline provides various graphs that provides you information on issues. There are various graphs such as:
Issue History
Resolution Pipeline
New Issues
Backlog
Contributor Type
New Contributors
Average Time To Resolve
Issue Resolution Efficiency
Efficiency
Top 10 Contributors
Top 10 Organizations
You can filter the data related to issues as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter the issues using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This bar graph provides the aggregate number of submitted and resolved issues.
Since this is the aggregated count, the count will never go down.
Observations window provides various observations carried out on the Issue Request Pipeline. Some of the observations that are displayed are listed in the following list:
The number of issues submitted increased by X% during the ${selected time period}. /* If the %increase is 0, the observation should say, No new issues were submitted during the ${selected time period}.
An average of X issues were submitted submitted during the ${selected time period}.
The number of issues resolved increased by X% during the ${selected time period}. /* If the %increase is 0, the observation should say, No new issues were resolved during the ${selected time period}.
An average of X issues were resolved during the ${selected time period}.
The highest growth in the number of issues submitted was seen between X-Y.
Most number of issues were closed during the time period between X-Y.
This funnel chart provides you the issue resolution pipeline showing bottlenecks and key data points such as issues waiting to be closed, commits pushed, pull requests submitted and more.
This bar graph provides you the trend of new issues submitted and resolved in a particular time frame.
This line chart provides you the breakdown of issues that are in development and those that are still open.
This line chart provides you the count of the total number of submitters and assignees over the selected time period.
This line chart provides you the count of the total number of new submitters and new assignees over the selected time period.
This line chart provides you the average time, in days, it takes for the issues to be closed or resolved during the selected time period.
This radar chart provides you the analysis of number of issues resolved by measuring their time to resolve into cohorts of different time periods which is less than a day, between 1-7 days, between 7-15 days, 15-30 days and more than 30 days.
This line chart provides you the average time in days required before initial comment made on a submitted issues and the time to assign the issue.
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the issues submitted on the project.
This list provides various details such as:
Display Name
System Username
Organization Name
Last activity
Issues submitted
Issues Assigned
Issue comments
You can order the list based on issues submitted, assigned and and comments.
On Click of Active Contributor Leaderboard, all the active contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the issues submitted on the project.
This list provides various details such as:
Organization name
Organization logo
Industry
Active Issues Contributions
Issues submitted
Issues Assigned
Issue comments
You can order the list based on Issue submitted, assigned and comments.
Commit Analysis provides various insights related to the commits carried out for the open source project. Commit Analysis provides various graphs that provides you information on commit analysis. There are various graphs such as:
Total number of commits
Commit Trends
Contributors / Organization
Code Changes
Documentation
Pair Programing Commits
Code by Day
Programming Languages
Commit-To- Merge Time
Top 10 Contributors
Top 10 Organizations
You can filter the data related to commit analysis as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter the commit analysis using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This line graph provides the count of the total number of commits aggregated since the start of the project analyzed over the selected time period.
Observations window provides various observations carried out on the commit analysis. Some of the observations that are displayed are listed in the following list:
The percentage change in the number of commits increased/decreased during the selected time period.
The most number of commits submitted was the highest during X-Y period.
For computing the average commits, only the unique commits submitted during the selected time period should be considered and averaged out based on the data points (buckets) on the graph.
This bar graph provides the total number of commits performed during the selected time period. Hover over the bar to see the total commits for that particular months. The annotation block show the total commits for the selected period and the rate of change compared to previous time period.
This bar graph provides the total number of number of unique contributors actively committing code to the project during the selected time period.
On click of View Contributors, you can view the list of people contributing to the project. For more, refer People.
This bar graph provides the total number of number of unique organizations actively committing code to the project during the selected time period.
This line graph provides the count of the total number of commits pushed and analyzed by those containing actual lines of code changes vs those that are empty or identified as merge commits.
This donut chart provides you the total number of commits that are intended to update documentation or assets like images for the project.
This line graph provides the total count of the number of commits signed-off by more than one author.
Pair Programming are enabled by default and are identified by the parsing the git trailers for more than one Author, generally given by 'Co-Authored' or 'Signed-off by' trailers.
A co-author should be different that the actual author of the commit, hence pair programming commits should be not identified by merely looking at multiple occurrences of the git trailers and rather by also checking the authors and co-authors involved in the commit and tag a commit as pair programming commit only if both are different individuals.
This radar chart provides you the total commits submitted and aggregated across each day of the week.
The aggregation applies to only commits submitted during the selected time period.
Only commits authored or co-authored are considered.
This bubble chart provides you the total number of programming languages used across the commits submitted and determined by analyzing the files (checking the extensions) modified or added for each commit.
If a file type cannot be determined, it is marked as 'Unknown'.
This speedometer chart provides you the average time, in days, for a commit to be committed to a branch. For each commit, the efficiency is computed by taking the difference between the time it was added and the time it was committed.
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the commits submitted on the project.
This list provides various details such as:
Display name
System name
Organization name
Last activity
Commits authored
Commits co-authored
LOC added
LOC deleted
Files modified
You can order the list based on commits authored, commits co-authored, LOC added, LOC deleted and Files modified.
On Click of View All, all the contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the commits submitted on the project.
This list provides various details such as:
Organization name
Organization Logo
Contributors
Last activity
Commits authored
Commits co-authored
LOC added
LOC deleted
Files modified
You can order the list based on commits authored, commits co-authored, LOC added, LOC deleted and Files modified.
You can download all the charts that are displayed in the issues Pipeline page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
You can download all the charts that are displayed in the Commit Analysis page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.