The table below indicates which team member reviewed which other team member's code.
| Reviewer | Coder |
|---|---|
| GitHub username 1 | GitHub username 2 |
| GitHub username 2 | GitHub username 3 |
| GitHub username 3 | GitHub username 4 |
| GitHub username 4 | GitHub username 5 |
| GitHub username 5 | GitHub username 6 |
| GitHub username 6 | GitHub username 7 |
| GitHub username 7 | GitHub username 1 |
NOTE: This is an example of a good format for a code review - It is very short, yet very informative (assuming you actually include links). You don't have to follow this format, but it can give you an idea of what we want to see - Short description of highlights, and links to isses/commits/pull-requests that allow us to get more details.
- I found several minor bugs (links to issues), and managed to fix a few of them (links to commits or pull-requests).
- I suggested an improvement to the design of component X (for more details, link to issue), as well as some additional useful features (links to issues).
- I thought that the implementation of component Y was very elegant - The use of interface Z (link to source file) made it really easy to add component Y to the rest of the system.
You can see all of my comments by searching for issues with the label code-review-MyGitHubUsername (link to search results).