← Reference · Nestor G Pestelos Jr · Print this page

Software Engineering · Collaboration

Pull Requests

Reference entry · last updated 20260908

A pull request (PR) proposes merging changes from one branch into another. It brings the proposed changes, discussion, reviews, and automated checks into one place.[1]

First principles and definitions

The head branch supplies the proposed changes; the base branch is their destination. A diff shows the changes between the compared versions. A commit records a version of the work. Opening a PR proposes integration; merging performs it.

Review and checks

A PR can collect reviewer comments and test results before integration. Repository rules determine which approvals and checks are required. An open PR is not evidence that anyone has reviewed it.[1]

Size and measurement

Focused changes and a clear description help reviewers assess purpose and behavior.[2] PR count alone does not measure delivered value: changes differ in size and scope. Review duration also needs a defined start and end event before teams compare it.

See also

• Acceleration Whiplash
• Code Review
• Software Quality Assurance
• Queueing Theory for Software Delivery

References

1. GitHub Docs. About pull requests.
2. Google Engineering Practices. Small CLs.