The Self-reviewed pull requests graph displays integrated code reviews that have bypassed the standard review process, i.e., have not been validated by a team member other than the author.
You can view this data by day, week, or month. Please note that the display of the last six months or the last year does not allow the display by day.
Psst! This graph is handy to identify automation that approves certain reviews, such as bots.
Example of use
For the following graph, the period displayed corresponds to the last 3 months, and the display mode is per week. Although the graph shows an average of 1.5 self-reviewed and integrated code reviews per week, we can see an increase in February to reach a total of 2 self-reviewed pull requests. The trend (red dotted line) is therefore upward for the current period.
Since this graph is interactive, hovering over it with your mouse will display more details for a given week (depending on the display mode selected).
These self-reviewed pull requests increase the risk of introducing bugs and technical debt, as other team members did not validate them. As much as possible, teams should aim to avoid merging pull requests without a review. Maintaining a low number of self-reviewed pull requests will likely result in a better delivery pipeline, quality, and team collaboration.
To learn more about the variation indicator and its calculation, check out this article!