# Code reviewing --- ## The Handbook https://learn.foundersandcoders.com/course/handbook/code-review/ --- ## The code review repo https://github.com/fac27/code-reviews --- ## Order of play - Read [Code review](https://learn.foundersandcoders.com/course/handbook/code-review/) in the handbook - Prepare your READMES - Quick Q&A - Code reviews - Responding to issues --- ## Prepare your READMEs - In your project pairs, again - Read the Handbook guidance - Get into pairs You have 40 minutes. --- ## Break --- ## Questions? --- ### Code review - Pair up into a group of 4 for reviewing - Return to your project pairs - Create an issue in the [code review repo](https://github.com/fac27/code-reviews), using the code review template --- 40 minutes --- ## Break --- ## Questions? --- ## Review the issue - In your project pairs, again - Review the code-review issue - Get into your group of 4 to go through your feedback together. --- ### In your pair 10 minutes --- ### In a group of 4 20 minutes --- ## Questions? --- ## A note on pull requests --- Are you using pull requests, or still merging to main? :scream: --- When you are working on a project together, it is usually more productive to review code before it has been merged. --- For the final week working on your project together, make sure that you are assigning pull requests to each other, reviewing each others' code and leaving comments on the PR before merging it. --- Take a few minutes to look at the code review issues raised by other teams. --- A couple of final things... --- That's all for now.