CI/CD & Dev Process · Level 1
The pipeline
Mission briefing
Mission 4-A: You pushed a small token change and opened your PR like a pro. Now there's a red X next to it and a message: "Pipeline failed." You didn't even know there was a pipeline. Apparently your change is blocking a release.
When you push, an automated pipeline runs — a series of steps the code goes through before it's allowed to ship. Build it, test it, check it. Think of it like a factory line with quality checkpoints. Your change hit a checkpoint and stopped.
The first step is the build — assembling all the code into the final, runnable version of the site. Your token file had a stray comma, so the build couldn't assemble. That's all 'pipeline failed' means here: it choked at the build step.
This whole setup is CI — Continuous Integration. Every change gets automatically built and checked the moment it's pushed, so problems surface in minutes instead of weeks later. It's not punishing you; it caught a typo before users ever saw it.
I fix the comma, push again. The pipeline reruns on its own, turns green, and the path to release reopens. And CD — the part that takes a green build and ships it automatically — does the rest.
Your PR shows "pipeline failed" at the build step. What do you do?