Lines Matching full:review
11 to set aside a few minutes to review smaller changes several times than it is
12 to allocate large blocks of time to review a large PR.
25 Draft PRs have no review expectation and PRs created as drafts from the start
112 - Commits in a pull request should represent clear, logical units of change that are easy to review
212 - Respond to comments using the "Start Review" and "Add Review" green buttons in
218 middle of a review. If a rebase is required, push this as a separate update
237 review or assign to a different maintainer.
250 - After 2 weeks of inactivity, add the `dev-review`_ label to the PR. This
288 any reviews in the PR and should notify the reviewer about their review being
295 Escalation can be triggered by any party participating in the review
300 Review` label on the PR. Beside the weekly meeting where such escalations are
302 review of the escalation if requested, especially if any of the parties can't
314 .. _dev-review: https://github.com/zephyrproject-rtos/zephyr/labels/dev-review