We’ve refined our algorithm for Code Review Cycles to provide a clearer signal on the back-and-forth context switches between authors and reviewers. 

With the rise of AI code review tools, developers should not see their metrics negatively impacted for using modern tools that help them improve code quality before human review. For this reason, we’ve made an update to exclude reviews from bots from the calculation.

We’ve made several other refinements, such as excluding reviews and comments by the pull request’s author, reviews that happen before a pull request is marked as ready for review (i.e., taken out of "Draft" status), and reviews from open source contributors.

With these changes, you may see a decrease in the Review Cycles reported for some pull requests. This adjustment applies historically, ensuring that your trends remain consistent while improving the overall accuracy of the metric. The result is a more precise and actionable measure for understanding and improving review efficiency.

You can learn more about how we calculate Review Cycles in our updated documentation. If you have any questions, please reach out to us at support@software.com.