From 05207e120144111f7a072baa1e265e41f95c2fa4 Mon Sep 17 00:00:00 2001 From: Rafael Santana Date: Thu, 26 Apr 2018 02:05:11 -0300 Subject: [PATCH] chore: remove unnecessary information in code_reviews (#10762) --- CODE_REVIEWS.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CODE_REVIEWS.md b/CODE_REVIEWS.md index 038e6d56194..6cf6dd1041a 100644 --- a/CODE_REVIEWS.md +++ b/CODE_REVIEWS.md @@ -3,12 +3,11 @@ * Before any coding begins on new, large, or breaking work, a design discussion should take place. * All code changes require a review and approval. * All behaviors should be covered by unit tests in the same PR. -* Large changes should be accompanied by corresponding e2e tests in the same PR. +* Large changes should be accompanied by corresponding e2e tests in the same PR. * Authors should attempt to keep PRs to 200 - 300 line changes. - + ## Workflow 1. The code author sends a PR for review. This request should include: - * A mention of the intended reviewer(s) (e.g., `@jelbourn`) * A high-level description of the change being made. * Links to any relevant issues. * Screenshots (for visual changes or new additions)