Code Review

Best practices for reviewing and approving changes

Code review catches bugs, shares knowledge, and keeps code quality high. It is a conversation, not an audit.

Code review happens between opening a PR and merging it. Reviewers check correctness, style, and design.

Open PR

Request Review

Comments

Changes

Approve

Merge

Terminal

# 1. Author opens a PR
$ gh pr create --title "Add search" --body "..."

# 2. Request reviewers
$ gh pr edit 42 --add-reviewer alice,bob

# 3. Reviewers leave comments
# 4. Author addresses feedback
# 5. Reviewer approves
# 6. PR is merged

27 / 35