Pull Request
A pull request is a record on a code-hosting site. It asks people to review one branch before adding its changes to a base branch.
Another example
A feature author includes the code difference, issue link, test proof, and upgrade risk. Reviewers discuss the exact changes, required checks pass, and the merge stays traceable. A pull request belongs to the hosting workflow and is not a Git object.
Main parts
- 01head and base
- 02diff and discussion
- 03review and checks
Use it when
Use this term when proposing a branch change for review, automatic checks, and controlled merging.
Do not use it when
PR approval does not prove that code is correct. Include every fact that reviewers need to judge risk.
Name used in code
head branch → review + checks → base branch Before you ship
Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback.
Outcome: Use Pull Request to release or recover the change safely, with a clear record. User context: A feature author includes the code difference, issue link, test proof, and upgrade risk. Reviewers discuss the exact changes, required checks pass, and the merge stays traceable. A pull request belongs to the hosting workflow and is not a Git object. Delivery concept or operation: Pull Request. Why it fits: Use this term when proposing a branch change for review, automatic checks, and controlled merging. Do not use it when: PR approval does not prove that code is correct. Include every fact that reviewers need to judge risk. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.
Check this request
Review the current use of Pull Request. Definition: A pull request is a record on a code-hosting site. It asks people to review one branch before adding its changes to a base branch. Release checks: Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.