Risk is a measure of how likely it is a particular commit will cause problems. Think of this as a pattern-matching engine, where Waydev is looking for anomalies that might cause problems.

Here are some of the questions we ask when looking at risk:

How big is this commit? Are the changes tightly grouped or spread throughout the code base? How serious are the edits being made — are they trivial edits or deeper, more severe changes to existing code?

Risk helps teams put their attention where it’s most needed. This not only helps with quality control, but serves an incredible tool for building engineering talent: by concentrating review on outlier commits, engineers receive high-quality feedback and suggestions for improvement where it’s needed most.

Did this answer your question?