A push that becomes a URL
Connect Vercel to GitHub so shipping becomes routine, then see what happens when a build fails.
Deployment used to involve far more manual work. In this setup, you push code to GitHub, Vercel notices the change, builds the site and publishes it to a URL. Press the button below and watch that flow happen.
Build log
waitingNothing has happened yet. Push something and read every line: this is the screen you will stare at for the rest of your career.
What the world sees
dpl_7fa204Ines Varga
Hand bookbinder, Lisbon
Four stages, and only the first one happens on your laptop. Run the good push first, then the broken one: the second is the one nobody shows beginners.
Timings and hashes are invented; the sequence and the log lines are the real ones. Your own first deploy will scroll past faster than you can read it, which is why it is worth reading slowly once here.
Then press the second button, because this is the part many beginners worry about. A build can fail because of a typo, a missing dependency or a type error. When that happens, the pipeline stops and your live site keeps serving the previous working version.
That is one of the reassuring parts of modern deployment. A failed build normally leaves the previous working version live, so the bad change simply does not go out.
Now do it for real. Connect Vercel to the GitHub account you just made, point it at a repository with an index.html in it, and push. The first deploy usually takes under a minute; every one after that will feel like nothing at all.
Build this in your own editor
This one runs on your machine rather than in the browser workbench. Work to the outcomes below, then come back and mark it complete.
You should now be able to
- Deploy a static page from a repository
- Read a deployment log
- Explain what happens to the live site when a build fails
Loading…