Emphasize that small CLs should be tested.

PiperOrigin-RevId: 318113971
lizhanhui · Jun 24, 2020 · 0bb4095 · 0bb4095
1 parent bfe316a
commit 0bb4095
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/review/developer/small-cls.md b/review/developer/small-cls.md
@@ -49,6 +49,7 @@ that:
     general it's better to err on the side of writing CLs that are too small vs.
     CLs that are too large. Work with your reviewer to find out what an
     acceptable size is.
+-   The CL should [include related test code](#test_code).
 -   Everything the reviewer needs to understand about the CL (except future
     development) is in the CL, the CL's description, the existing codebase, or a
     CL they've already reviewed.