pull request
A request on a hosting service such as GitHub to merge one branch into another, with a page for review, discussion and automated checks.
In more detail
Pull requests are a feature of hosting services such as GitHub, not of Git itself; GitLab calls them merge requests. You push a branch, open the request, reviewers comment on the diff against the merge base, and checks run; when it is approved, the branch is merged. Keeping each one small and about one thing makes it easier to review.
Examples
In AWS: A proposal to merge a set of changes into a repository, where teammates review and discuss them first.Design system pull requests run token builds, axe-core audits and visual comparisons, and add a changeset describing the version bump.gh pr create --title "Add a new button" --body "Closes #42"A reviewer asking "how many distinct values can this label have?" on the pull request prevents cardinality explosions.The course puts a three-question threat model in the pull request description, and runs security gates on pull requests so new high-confidence findings fail before merge.on:
pull_request:In Terraform: For infrastructure as code the pull request is where a change is reviewed before anything is applied. Pipelines usually run format checks, validation, tests and a plan on every pull request and post the results. Some teams even create a short-lived environment per pull request and destroy it afterwards.In this course: Make gate results visible in the pull request so the reviewer spends attention on the change rather than asking whether the checks ran. Reviewers comment on its diff, and required checks must pass before it can be merged.Related terms
- pull_request — The workflow event that fires when a pull request is opened or updated, running the contributor's code with no secrets and a read-only token.
- required status check — A check, such as a CI job, that must pass on a pull request before branch protection allows it to merge.
- code review — A teammate reading a proposed change before it is merged, to understand it, catch mistakes and share knowledge.
- fork — A copy of someone else's repository made on a hosting service such as GitHub, under your own account, so you can push to it.
- repository — A project folder whose full history is tracked by version control; in Git, your files plus the hidden .git directory that stores every commit.
- terraform plan — The command that compares configuration, state and reality and prints the actions needed to make them match, without changing anything.
- infrastructure as code — Describing servers, networks and other infrastructure in text files that a tool reads to create and change the real thing.
- CODEOWNERS — A file in a repository that maps paths to the people or teams who must review changes to them.
- status check — A pass or fail result that a pipeline job reports on a commit or pull request, which can be required before merging.
- security gate — An automated check in a pipeline that stops a change going further when it fails, usually by exiting with a non-zero code.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- quality gate — A check, or set of checks, that a change must pass before it can move on, such as being merged or promoted to the next pipeline stage.
- Changesets — A tool where each pull request adds a small Markdown file describing its change and its version bump, later combined into releases and changelogs.
- Git — A free, open-source distributed version control system that records the history of a project as a chain of snapshots.
- branch — In Git, a movable name for one commit; committing on the branch moves the name forward to the new commit.
- merge — Combining the work of two branches into one, either by moving a branch forward (a fast-forward) or by recording a merge commit.
- GitHub — A hosting service for Git repositories that adds collaboration features such as pull requests, issues, forks and releases.
- diff — A listing of the differences between two versions of something, such as two files, two commits or two screenshots.
- pull request template — A Markdown file in a repository whose text GitHub pre-fills into every new pull request description.
- GitHub issue — A numbered item on GitHub for tracking a bug, task or feature request, with its own discussion.
- cardinality — The number of distinct values a metric label can take, which multiplies how many separate series a metric creates.
- modular monolith — A monolith divided internally into modules with clear boundaries and owned data.
- branch protection rule — A setting on a hosting service that stops changes reaching a branch, usually main, unless conditions such as an approved review and passing checks are met.
Taught in
- Prompts As Code — AI Engineering: LLM Apps, RAG & Agents
- Regression Tests In CI — AI Engineering: LLM Apps, RAG & Agents
- Working With AI Coding Assistants — AI Engineering: LLM Apps, RAG & Agents
- Branch Policies And Protection Rules — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- Sixteen Pods, Room For Twelve: The System, Feedback And Continuous — Certified GitOps Associate (CGOA) Exam Prep
- Terminology Sprint: One Incident, Nine Terms — Certified GitOps Associate (CGOA) Exam Prep
- Two Clicks Nobody Wrote Down: Configuration And Infrastructure As Code — Certified GitOps Associate (CGOA) Exam Prep
- Friday At Five To Five: DevOps And DevSecOps — Certified GitOps Associate (CGOA) Exam Prep
- What Does CI Still Do? CI, CD And Where GitOps Starts — Certified GitOps Associate (CGOA) Exam Prep
- Related Practices Sprint: One Change, Five Practices — Certified GitOps Associate (CGOA) Exam Prep
- Thursday, With A Way Back: Promotion, Deploy And Release — Certified GitOps Associate (CGOA) Exam Prep
- Patterns Sprint: Eight Needs, One Pattern Each — Certified GitOps Associate (CGOA) Exam Prep
- A Bucket Nobody Wrote Down: State Stores Beyond Git — Certified GitOps Associate (CGOA) Exam Prep
- A Rollback Nobody Heard: Notifications, Observability And CI — Certified GitOps Associate (CGOA) Exam Prep
- The Evening Before: Final Review — Certified GitOps Associate (CGOA) Exam Prep
- Runners: Where Code Executes — Continuous Integration & Continuous Delivery Pipelines
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- Scaling with Matrix Builds — Continuous Integration & Continuous Delivery Pipelines
- What is GitOps? — Continuous Integration & Continuous Delivery Pipelines
- The Console versus the CLI — Cloud Infrastructure & Hyperscaler Architecture
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Shift-Left Security Principles & Automated Pipeline Gates — Cloud Security & DevSecOps Engineering
- Static Application Security Testing with Semgrep — Cloud Security & DevSecOps Engineering
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Static IaC Scanning: Linting Terraform with Checkov — Cloud Security & DevSecOps Engineering
- Enforcing OPA Guardrails on Terraform Plan Payloads — Cloud Security & DevSecOps Engineering
- Automated Accessibility Testing: axe-core & Testing Library — Design Systems & Component Engineering
- Visual Regression Testing: Playwright & Snapshot Differencing — Design Systems & Component Engineering
- System Governance: Changesets, Semantic Versioning & Deprecation — Design Systems & Component Engineering
- Instability: Change Fail Rate And Deployment Rework Rate — DevOps & Site Reliability Engineering
- Code Quality: .editorconfig and Roslyn Analyzers — Modern .NET Core, C# & Enterprise Microservices
- Conventional Commits — Advanced Git Internals & Distributed Workflows
- Reading History: log, show And diff — Advanced Git Internals & Distributed Workflows
- Merging: Fast Forward Or A Merge Commit — Advanced Git Internals & Distributed Workflows
- Clone, Forks, Push, And The Upstream Branch — Advanced Git Internals & Distributed Workflows
- The Pull Request, And Branch Naming — Advanced Git Internals & Distributed Workflows
- Reviewing Code Well — Advanced Git Internals & Distributed Workflows
- Interactive Rebase: Squash, Reorder, Reword — Advanced Git Internals & Distributed Workflows
- Investigating History: blame, bisect And worktree — Advanced Git Internals & Distributed Workflows
- The Workflow That Ran On A Stranger's Pull Request — GitHub Actions (GH-200) Exam Prep
- How GH-200 Asks: Pacing, Weights And Stems — GitHub Actions (GH-200) Exam Prep
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Expressions, Contexts And The If That Is Always True — GitHub Actions (GH-200) Exam Prep
- Outputs, Artifacts, Caches And Job Summaries — GitHub Actions (GH-200) Exam Prep
- Why It Ran, Why It Did Not: Reading Runs, Jobs And Checks — GitHub Actions (GH-200) Exam Prep
- Failed Runs: Debug Logging And Re-Running The Right Jobs — GitHub Actions (GH-200) Exam Prep
- Distributing And Versioning Actions: Tags, SHAs And Marketplace — GitHub Actions (GH-200) Exam Prep
- Governing Actions: Allow Lists, SHA Pinning And Rulesets — GitHub Actions (GH-200) Exam Prep
- Self-Hosted Runners At Scale: Labels, Groups And ARC — GitHub Actions (GH-200) Exam Prep
- Secrets And Variables By Scope: Precedence, Access And The REST API — GitHub Actions (GH-200) Exam Prep
- GITHUB_TOKEN: Least Privilege, Job By Job — GitHub Actions (GH-200) Exam Prep
- Script Injection: When An Issue Title Becomes Code — GitHub Actions (GH-200) Exam Prep
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep
- Supply Chain: Pinning, Trusted Actions And Attestations — GitHub Actions (GH-200) Exam Prep
- Faster And Cheaper: Where The Minutes Go — GitHub Actions (GH-200) Exam Prep
- YAML-Reading Sprint: What Happens When This Runs? — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep
- Cardinality And How It Bankrupts You — Full-Stack Observability: Metrics, Tracing & Logging
- The Threat Model Habit — Application Security & Threat Modeling for Engineers
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- How To Stop Drowning In Findings — Application Security & Threat Modeling for Engineers
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- What Is Infrastructure As Code? — Infrastructure as Code with Terraform
- Installing Terraform And Meeting The CLI — Infrastructure as Code with Terraform
- Tearing It Down With Destroy — Infrastructure as Code with Terraform
- Running Terraform In CI — Infrastructure as Code with Terraform
- Native Testing With Tftest Files — Infrastructure as Code with Terraform
- Provider Mocking For Tests — Infrastructure as Code with Terraform
- Policy As Code With OPA — Infrastructure as Code with Terraform
- Releasing The Real Cloud Artifact — Infrastructure as Code with Terraform
- Code Review As A Quality Gate — Automated Testing, TDD & Quality Engineering
- The Plan That Wanted To Destroy Production — HashiCorp Terraform Associate (004) Exam Prep
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Versions, The Lock File And Provider Aliases — HashiCorp Terraform Associate (004) Exam Prep
- Write, Plan, Apply, And What Init Prepares — HashiCorp Terraform Associate (004) Exam Prep
- Reading A Plan, Saving It, Applying It — HashiCorp Terraform Associate (004) Exam Prep
- Validate, Format, Destroy, And The Flags That Bend A Plan — HashiCorp Terraform Associate (004) Exam Prep
- Custom Conditions: Validation, Pre And Postconditions, Checks — HashiCorp Terraform Associate (004) Exam Prep
- Module Versions: Pin, Upgrade, Re-Initialise — HashiCorp Terraform Associate (004) Exam Prep
References
Certification courses
- AWS AIP-C01 course and practice exam: AI engineering with LLM apps, RAG and agents
- AZ-400 course and practice exam: Microsoft Azure DevOps Engineer Expert
- CGOA course and practice exam: Certified GitOps Associate
- GH-200 course and practice exam: GitHub Actions
- Terraform Associate course and practice exam: HashiCorp Terraform Associate (004)