Commit Risk data shows the tendency of pushing risky codes by the team and each developer to identify at least one of the parts team members can improve.
Commit risk is calculated by considering;
- The size of the commit in terms of the number of line changes
- Whether the changes are distributed or in the same area
- The AI trained by the data set we collected through years of coding experience
To follow the best practices and reduce the time spent in the development process we suggest you follow this metric closely.
The categories of the commit risk are as the following;
Risky commits can cause a longer process to evaluate, review, test flows and in case of any failure to detect commit-related issues, serious defects can occur in the production.
Our recommendation is to reduce risky commits and take extra care in the review and test processes to avoid such cases.