A reference from Weave

Find a term

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

Terms beginning with A

14 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