Pull request
A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
"Looks Good to Me"
A pull request, also called a merge request, is a proposal to integrate code changes into a target codebase or branch while supporting review, discussion, and approval.
- How it is used
- Uses a Git-based mechanism to organize code inspection, discussion, feedback, and approval before integrating changes.
- How deep it goes
- Explains the workflow, preparation practices, size guidance, approval rules, and process refinement, while deferring tool-specific implementation details.
- Examples
- Uses an invoice-parser failure, PR templates, automated checks, labels, review states, and smaller PRs as concrete teaching examples.
- What you can do after
- Operate a PR-centered review workflow and prepare changes that reviewers can understand, discuss, evaluate, and approve.
Platform Engineering on Kubernetes
A pull request is a source-control request for other developers or automation to review and merge a proposed change into a target branch.
- How it is used
- Coordinates code review, branch validation, merging, and automated promotion across service and environment repositories.
- How deep it goes
- Explains pull requests through branch, pipeline, artifact, and environment flows without detailing platform-specific configuration.
- Examples
- Uses GitHub pull requests for feature validation and automated requests that promote service versions through environment repositories.
- What you can do after
- Operate pull-request workflows that validate changes before merging and promote tested releases through increasingly sensitive environments.
Read how Platform Engineering on Kubernetes explains pull request →
GitHub Actions in Action: Continuous integration and delivery for DevOps
A pull request is a proposal to review and integrate changes from one repository branch or repository into another.
- How it is used
- Gates feature-branch changes before merging them into main and triggering downstream delivery workflows.
- How deep it goes
- Explains the PR workflow and branch-protection settings, but defers detailed CODEOWNERS configuration.
- Examples
- Uses a feature branch, peer approval, PR-triggered quality checks, and container-image publication as the delivery path.
- What you can do after
- Operate/configure it by requiring approvals and pull requests before merges to the main branch.
Vibe Engineering
A proposed set of repository changes submitted for review and integration into a codebase.
- How it is used
- Uses pull requests to isolate migration changes, expose risks, and obtain human and AI-assisted review before integration.
- How deep it goes
- Explains PR granularity, branch isolation, commit structure, reviewer selection, and AI-assisted checks, but not platform-specific configuration.
- Examples
- Uses a JBoss-to-Spring migration with final, layer-specific, and isolated pull requests as concrete review patterns.
- What you can do after
- Apply it via Git branches and commits to structure migration changes for focused human and AI-assisted review.
Automating API Delivery
A pull request is a proposed change submitted for review and integration into a version-controlled codebase.
- How it is used
- Uses version-controlled API-definition changes as a collaboration, validation, and governance workflow before integration.
- How deep it goes
- Explains workflow states, automated gates, logs, and human review, but does not specify provider-specific commands or configuration.
- Examples
- Uses OpenAPI definition changes, PR discussion interfaces, build statuses and logs, warning reports, labels, and review status boards.
- What you can do after
- Operate/configure a review workflow that exposes proposed API changes, validates them automatically, and routes them for human approval.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A pull request is a repository collaboration request that proposes external changes for review and merging into another branch.
- How it is used
- Coordinates review and controlled merging of feature-based configuration changes.
- How deep it goes
- Explains creation, pushing, review, approval, merging, and branch synchronization, then defers automation to delivery pipelines.
- Examples
- Demonstrates firewall-rule and license updates across TICKET-002, TICKET-005, main, and a remote repository.
- What you can do after
- Apply it via Git to push a branch, request review, merge approved changes, and synchronize another branch with main.
100 SQL Server Mistakes and How to Avoid Them
A pull request is a proposal to review changes from one repository branch and merge them into another branch.
- How it is used
- Coordinates review and merging of changes pushed from a remote branch into the trunk.
- How deep it goes
- Explains the Git-to-GitHub workflow from commit and push through review and merge, while deferring deeper Git and GitHub topics.
- Examples
- Uses the Git Changes window, a remote branch, the Create Pull Request link, and a changed CalculateCampaignSummary procedure.
- What you can do after
- Apply it via GitHub to request contributor review before merging a remote-branch change into the trunk.
Read how 100 SQL Server Mistakes and How to Avoid Them explains pull request →
Also covered in
- Shipping Go: Develop, deliver, discuss, design, and go again
- Practical Automation with PowerShell: Effective scripting from the console to the cloud
- Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
- Spec-Driven DevelopmentIn early access (MEAP)
- Logs and Telemetry
- Authorization in Action
- Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
What to know first
- software testingSoftware testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- branchA branch is an independently evolving line of development in a version-control repository, typically represented by a reference to a sequence of changes or commits.
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- commitA commit is an act or record that finalizes a change or state transition within a system.
Related concepts
- code reviewused by · Code review is the systematic examination of source code or proposed changes to assess correctness, quality, risks, or conformance to requirements or standards.
- GitHubused by · GitHub is a web-based platform for hosting Git repositories and supporting collaborative software development.
- workflowused by · A workflow is an organized sequence of coordinated activities or tasks through which work progresses toward a defined outcome.
Questions about pull request
What is pull request?
A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
Which Manning books explain pull request?
"Looks Good to Me", Platform Engineering on Kubernetes, GitHub Actions in Action: Continuous integration and delivery for DevOps, Vibe Engineering, Automating API Delivery, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform and 100 SQL Server Mistakes and How to Avoid Them.
What should I know before learning pull request?
Manning books that teach pull request usually introduce software testing, branch, deployment pipeline and commit first.
What is pull request a kind of?
Pull request is a kind of code change proposal. A code change proposal is a request or plan to modify source code before the modifications are incorporated into a larger codebase.
What is pull request also called?
Pull request is also called PR, PRs or merge request.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.






