Code review in your team

### Link to the coursework

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews

### Why are we doing this?

You must set aside a part of your development time to review the work of your team. In technical interviews, you may to asked to discuss a feature written by someone else in your team, so you will need to read and understand it.

## How to review

- [ ] Use the GitHub PR interface, either on GitHub or via VSCode
- [ ] Checkout the PR locally `gh pr checkout 123` and run the code to make sure it works
- [ ] Test the code using the acceptance criteria on the ticket
- [ ] Ask clarifying questions to make sure you understand the code
- [ ] Offer any fixes or improvements you can see

### Maximum time in hours

2

### How to get help

Volunteers and other team members can help you with code review. You may choose to spend some time in class doing this together.

### How to submit

Submit your review directly on your teammates PR.

Start with the linked GitHub pull request review guide, then open a teammate's PR in GitHub or VS Code; optionally check it out locally with `gh pr checkout 123` and run it. Review against the ticket's acceptance criteria, ask questions, suggest improvements, and submit the review on the teammate's PR.

Written by the indexing model from the issue text.