Read the pipeline that ships your change
Follow a change from a pull request through the canonical CI stage set to a gated production deploy - the ordered gates a pipeline runs, why CI is the real gate, and how the deployment model promotes one signed artifact dev to staging to prod.
Units5
Duration26 min
Levelintermediate
By the end of this module, you'll be able to:
- Read the canonical CI stage set - the ordered, fail-fast gates every repository runs on every pull request - and name the mandatory floor.
- Explain why CI is the machine half of the Definition of Done, and why the local hook is only its fast mirror, not the gate.
- Reason about the deployment model: one signed artifact promoted dev to staging to prod by pull-based GitOps, with a human gate on prod.
- Follow the pipeline to its owning standards for the detail, instead of paraphrasing a gate from memory.
Prerequisites
- Basic familiarity with Git, pull requests, and the command line.
- Helpful: the AGENTS floor (least privilege, the human gate) from the contributor-onboarding path.
Units
- 01Introduction4 min
- 02The CI pipeline7 min
- 03Deploy and deliver7 min
- 04Knowledge check5 min
- 05Summary3 min
Related
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Apply the naming standards Name a new identifier, file, repo, or branch the way an AI-native org does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.
- Commits and versioning Write Conventional Commits whose type, scope, and breaking marker drive Semantic Versioning; see how release-please turns merged commits into a human-approved Release-PR, changelog, and tag; and how the trunk-based, protected-main model gates every release.