Unit 9 · Ship it and keep it alive
Pushed is not live: verify a deploy
A push starts a build, and a build takes minutes and can fail. Say “done” only after you have seen the change on the real address customers type.
The mix-up
What people often think
“Once the code is pushed, the change is live.”
What the tutor says
A push starts a build, and a build takes minutes and can fail. Say "done" only after you have seen the change on the real URL.
What could happen between the push and the page changing?
How it works
Checking straight after pushing tells you nothing: until the build is ready, the site still serves the old version. And a ready build is not proof either, because a cache, the wrong domain or the wrong commit can still hide the change.
Changed code on your laptop proves the code changed. Only the live page proves customers see it. Check first, then report, because once you have said done, people act on it.
Close cousins of this mix-up
The tutor watches for these in the same lesson.
“You can check the site straight after pushing.”
Until the build is Ready, the site still serves the old version. Checking early tells you nothing.
“Showing the changed code proves the change.”
Code on a laptop proves the code changed. Only the live page proves customers see it.
“A Ready deploy means the change is visible.”
Ready means the build worked. A cache, the wrong domain or the wrong commit can still hide the change. Look at the page.
“You can report first and check afterwards.”
Once you have said "done", people act on it. Check the live page first, then report.
Practise it with a tutor watching
Deploy, then verify
Ship a change and prove it is live on the real URL before anyone says "done".
Free, no account needed.