Lesson 2: CI/CD, a pipeline that guards every release
19 min read·13 Oct 2026
Module 13 · Lesson 2 · About 50 minutes · Needs: Module 1, Lesson 4 (Git) and the Module 12 lab (gate.py and its saved results)The situation
Dev has two small changes ready: the shorter answer prompt from Module 12, and a tidy-up that drops a greeting such as "hi" before a message reaches the model. Today, shipping a change means Dev copying files onto the server and hoping.
The answer is a pipeline: checks every change must pass, run by a machine, ending in a deploy that can be undone in seconds. This is CI/CD. You will build BrightCart's as real files; GitHub's runners do not run here, so workflows are checked in Python and marked "not run here".