A reference from Weave

Code review glossary

Follow the path from opening a pull request to merging it. Explore review practices, collaboration patterns, and the measurements that reveal bottlenecks.

All terms

109 terms

  • Approval

    Approval is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Approval bottleneck

    An approval bottleneck occurs when a required reviewer or approval rule constrains the flow of otherwise ready changes.

    Code review

  • Approval churn

    Approval churn is the frequency with which approvals become stale, are dismissed, or need to be repeated after a change is updated.

    Code review

  • Approval condition

    Approval condition is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Approval dismissal

    Approval dismissal is the removal of an approval from the set of decisions that currently permits a change to merge.

    Code review

  • Approval expiration

    Approval expiration means a prior approval no longer satisfies the current merge policy, often because the change or target branch changed.

    Code review

  • Approval gate

    An approval gate is a workflow checkpoint that prevents a change from advancing until a defined reviewer decision is recorded.

    Code review

  • Approval latency

    Approval latency is the time between a change becoming reviewable and the required approval being recorded.

    Code review

  • Approval policy

    An approval policy states who must review which changes and what evidence is needed before integration.

    Code review

  • Approval rate

    Approval rate is the proportion of review requests or pull requests that receive the required approval within a defined population and period.

    Code review

  • Architecture review

    Architecture review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Asynchronous code review

    Asynchronous code review lets authors and reviewers contribute at different times through a persistent change discussion rather than a shared meeting.

    Code review

  • Atomic change

    Atomic change is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Automated code review

    Automated code review uses deterministic tools or models to inspect a proposed change and report possible defects, policy violations, or maintainability issues.

    Code review

  • Branch protection

    Branch protection rules define merge conditions for important branches, such as required reviews, status checks, or restrictions on direct pushes.

    Code review

  • Change author

    Change author is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Change request

    A change request is reviewer feedback that asks the author to modify a proposed change before it can be accepted.

    Code review

  • Change suggestion

    Change suggestion is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Code ownership

    Code ownership assigns review responsibility for particular files, directories, or system areas to named people or teams.

    Code review

  • Code review

    Code review is the examination of a proposed code change by someone other than its author, or by an automated reviewer, before or after integration. It helps identify problems, share context, and assess whether a change fits the surrounding system.

    Code review

  • Code review checklist

    A code review checklist is a repeatable set of questions that helps reviewers examine behavior, tests, security, operations, and maintainability.

    Code review

  • Code review time

    Code review time is the elapsed period associated with reviewing a proposed change. Teams may measure time to first response, time from opening to approval, or time from opening to merge, and those intervals describe different parts of the review process.

    Code review

  • CODEOWNERS

    A CODEOWNERS file maps repository paths to people or teams that should be requested for review when matching files change.

    Code review

  • Comment resolution time

    Comment resolution time is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Comment-only review

    Comment-only review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Dependency review

    Dependency review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Dependent change

    Dependent change is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Design review

    Design review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Discussion resolution

    Discussion resolution is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Documentation review

    Documentation review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Draft pull request

    A draft pull request signals that a change is visible for early discussion but is not ready for final approval or merge.

    Code review

  • Escaped review defect

    An escaped review defect is a problem that passes through review and is discovered later in testing, production, or user feedback.

    Code review

  • Fast-forward merge

    Fast-forward merge is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Inline review comment

    Inline review comment is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Merge commit

    Merge commit is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Merge conflict

    Merge conflict is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Merge queue

    Merge queue is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Merge readiness

    Merge readiness is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Ownership boundary

    Ownership boundary is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Ownership transfer

    Ownership transfer is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Pair review

    Pair review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Pre-review checklist

    Pre-review checklist is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Pull request size

    Pull request size describes the amount of change contained in a pull request. Tools may count added and deleted lines, changed files, commits, or a combination, so a size report should state its unit.

    Code review

  • Rebase before review

    Rebase before review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Rebase merge

    Rebase merge is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reopened review

    Reopened review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Requested changes

    Requested changes is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Required review

    Required review is a repository or branch rule that blocks integration until specified review conditions are met.

    Code review

  • Revert review

    Revert review is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review abandonment

    Review abandonment is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review