Review a pull request

### 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 your technical interview, 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 guidance on reviewing pull request changes, then use the GitHub or VSCode PR interface and check out the assigned PR with `gh pr checkout 123`. Run the code, compare it with the ticket's acceptance criteria, ask clarifying questions, and submit the review directly on the teammate's PR.

Written by the indexing model from the issue text.