Pull request

A pull request (or merge request) packages a proposed integration: diff, description, discussion, automated checks, review decisions, and merge policy. It is both a collaboration surface and an audit record.

| Element | Purpose | |---------|---------| | Description | Intent, risk, rollout, test plan | | Checks | Lint, tests, build, security scans | | Review | Human judgment on behavior and design | | Merge strategy | Merge commit, squash, or rebase per policy |

Draft PRs enable early feedback; small PRs keep review latency low and defects visible.

On interviews: PR sizing, required checks, draft PRs, merge strategies, and how branch protection enforces policy.

Common pitfalls: giant PRs that reviewers skim; descriptions that list files but not intent; treating green CI as proof of correctness.

The trade-off is review thoroughness versus integration throughput — optimize batch size and automation together.

Checklist:

• Explain intent, risk, and test evidence in the PR body.
• Keep changes reviewable in one sitting when possible.
• Require authoritative CI before merge.
• Align merge strategy with history and release needs.