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.
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 →
Related concepts
- code reviewused by · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
- GitHubused by · GitHub is a web-based platform for hosting Git repositories and supporting collaborative software development.
- preview environmentused by · A preview environment is a temporary, nonproduction deployment context for evaluating or testing a proposed software change before release.
- deployment pipelineproduced by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
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.