What is
...
Pull Request Size?
Pull Request Size is a measure of the size of pull requests including the number of lines changed within each file.
Why
...
does Pull Request Size matter?
Code reviews are an important part of the software development lifecycle because they provide the ability for code written by team members to be peer reviewed and assured for quality before the code is merged from branch into master. Reviewing pull requests can also be one of the most time consuming activities of a team’s software development process.
Making smaller pull requests is the best way to speed up time spent reviewing your peer’s work. By applying the discipline to break down pull requests into smaller, manageable batches of code, it’s much quicker for reviewers to understand the context and reason with the logic and detect defects that need remediation.
What does ‘good’ Pull Request Size looks like?
Small pull requests are easier to review, making it more likely for code to be thoroughly reviewed before approval. It helps to speed up the review, reduces risk of introducing bugs into the codebase, helps not block other developments and speeds up the product development process.
...
Large pull requests tend to be glazed over and rubber stamped, limiting the effectiveness of defect detection.
How Umano measures
...
Pull Request Size
Umano measures Size of Pull Request through:
Number of files changed
Number of lines added and/or removed
Practices that influence
...
Pull Request Size
Number of lines
Number of lines added
Number of lines removed
Number of issues addressed in a PR
...
Included | Not included |
|---|---|
All Pull Requests in selected repositories | x |
Tips for improving
...
Pull Request Size
| Tip |
|---|
Code reviews in reasonable quantity, at a slower pace for a limited amount of time results in the most effective code review |
...