Skip to main content

Glossary Term

Pull Request

By The Codegen Team · Updated March 26, 2026

A method for submitting code changes for review before merging into a shared codebase, serving as the AI-to-human handoff point.

A pull request (PR) is a method for submitting code changes for review before merging them into a shared codebase. PRs contain the diff (what changed), a description of the changes, and space for reviewer comments and discussion.

In agent-assisted workflows, PRs serve as the primary handoff point between AI and human contributors. An autonomous coding agent produces a PR as its output, and a human reviewer evaluates whether the changes meet quality standards before merging.

The volume of PRs is increasing as agents generate code faster. This has created demand for AI-powered code review tools that can evaluate PRs at the same pace they are created.

In plain English

A formal proposal to add a set of code changes to the main codebase, which triggers review and automated testing before the changes go live.

Why it matters

Pull requests are the checkpoint where AI-generated code meets human judgment. As agents produce more PRs faster, the review queue becomes the primary bottleneck — the 2025 DORA research found AI-adopting teams saw review times grow 91% even as their output increased. The PR is where the human is still essential, which makes everything that reduces friction in that step directly valuable.

In practice

A Codegen agent completes a task and opens a PR. The description mirrors the ClickUp ticket: what was changed, why, which files are affected, and what the test results were. The CI pipeline is already green. The Codegen PR Review Agent has already left comments on the three style issues it found. The human reviewer reads the diff, approves, and merges — a 12-minute review instead of a 40-minute one.

How Codegen uses Pull Request

Pull requests are the primary output of every Codegen agent session. The agent opens the PR against the target branch, generates the description from the original task context, and the PR Review Agent runs automatically. The review-to-merge step still requires a human — Codegen does not auto-merge. That is intentional. The goal is to compress the time from task assignment to a reviewable PR, not to remove human judgment from the process entirely.

Frequently Asked Questions