Lessons in this course (10)

6. Pull requests, code review and branch policies

Intermediate★ Must knowLesson 6 of 10

A good PR: one purpose, small (< ~400 changed lines), descriptive title, linked work item, screenshots for UI, tests included.

Branch protection / policies on main:

  • Require PR (no direct pushes), at least 1–2 reviewers, code owners for sensitive folders.
  • Require CI build + tests to pass (status checks).
  • Require linked work item and resolved comments (Azure Repos).
  • Require up-to-date branch / linear history; block force pushes.

Review checklist: correctness, tests, naming, security (secrets, SQL injection), performance, error handling, readability — comment on code, not on people.