Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: fmt.Println("AAAAAAAAAAAAAAAAAA") – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: fmt.Println("AAAAAAAAAAAAAAAAAA") – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. 38 Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: fmt.Println("AAAAAAAAAAAAAAAAAA") – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. 40 Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: fmt.Println("AAAAAAAAAAAAAAAAAA") – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. 39 Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: fmt.Println(“AAAAAAAAAAAAAAAAAA”) – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: fmt.Println(“AAAAAAAAAAAAAAAAAA”) – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them com/vitessio/vitess/compare). Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: fmt.Println(“AAAAAAAAAAAAAAAAAA”) – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. 26 Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)

Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: fmt.Println("AAAAAAAAAAAAAAAAAA") – Look for inconsistencies change was implemented in this way. • Comments – // Prefer complete sentences when possible. – Leave a space after the comment marker //. If your reviewer leaves comments, make sure that you address them branch manually. Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git checkout new-feature (new-feature)