The Pull requests size graph displays the average number of files changed per code review, for the selected period. You can display this data by day, week, month, or by sprint, depending on your preference. However, note that if a Kanban-type board has been linked to your Axify project, the "sprint" option will not be available in the filters at the top of the page. In addition, the periods "last 6 months" and "last year" do not allow the display by day.
Reading the graph
For the following graph, the period displayed corresponds to the last three months, and the display mode is by week. On average, we can see that 10,6 files are changed per PRs, per week.
This graph also includes a variation indicator, which compares the average number of files changed per PR for the current period to the average number for the previous period. To learn more about the variation indicator and its calculation, check out this article!
Psst! Larger pull requests tend to have fewer comments and have less thorough reviews, thus potentially decreasing code quality and introducing more problems or bugs. It is also possible to see an impact of larger PRs on the time to take reviews. Better slicing and attention to the volume of files changed can be interesting options to improve your cycle time or your DORA metrics!
Calculating the metric
The number of code reviews (PRs) merged for the current period as well as the number of files changed for each of these PRs, each week or each sprint depending on the display, are used to calculate an average for the week or the sprint concerned. Then, the average score visible at the top of the graph is an average of the weekly or sprint averages.