Code Review and CI
The gates every change to your course system passes through: a CI workflow that runs on every push and pull request, commit messages a machine can read, and (in Pass 7) reviewing a change someone else wrote against the system you own.
Overview
Section titled “Overview”- What lives here: the course chapters
craft.01(your repo and CI gate, Pass 0) andcraft.08(code review of a seeded pull request, Pass 7). - Prerequisites: Shell, git, make, processes (
lang.02). - Optional depth: Software Engineering at Google, ch. 9 “Code Review” and ch. 23 “Continuous Integration” (abseil.io/resources/swe-book, free); Conventional Commits 1.0.0 (conventionalcommits.org, free).
Key Takeaways
Section titled “Key Takeaways”- CI is a function from a commit to pass or fail; branch protection turns it into a gate.
- One rule, one implementation: the hook you run locally is the step CI runs.
- Conventional commit headers make history machine-readable, which is what releases (craft.11) are computed from.
How to Study
Section titled “How to Study”- Work
craft.01right after the two Pass 0 primers; MS-P0 is green when your CI is. - Keep the gate strict from the first commit: loosening it later is easy, tightening it means rewriting history.
Chapters
Section titled “Chapters”| # | Module | Chapter | Kind | Pass |
|---|---|---|---|---|
| 1 | craft.01 | Your repo and CI gate (conventional commits enforced) | practice | 0 |
| 2 | craft.08 | Code review: review a seeded PR against your system | practice | 7 |