CI
Continuous Integration
ELI5 — The Vibe Check
CI is like a robot assistant that instantly checks your homework every time you hand it in. The moment you push code, it automatically runs tests to make sure you didn't break anything. If something's wrong, it tells you right away instead of letting it pile up.
Real Talk
Continuous Integration is the practice of automatically building and testing code changes every time a developer pushes to a shared repository. It detects integration errors early, prevents the 'works on my machine' problem, and keeps the codebase in a consistently working state.
Show Me The Code
# .github/workflows/ci.yml
on: [push]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: npm test
When You'll Hear This
"Set up CI so every PR gets tested automatically." / "Our CI caught that bug before it hit production."
Related Terms
Build
A build is the process of turning your development code into something a real computer or browser can run efficiently.
CD (Continuous Delivery / Continuous Deployment)
CD is what happens after CI checks your homework — it automatically delivers your finished work to the real world.
GitHub Actions
GitHub Actions is CI/CD built right into GitHub. Push code, run tests, deploy — all from YAML files in your repo. No separate CI server needed.
Pipeline
A pipeline is like an assembly line at a factory.
Workflow
A workflow is a recipe for your robot assistant — it tells CI exactly what to do when something happens. 'When someone pushes code, run tests.