Lines Matching full:review

4 Code review guidelines
14 have Gerrit automatically choose an appropriate person to review your change.
25 <https://google.github.io/eng-practices/review/developer/small-cls.html>`_.
42 Review speed
45 <https://google.github.io/eng-practices/review/reviewer/speed.html>`_.  Most
48 * If you are not in the middle of a focused task, **you should do a code review
51   review request (i.e., first thing the next morning).
52 * If you will not be able to review the change within a business day, comment
58 <https://gerrit-review.googlesource.com/Documentation/user-attention-set.html>`_
60 you can continue to review. You are encouraged, but not required, to leave a
68 Feel free to link to them from code review comments, too.
85 often needs to engage in more careful design review, either in meetings with
94 Sometimes, a change doesn't make it out of the review process: after some
95 rounds of review, there are unresolved comments from the Pigweed team, but the
119 place on `our Gerrit instance <https://pigweed-review.googlesource.com/>`_.