Every time someone changes something, a machine automatically re-checks the whole thing. When everything passes, it automatically ships it out.
Like airport security: no matter who you are or how late you are, you go through that gate. Failures are stopped on the spot, and the rest go straight to boarding.
2
How was it done before?
BEFORE
Make a change, then remember to check it yourself
Checking depends on people remembering. Skip it once when you're in a hurry, look less carefully when you're tired, and a different person does it differently. Problems usually aren't because people don't know how. They happen because someone forgot that day.
NOW
Hand in your change and the machine takes over
What to check, and in what order, is written down in advance as a list. Every later change runs through that list, with no exceptions, whoever made it.
Put simply: "relying on people to remember" became "the machine does it every time".
3
How does it work?
1. Someone changes something and submits itEven if it is just one word
2. The machine runs the whole listDoes it build? Does it still work? Is it written to standard?
3. One failure stops everythingA red light goes on at once, says which item failed, and nothing goes out
4. All passed, ships automaticallyPackaged, launched, pushed to users, with no one lifting a finger
4
What do the two parts stand for?
CI
Continuous Integration
The "check" part
Everyone's changes are merged together all the time, and each merge gets checked. No saving them up. If you merge everything at the end and something breaks, nobody can say whose change did it.
CD
Continuous Delivery / Deployment
The "ship" part
Once the checks pass, it ships automatically. Some places deliver it to the doorstep and wait for a person to nod before release. Others go all the way and launch it directly.
Together: keep checking and keep shipping. "Continuous" means it isn't saved up for one big run at month end. Every single change goes through it.
5
What does the machine check?
Do old features still work?Redo the test questions written earlier
Does it build?Can it start up and run normally
Any known holes?Are the ready-made parts it uses safe
Is it tidy?Consistent style, so others can read it
On GitHub, this list is just a file in the project. Whatever is written in it gets checked every time. Whatever isn't, never gets checked.
6
One thing it can't do
Green light ≠ no problemsA green light means just one thing: everything you asked it to check passed. What you didn't put on the list, it never looked at.
So it can't judge whether a feature should exist, whether it is easy to use, or whether users like it. Those are still human jobs. It is good at exactly one thing: repeating the same checks ten thousand times without missing one.
What does it have to do with you?
Why does an app on your phone update every few days instead of every six months?
Because "releasing a new version" went from something that kept a whole company up all night to something you do with one click.
The point isn't that machines are smarter than people. It is that machines don't get tired, don't rush, and never think "this time it should be fine".
