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.

Commence par consulter les recommandations GitHub liées sur la revue des modifications d’un pull request, puis utilise l’interface PR de GitHub ou de VSCode et récupère le PR assigné avec `gh pr checkout 123`. Exécute le code, compare-le aux critères d’acceptation du ticket, pose des questions de clarification et soumets la revue directement sur le PR de ton coéquipier.

Rédigé par le modèle d'indexation à partir du texte de l'issue.