From 74ca7664bf7be4e35ee668eaa1a79bc1185767c9 Mon Sep 17 00:00:00 2001 From: "A. Googler" Date: Mon, 18 Nov 2019 17:37:57 -0800 Subject: [PATCH] Internal change PiperOrigin-RevId: 281192419 --- review/developer/cl-descriptions.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/review/developer/cl-descriptions.md b/review/developer/cl-descriptions.md index c1fdfac..6f25b62 100644 --- a/review/developer/cl-descriptions.md +++ b/review/developer/cl-descriptions.md @@ -41,6 +41,11 @@ approach. If there are any shortcomings to the approach, they should be mentioned. If relevant, include background information such as bug numbers, benchmark results, and links to design documents. +If you include links to external resources consider that they may not be visible +to future readers due to access restrictions of retention policies. Where +possible include enough context for reviewers and future readers to understand +the CL. + Even small CLs deserve a little attention to detail. Put the CL in context. ## Bad CL Descriptions {#bad}