From 821c5dc4d72724426e699d1762cb00f9b7a9e9c2 Mon Sep 17 00:00:00 2001 From: msperryucsd Date: Sun, 4 Jun 2023 14:25:42 -0700 Subject: [PATCH 1/2] edit README --- tests/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/README.md b/tests/README.md index 053760d..0c898b9 100644 --- a/tests/README.md +++ b/tests/README.md @@ -39,7 +39,7 @@ git push When a pull request is submitted, reviews should be done in a timely manner (it will be time-consuming to remember what the code does if the code takes a week to be reviewed) When reviewing a pull request, approve when: - - Requirements above are met + - Requirements above are met - Make sure code is commented cleanly - GitHub actions tests pass - The code runs locally on your computer (run cases to try and break their code) From a42259c4b3026be9d110b8e1c53cd4d96c528c1e Mon Sep 17 00:00:00 2001 From: msperryucsd Date: Sun, 4 Jun 2023 15:12:19 -0700 Subject: [PATCH 2/2] fix --- tests/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/README.md b/tests/README.md index 0c898b9..ca9d5ae 100644 --- a/tests/README.md +++ b/tests/README.md @@ -44,7 +44,7 @@ When reviewing a pull request, approve when: - GitHub actions tests pass - The code runs locally on your computer (run cases to try and break their code) -When rejecting a pull request, write a precise description of what needs to improved/fixed in the comment section. +When rejecting a pull request, write a precise description of what needs to improved/fixed in the comment section. ## Tests For test driven development, create tests before code implementation.